Which is NOT a typical phase of the System Development Life Cycle?

Which is NOT a typical phase of the System Development Life Cycle?

• A. Testing
• B. Planning
• C. Design
• D. Analysis

Answer: (A)

Understanding where Testing fits in the System Development Life Cycle helps clarify why it’s not always listed as a separate phase. In many SDLC descriptions, Planning, Analysis, and Design are clearly defined, distinct stages that set the project’s goals, gather requirements, and blueprint the system before building it. Testing, while essential to quality, is usually carried out as an ongoing activity that happens during and after development, often coordinated through quality assurance or verification steps rather than standing alone as its own phase. That’s why, in this context, Testing is considered not to be a separate SDLC phase, making it the best choice for this question. The other stages—Planning, Analysis, and Design—are the ones typically treated as individual phases that precede implementation.

Understanding where Testing fits in the System Development Life Cycle helps clarify why it’s not always listed as a separate phase. In many SDLC descriptions, Planning, Analysis, and Design are clearly defined, distinct stages that set the project’s goals, gather requirements, and blueprint the system before building it. Testing, while essential to quality, is usually carried out as an ongoing activity that happens during and after development, often coordinated through quality assurance or verification steps rather than standing alone as its own phase. That’s why, in this context, Testing is considered not to be a separate SDLC phase, making it the best choice for this question. The other stages—Planning, Analysis, and Design—are the ones typically treated as individual phases that precede implementation.