Entity- relation model
Data flow model
Structural model
Object model
D. Object model
Data- flow design
Structural decomposition
Detailed design description
All the above
Failure detection
Damage assessment
Fault avoidance
Fault repair
Arrow Head
Rectangle
Rounded Rectangle
Circle
Number of request for corrective maintenance
Average time required for impact analysis
All the above
Number of oustanding change request
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.
Application Domain
Staff stability
Programming language
External environment
Ability to deliver software on time with good quality
A situation in which experienced developers leave the company
Inability of new software to inter-operate with existing software
Instability in the development team
processing
programming
storing
organizing
Waterfall model
Incremental model
Spiral model
Iterative model
Procedure-oriented, Structured
Structured, Procedure-oriented
Structured, Object-oriented
Object-oriented, Structured
The time between system failure
The frequency of occurrence with which unexpected behaviour is likely to occur
The elapsed repair or restart time when a system failure occurs. Given that the system must be continuously available.
The number of system failures given a number of systems inputs.
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Boehm and Belz
Khalifa and Verner
Madhavji et al.
Blackburn et al.
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
interface design
data design
procedural design
architectural design
Random Application Development
Raw Application Development
Robust Application Development
Rapid Application Development
Large system applications
Small system applications
Medium system applications
Very small system applications
Function reuse
Application system reuse
Sub- system reuse
Generator based reuse
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Study and understand the problem
Identify gross features of at least one possible solution.
Describe each abstraction used in the solution
Maintenance
Waterfall
Spiral
Iterative
Cleanroom
A useful approach when a customer cannot define requirements clearly.
Is more chaotic than the incremental model
Includes project risks evaluation during each iteration
Often used for the development of client/server applications
Intermediation
Disintermediation
Mediation
None of the above
licensing
responsiveness
processing time
memory utilization
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Madhavji
Sutton
Khalifa
Humphrey
Design
Project Management
Maintenance
Quality management
User satisfaction
Job satisfaction
Business success
Profit making
data,architectural and procedural designs only
architectural,procedural and interface design only
data,architectural and interface design only
data,architectural interface and procedural design
Fault avoidance
Fault tolerance
Fault detection
Fault repair