Requirements for Software Engineerings
Requirements in software engineering are the statements of what a system must do and how well it must do it. They are gathered from users and stakeholders, written down, checked and managed before design starts. This unit also covers process models such as waterfall, iterative and agile that decide how requirements flow into delivery.
Stage: Requirements and Process · Part of the Software Engineering roadmap · Last reviewed 19 November 2026
What to learn in Requirements
- Separate functional requirements from non-functional ones such as latency, availability and security
- Write a user story with clear acceptance criteria that a tester can verify
- Elicit requirements through interviews, prototypes and observation of real users
- Compare waterfall, iterative and Scrum models and pick one for a given project
- Trace a requirement through design, code and test to catch scope creep
Requirements interview questions
What is the difference between functional and non-functional requirements?
Functional requirements describe behaviour the system provides, such as letting a user reset a password. Non-functional requirements describe qualities of that behaviour, such as the reset email arriving within thirty seconds or the system handling ten thousand concurrent users. Both must be testable, or they cannot be verified.
Why do agile teams still write requirements?
Agile does not remove requirements, it changes how they are captured. Stories, acceptance criteria and a prioritised backlog record intent in small pieces that are refined each sprint. The aim is to learn early and adjust, while still giving developers and testers a shared, checkable definition of done.
Where Requirements fits in the Software Engineering roadmap
Requirements belongs to the Requirements and Process stage (beginner level), which takes about 33 hours. Know what to build.
Other units in this stage
Back to the full Software Engineering roadmap