distinctly specific
unambiguous
all of these
functional
C. all of these
Spiral model
Incremental model
Iterative model
Waterfall model
Lower
Back-end
Intermediate
Upper
Boehm and Belz
Khalifa and Verner
Madhavji et al.
Blackburn et al.
User Action Notation
User Action Norms
User Analogy Notation
User Analogy Norms
Study and understand the problem
Identify gross features of at least one possible solution.
Describe each abstraction used in the solution
Maintenance
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
Profit maximization
Cost reduction
Customer satisfaction
All of the above
Asset
Resource
Problem Solver
Knowledge Provider
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
Internet Explorer
Mozilla
MS-Office
Oracle
Accounting Personnel
Database Manager
Salesman
System Operator
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Upper
Front-end
Intermediate
Lower
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.
Failure detection
Damage assessment
Fault avoidance
Fault repair
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.
Confidentiality
Intellectual property rights
Managing Client Relationships
Both a & b
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Grey- box testing
White box testing
Black box testing
Red Box Testing
distinctly specific
unambiguous
all of these
functional
Entity- relation model
Data flow model
Structural model
Object model
Identify system- processing transformation
Identify input transformation
Identify output transformation
All the above
Intermediation
Disintermediation
Mediation
None of the above
Number of request for corrective maintenance
Average time required for impact analysis
All the above
Number of oustanding change request
Behavioural error
Logic errors
Performance error
Interface error
Application Domain
Staff stability
Programming language
External environment
sometimes
many times
always
no times
licensing
responsiveness
processing time
memory utilization
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
Minimization, Satisfaction
Minimization, Dissatisfaction
Maximization, Satisfaction
Maximization, Dissatisfaction