Which statement describes the sequence and purpose of the steps in a typical Software Development Life Cycle (SDLC)?

Which statement describes the sequence and purpose of the steps in a typical Software Development Life Cycle (SDLC)?

• A. Requirements gathering, Design, Implementation (coding), Testing, Deployment, Maintenance; each phase adds planning, building, verifying, releasing, and updating software.
• B. Requirements gathering, Design, Implementation (coding), Testing, Deployment; Maintenance is optional.
• C. Planning, Design, Coding, Testing, Deployment, Retirement.
• D. Design, Deployment, Maintenance, Requirements, and Testing.

Answer: (A)

The main idea being tested is the ordered set of stages in the Software Development Life Cycle and what each stage does. In a typical SDLC, you begin with gathering requirements to understand what the software must achieve and the constraints it must meet. Next comes design, where the architecture and components are planned to meet those requirements. Then you implement or code the design, turning plans into working software. After implementation, testing verifies that the software works as intended and satisfies the requirements. Once testing is complete, the software is deployed to users. Finally, maintenance involves ongoing fixes, updates, and enhancements after release. Maintenance isn’t optional in practice because software continuously needs support as issues arise and needs evolve. The other options misplace or skip stages—such as omitting maintenance, introducing retirement, or rearranging phases—so they don’t reflect the typical, purposeful flow of SDLC.

The main idea being tested is the ordered set of stages in the Software Development Life Cycle and what each stage does. In a typical SDLC, you begin with gathering requirements to understand what the software must achieve and the constraints it must meet. Next comes design, where the architecture and components are planned to meet those requirements. Then you implement or code the design, turning plans into working software. After implementation, testing verifies that the software works as intended and satisfies the requirements. Once testing is complete, the software is deployed to users. Finally, maintenance involves ongoing fixes, updates, and enhancements after release. Maintenance isn’t optional in practice because software continuously needs support as issues arise and needs evolve. The other options misplace or skip stages—such as omitting maintenance, introducing retirement, or rearranging phases—so they don’t reflect the typical, purposeful flow of SDLC.