In the System Development Life Cycle, during which phase is the problem domain analyzed to define requirements, constraints, and the logical model of the new system?

Introduction / Context:
Clear problem definition and requirement capture precede solution design. The SDLC separates analysis (what must be built) from design (how it will be built) to reduce rework and improve traceability from business needs to technical specifications.

Given Data / Assumptions:

• Analysis focuses on requirements, processes, data, and constraints.
• Design focuses on architecture, components, interfaces, and technologies.
• Testing occurs much later and validates built artifacts against analyzed requirements.

Concept / Approach:

The systems analysis phase develops the logical view: use cases, data flows, entity-relationship models, and nonfunctional requirements. Only after agreement on these do teams move into physical design. This separation supports stakeholder validation before making costly design commitments.

Step-by-Step Solution:

Verification / Alternative check:

Standard SDLC artifacts (SRS, process models) are outputs of analysis, not design or testing.

Why Other Options Are Wrong:

System design: Solutioning stage, not problem analysis.

Before system test: Too vague and not a defined SDLC phase.

All/None: Do not reflect the structured SDLC flow.

Common Pitfalls:

Jumping into design/technology choices before validating requirements leads to scope creep and misalignment.

Final Answer:

systems analysis phase