Study and understand the problem
Identify gross features of at least one possible solution.
Describe each abstraction used in the solution
Maintenance
D. Maintenance
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
classical life cycle model
Fountain model
Spiral model
Concurrent model
Random Application Development
Raw Application Development
Robust Application Development
Rapid Application Development
Application Domain
Staff stability
Programming language
External environment
interface design
data design
procedural design
architectural design
sometimes
many times
always
no times
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Arrow Head
Rectangle
Rounded Rectangle
Circle
Data- flow design
Structural decomposition
Detailed design description
All the above
An Old Fashioned model that cannot be used in a modern context
A good approach when a working program is required quickly
A useful approach when a customer cannot define requirements clearly.
A reasonable approach when requirement are well defined.
Entity- relation model
Data flow model
Structural model
Object model
Design
Project Management
Maintenance
Quality management
Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.
The product should be easy to use.
It means that the product designed /created should be easily available.
Software engineers shall ensure that their products and related modifications satisfy the client.
Study and understand the problem
Identify gross features of at least one possible solution.
Describe each abstraction used in the solution
Maintenance
Availability
Data Integrity
Security
Reliability
bottom-up
random
top-down
center fingring
70 to 80
30 to 40
50 to 60
10 to 20
Indian Statistical Organization
Inter State Organization
International Standards Organization
Indian Standards Organization
Unit testing
Integration testing
Validation testing
System testing
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
distinctly specific
unambiguous
all of these
functional
Madhavji
Sutton
Khalifa
Humphrey
User Action Notation
User Action Norms
User Analogy Notation
User Analogy Norms
Number of request for corrective maintenance
Average time required for impact analysis
All the above
Number of oustanding change request
Waterfall
Spiral
Iterative
Cleanroom
major decision points are tested early
no drivers need to be written
no stubs need to be written
regression testing is not required
Large system applications
Small system applications
Medium system applications
Very small system applications
System Operator
Salesman
Database Manager
Accountant
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True