Which set of phases is commonly used in a five-phase SDLC breakdown?

Which set of phases is commonly used in a five-phase SDLC breakdown?

• A. Requirements, Design, Implementation, Test, Maintenance
• B. Planning, Analysis, Coding, Testing, Deployment
• C. Initiation, Planning, Execution, Control, Close
• D. Concept, Development, Validation, Release, Support

Answer: (A)

In a five-phase SDLC, work flows from defining what’s needed to keeping the system functioning after release. The sequence starts with gathering and documenting requirements from stakeholders, which sets what the system must achieve. Then design translates those needs into architecture, modules, interfaces, and data models. After that, implementation is the actual building of the software and often includes unit testing. The next phase, testing, verifies that the product meets the requirements through various tests and quality checks. Finally, maintenance covers post-release support, bug fixes, and enhancements to keep the system useful over time. This set—requirements, design, implementation, testing, maintenance—is the most widely taught and recognized five-phase breakdown, which is why it’s the best answer. Other options reflect different naming or include additional stages like deployment or project-management phases, but they don’t align as cleanly with the classic five-phase SDLC flow.

In a five-phase SDLC, work flows from defining what’s needed to keeping the system functioning after release. The sequence starts with gathering and documenting requirements from stakeholders, which sets what the system must achieve. Then design translates those needs into architecture, modules, interfaces, and data models. After that, implementation is the actual building of the software and often includes unit testing. The next phase, testing, verifies that the product meets the requirements through various tests and quality checks. Finally, maintenance covers post-release support, bug fixes, and enhancements to keep the system useful over time. This set—requirements, design, implementation, testing, maintenance—is the most widely taught and recognized five-phase breakdown, which is why it’s the best answer. Other options reflect different naming or include additional stages like deployment or project-management phases, but they don’t align as cleanly with the classic five-phase SDLC flow.