bottom-up
random
top-down
center fingring
C. top-down
Application Domain
Staff stability
Programming language
External environment
User satisfaction
Job satisfaction
Business success
Profit making
Accounting Personnel
Database Manager
Salesman
System Operator
classical life cycle model
Fountain model
Spiral model
Concurrent model
Internet Explorer
Mozilla
MS-Office
Oracle
Class Name
Entity
Attributes
Service
Data- flow design
Structural decomposition
Detailed design description
All the above
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Polymorphism
Encapsulation
Inheritance
Information hiding
Entity- relation model
Data flow model
Structural model
Object model
Boehm and Belz
Khalifa and Verner
Madhavji et al.
Blackburn et al.
Indian Statistical Organization
Inter State Organization
International Standards Organization
Indian Standards Organization
Upper
Front-end
Intermediate
Lower
abstraction
refinement
information hiding
all of above three
Study and understand the problem
Identify gross features of at least one possible solution.
Describe each abstraction used in the solution
Maintenance
licensing
responsiveness
processing time
memory utilization
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
processing
programming
storing
organizing
Madhavji
Sutton
Khalifa
Humphrey
Number of request for corrective maintenance
Average time required for impact analysis
All the above
Number of oustanding change request
that are not relevant to him
that re relevant to him
that may be maliciously handled by him
that are confidential
Unauthorized modification of computer material
Unauthorized access to computer material
Dissemination of viruses or other malware
All of the mentioned
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Function reuse
Application system reuse
Sub- system reuse
Generator based reuse
Software Analysis
Software Design
Software quality
Software testing
Unit testing
Integration testing
Validation testing
System testing
Arrow Head
Rectangle
Rounded Rectangle
Circle
Procedure-oriented, Structured
Structured, Procedure-oriented
Structured, Object-oriented
Object-oriented, Structured
70 to 80
30 to 40
50 to 60
10 to 20
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.