Asset
Resource
Problem Solver
Knowledge Provider
B. Resource
licensing
responsiveness
processing time
memory utilization
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
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.
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Lower
Back-end
Intermediate
Upper
Random Application Development
Raw Application Development
Robust Application Development
Rapid Application Development
Accounting Personnel
Database Manager
Salesman
System Operator
70 to 80
30 to 40
50 to 60
10 to 20
Understanding
Restrictions
Transparency
Controversy
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Study and understand the problem
Identify gross features of at least one possible solution.
Describe each abstraction used in the solution
Maintenance
processing
programming
storing
organizing
interface design
data design
procedural design
architectural design
Intermediation
Disintermediation
Mediation
None of the above
Waterfall model
Incremental model
Spiral model
Iterative model
Asset
Resource
Problem Solver
Knowledge Provider
Procedure-oriented, Structured
Structured, Procedure-oriented
Structured, Object-oriented
Object-oriented, Structured
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
major decision points are tested early
no drivers need to be written
no stubs need to be written
regression testing is not required
bottom-up
random
top-down
center fingring
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
that are not relevant to him
that re relevant to him
that may be maliciously handled by him
that are confidential
Profit maximization
Cost reduction
Customer satisfaction
All of the above
Grey- box testing
White box testing
Black box testing
Red Box Testing
Confidentiality
Intellectual property rights
Managing Client Relationships
Both a & b
Application Domain
Staff stability
Programming language
External environment
Failure detection
Damage assessment
Fault avoidance
Fault repair
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
Availability
Data Integrity
Security
Reliability
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.