Which phase answers the questions of who will use the system, what the system will do and where and when it will be used?

Question

Accepted Answer

The correct option is (1):
The **Analysis** phase, often called the Requirements Analysis or Requirements Gathering phase, is the crucial step in the System Development Life Cycle (SDLC) specifically dedicated to fully understanding the business problem and the needs of the stakeholders. It is during this phase that analysts work closely with users to determine *who* will use the system (the user roles), *what* the system must be capable of doing (the functional requirements), and the complete operational context of *where* and *when* the system will be installed and utilized. These activities produce the detailed Software Requirements Specification (SRS) document, which serves as the definitive blueprint for the entire development project. By answering the fundamental "who, what, where, and when" questions, the Analysis phase ensures the final system will meet the actual business need.

The incorrect option is (2):
The **Design** phase occurs *after* the Analysis phase. Its purpose is to figure out *how* the system will fulfill the requirements that were documented during the Analysis phase. This involves creating the architectural structure, database tables, modules, user interfaces, and technical specifications for the system. Design is an implementation strategy, not a requirements definition activity.

The incorrect option is (3):
The **Implementation** phase is a late-stage activity in the SDLC. This is the stage where developers write, compile, and test the actual program code, install the hardware, and prepare the system for launch. By this point, the requirements (what to build) and the design (how to build it) have already been fixed and approved.

The incorrect option is (4):
The **Planning** phase is the very first stage of the SDLC. Its focus is on initial project feasibility, resource estimation, scheduling, and budget determination. Planning establishes *why* the project is necessary and whether it is viable, and sets the initial scope. It does not go into the deep detail required to define the system's exact requirements—the detailed "who, what, where, and when"—which is the job of the Analysis phase.