Assume a five-phase SDLC for this question: (1) Planning, (2) Analysis, (3) Design, (4) Implementation, (5) Maintenance. Which of the following activities does not belong to Phase 4 (Implementation)?

Difficulty: Easy

Correct Answer: Conduct interviews

Explanation:


Introduction / Context:
SDLC activities are grouped into phases to reduce risk and create predictable outcomes. For clarity, this question explicitly defines Phase 4 as Implementation, which typically includes acquiring or configuring the environment, integrating components, system testing, user training, cutover, and deployment. The task is to identify the activity that is not part of Implementation under this assumption.


Given Data / Assumptions:

  • Phase 4 is Implementation (build/configure, integrate, test, train, deploy).
  • Earlier phases already captured requirements and designed the solution.
  • We must choose the activity that does not belong to Implementation.


Concept / Approach:
Implementation turns design into working capability: provisioning hardware/software, building/configuring components, system/integration testing, data migration, user training, and go-live. By contrast, stakeholder interviews are a hallmark of Analysis (Phase 2), where we elicit and refine requirements prior to design and build.


Step-by-Step Solution:

1) Map each option to the defined phases. 2) Acquire hardware/software: Implementation (environment readiness). 3) Test the new system: Implementation (system/integration testing). 4) Train users: Implementation (adoption/transition activity). 5) Conduct interviews: belongs to Analysis, not Implementation.


Verification / Alternative check:
Cross-check with standard SDLC references: elicitation and interviews are listed under Analysis deliverables such as requirements specifications and process models; they precede Implementation tasks.


Why Other Options Are Wrong:

Training users: typically scheduled near go-live to ensure adoption. Acquiring hardware/software: prepares the technical environment for deployment. Testing the new system: validates integration and readiness in Implementation. None of the above: incorrect because one option (interviews) clearly does not belong.


Common Pitfalls:
Starting interviews during Implementation due to scope creep leads to rework; keep discovery bounded to Analysis with change control thereafter.


Final Answer:
Conduct interviews.

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion