1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
C. 1-False, 2-True
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.
Lower
Back-end
Intermediate
Upper
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Understanding
Restrictions
Transparency
Controversy
data,architectural and procedural designs only
architectural,procedural and interface design only
data,architectural and interface design only
data,architectural interface and procedural design
distinctly specific
unambiguous
all of these
functional
Random Application Development
Raw Application Development
Robust Application Development
Rapid Application Development
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.
Fault avoidance
Fault tolerance
Fault detection
Fault repair
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Grey- box testing
White box testing
Black box testing
Red Box Testing
70 to 80
30 to 40
50 to 60
10 to 20
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
Behavioural error
Logic errors
Performance error
Interface error
sometimes
many times
always
no times
Data- flow design
Structural decomposition
Detailed design description
All the above
Unit testing
Integration testing
Validation testing
System testing
Design
Project Management
Maintenance
Quality management
Arrow Head
Rectangle
Rounded Rectangle
Circle
Large system applications
Small system applications
Medium system applications
Very small system applications
Boehm and Belz
Khalifa and Verner
Madhavji et al.
Blackburn et al.
Profit maximization
Cost reduction
Customer satisfaction
All of the above
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Which is used by one person only
Which is assigned one and only one task
Which uses one kind of software
Which is meant for application software
User Action Notation
User Action Norms
User Analogy Notation
User Analogy Norms
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
Availability
Data Integrity
Security
Reliability
User satisfaction
Job satisfaction
Business success
Profit making
Function reuse
Application system reuse
Sub- system reuse
Generator based reuse