Free Software Development Lifecycle MCQs with Answers

• A. Spiral
• B. Waterfall
• C. RAD
• D. Iterative Enhancement Model

Explanation: The Spiral model repeatedly identifies and reduces risks, making it useful when the team has limited experience with similar projects.

• A. Requirements
• B. Development team & Users
• C. Project type and associated risk
• D. All of the mentioned

Explanation: Model selection depends on several factors, including requirements, the development team and users, and the project type and risks.

• A. Software Verification
• B. Software Validation
• C. Software design and implementation
• D. Software evolution

Explanation: The fundamental process activities are specification, design and implementation, validation, and evolution.

• A. Transition
• B. Elaboration
• C. Construction
• D. Inception

Explanation: RUP's Inception phase establishes the system's scope, feasibility, objectives, and business case.

• A. It shows the process activities that are enacted
• B. It suggests good practices to be used during the process
• C. It shows the phases of the model over time
• D. All of the mentioned

Explanation: The static perspective describes the activities and workflows that make up the RUP process.

• A. Progress can be measured for Incremental Model
• B. Changing requirements can be accommodated in Incremental Model
• C. Users can see the system early in Incremental Model
• D. All of the mentioned

Explanation: Progress is explicitly tracked through the successive working increments, making it easy to measure what has been completed.

• A. It defines tasks required to define resources, timelines, and other project related information
• B. It defines a set of negotiation activities at the beginning of each pass around the spiral
• C. It defines tasks required to assess both technical and management risks
• D. It defines tasks required to construct, test, install, and provide user support

Explanation: The WINWIN Spiral Model adds stakeholder negotiation at the start of every spiral cycle so that conflicting goals can be reconciled.

• A. Customer can respond to each increment
• B. Easier to test and debug
• C. It is used when there is a need to get a product to the market early
• D. Easier to test and debug & It is used when there is a need to get a product to the market early

Explanation: Incremental development produces smaller working releases, so each increment is easier to test and the product can reach users or the…

• A. IBM
• B. Barry Boehm
• C. Pressman
• D. Royce

Explanation: Barry Boehm proposed the Spiral Model in 1986, making risk analysis the central activity of each development cycle.

• A. Software Development Life Cycle
• B. System Development Life cycle
• C. Software Design Life Cycle
• D. System Design Life Cycle

Explanation: SDLC expands to Software Development Life Cycle, the sequence of activities used to plan, build, test, deploy, and maintain software.

• A. 2 phases
• B. 3 phase
• C. 5 phases
• D. 6 phases

Explanation: The usual RAD structure has five phases: business modeling, data modeling, process modeling, application generation, and testing and…

• A. Quick Design
• B. Coding
• C. Prototype Refinement
• D. Engineer Product

Explanation: The Prototyping Model normally includes communication, quick planning and design, prototype construction, and evaluation or refinement…

• A. Waterfall Model
• B. Prototyping Model
• C. RAD Model
• D. both Prototyping Model & RAD Model

Explanation: RAD relies on continuous user participation to define requirements, review prototypes, and approve successive versions throughout…

• A. 100-200
• B. 200-400
• C. 400-1000
• D. above 1000

Explanation: The Build and Fix approach is intended for very small programming exercises, commonly around 100 to 200 lines of code.

• A. Build & Fix Model
• B. Prototyping Model
• C. RAD Model
• D. Waterfall Model

Explanation: The Waterfall Model fixes most requirements and development stages early, so changes later are costly and difficult to accommodate.

• A. Heterogeneity
• B. Flexibility
• C. Business and social change
• D. Security

Explanation: Heterogeneity, business and social change, and security are broad software-engineering concerns affecting many software types.

• A. Software dependence
• B. Software development
• C. Software validation
• D. Software specification

Explanation: The basic software process activities include specification, development, validation, and evolution.

• A. Increasing Demand
• B. Low expectation
• C. Increasing Supply
• D. Less reliable and expensive

Explanation: Increasing demand, low expectations, and software that is unreliable or expensive are commonly cited factors behind software problems.

• A. Software companies
• B. Software Developers
• C. Both Software companies and Developers
• D. All of the mentioned

Explanation: Software failures can result from both organizational decisions by software companies and technical or process mistakes by developers.

• A. The product should be easy to use
• B. Software engineers shall ensure that their products and related modifications meet the highest professional standards possible
• C. Software engineers shall ensure that their products and related modifications satisfy the client
• D. It means that the product designed /created should be easily available

Explanation: The Product principle requires engineers to ensure that software and its modifications meet the highest professional standards possible.