A Combination of prototyping and waterfall model
Includes project risks evaluation during each iteration
A high speed adaptation of the linear sequential model
Used to suggests a systematic sequential approach to software development
C. A high speed adaptation of the linear sequential model
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
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Class Name
Entity
Attributes
Service
interface design
data design
procedural design
architectural design
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
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.
not use your technical skills to misuse other peoples computers.
not knowingly accept work that is outside your competence.
be dependent on their colleagues.
maintain integrity and independence in their professional judgment.
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
Fault avoidance
Fault tolerance
Fault detection
Fault repair
Design
Project Management
Maintenance
Quality management
licensing
responsiveness
processing time
memory utilization
A Combination of prototyping and waterfall model
Includes project risks evaluation during each iteration
A high speed adaptation of the linear sequential model
Used to suggests a systematic sequential approach to software development
ensure that their products only meet the SRS.
act consistently with the public interest.
act in a manner that is in the best interests of his expertise and favour.
none
70 to 80
30 to 40
50 to 60
10 to 20
Function reuse
Application system reuse
Sub- system reuse
Generator based reuse
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Availability
Data Integrity
Security
Reliability
classical life cycle model
Fountain model
Spiral model
Concurrent model
major decision points are tested early
no drivers need to be written
no stubs need to be written
regression testing is not required
abstraction
refinement
information hiding
all of above three
data,architectural and procedural designs only
architectural,procedural and interface design only
data,architectural and interface design only
data,architectural interface and procedural design
Upper
Front-end
Intermediate
Lower
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.
User satisfaction
Job satisfaction
Business success
Profit making
Software Analysis
Software Design
Software quality
Software testing
Indian Statistical Organization
Inter State Organization
International Standards Organization
Indian Standards Organization
Unit testing
Integration testing
Validation testing
System testing
Number of request for corrective maintenance
Average time required for impact analysis
All the above
Number of oustanding change request