Which SDLC phase is primarily used for defining system needs and requirements?

Which SDLC phase is primarily used for defining system needs and requirements?

• A. Requisition phase
• B. Requirements analysis phase
• C. Concept development phase
• D. Operations and maintenance phase

Answer: (B)

Defining what the system needs to do and how it should behave happens in the requirements analysis stage. In this phase, analysts work with stakeholders to elicit, document, and analyze needs, business processes, data requirements, constraints, and success criteria. This creates a clear baseline that guides design, development, and testing later in the lifecycle, ensuring the solution aligns with user and business goals. Other options don’t fit this purpose: a requisition-focused phase centers on obtaining resources rather than detailing what the system must achieve; concept development explores ideas and feasibility; and operations and maintenance occurs after the system is in use, focusing on support and updates. So, the requirements analysis phase is the one dedicated to defining system needs and requirements.

Defining what the system needs to do and how it should behave happens in the requirements analysis stage. In this phase, analysts work with stakeholders to elicit, document, and analyze needs, business processes, data requirements, constraints, and success criteria. This creates a clear baseline that guides design, development, and testing later in the lifecycle, ensuring the solution aligns with user and business goals. Other options don’t fit this purpose: a requisition-focused phase centers on obtaining resources rather than detailing what the system must achieve; concept development explores ideas and feasibility; and operations and maintenance occurs after the system is in use, focusing on support and updates. So, the requirements analysis phase is the one dedicated to defining system needs and requirements.