1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
C. 1-False, 2-True
sometimes
many times
always
no times
interface design
data design
procedural design
architectural design
bottom-up
random
top-down
center fingring
major decision points are tested early
no drivers need to be written
no stubs need to be written
regression testing is not required
Asset
Resource
Problem Solver
Knowledge Provider
Design
Project Management
Maintenance
Quality management
Accounting Personnel
Database Manager
Salesman
System Operator
Software Analysis
Software Design
Software quality
Software testing
Waterfall model
Incremental model
Spiral model
Iterative model
Profit maximization
Cost reduction
Customer satisfaction
All of the above
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Application Domain
Staff stability
Programming language
External environment
licensing
responsiveness
processing time
memory utilization
Polymorphism
Encapsulation
Inheritance
Information hiding
Lower
Back-end
Intermediate
Upper
Arrow Head
Rectangle
Rounded Rectangle
Circle
Study and understand the problem
Identify gross features of at least one possible solution.
Describe each abstraction used in the solution
Maintenance
Grey- box testing
White box testing
Black box testing
Red Box Testing
processing
programming
storing
organizing
distinctly specific
unambiguous
all of these
functional
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.
Unit testing
Integration testing
Validation testing
System testing
Data- flow design
Structural decomposition
Detailed design description
All the above
Intermediation
Disintermediation
Mediation
None of the above
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Random Application Development
Raw Application Development
Robust Application Development
Rapid Application Development
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.
Unauthorized modification of computer material
Unauthorized access to computer material
Dissemination of viruses or other malware
All of the mentioned
Function reuse
Application system reuse
Sub- system reuse
Generator based reuse
Minimization, Satisfaction
Minimization, Dissatisfaction
Maximization, Satisfaction
Maximization, Dissatisfaction