Which stage in the traditional software development lifecycle comes after requirements definition?

The stage that follows requirements definition in the traditional software development lifecycle is the systems design phase. During this phase, the project team translates the documented requirements into a detailed system architecture and design. This includes defining how the system will operate, specifying the hardware and software requirements, and outlining the overall system structure. The systems design phase is crucial as it sets the foundation for the next stages of development, helping ensure that all functional and non-functional requirements identified earlier are addressed adequately.

In contrast, sprint planning refers to agile methodologies where teams plan tasks for the next iteration, not typically a phase following requirements gathering in the traditional model. Testing occurs much later in the process, focusing on validating and verifying the software against requirements. Deployment is the final stage where the completed system is delivered to users, which also comes well after the design phase. Thus, the systems design phase is a key step immediately succeeding requirements definition in the software development lifecycle.