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
C. Includes project risks evaluation during each iteration
Entity- relation model
Data flow model
Structural model
Object model
Data- flow design
Structural decomposition
Detailed design description
All the above
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-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Confidentiality
Intellectual property rights
Managing Client Relationships
Both a & b
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.
Failure detection
Damage assessment
Fault avoidance
Fault repair
that are not relevant to him
that re relevant to him
that may be maliciously handled by him
that are confidential
sometimes
many times
always
no times
Function reuse
Application system reuse
Sub- system reuse
Generator based reuse
Availability
Data Integrity
Security
Reliability
70 to 80
30 to 40
50 to 60
10 to 20
Random Application Development
Raw Application Development
Robust Application Development
Rapid Application Development
Intermediation
Disintermediation
Mediation
None of the above
licensing
responsiveness
processing time
memory utilization
Boehm and Belz
Khalifa and Verner
Madhavji et al.
Blackburn et al.
Spiral model
Incremental model
Iterative model
Waterfall model
Number of request for corrective maintenance
Average time required for impact analysis
All the above
Number of oustanding change request
Polymorphism
Encapsulation
Inheritance
Information hiding
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
Profit maximization
Cost reduction
Customer satisfaction
All of the above
Lower
Back-end
Intermediate
Upper
objects inherit the properties of the class
classes are defined based on the attributes of the object
objects can belong to two classes
classes are always different
Unit testing
Integration testing
Validation testing
System testing
Upper
Front-end
Intermediate
Lower
Internet Explorer
Mozilla
MS-Office
Oracle
Madhavji
Sutton
Khalifa
Humphrey
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Accounting Personnel
Database Manager
Salesman
System Operator