Requirements: definiton
We use the collective term requirements to refer to all of these types of information, whether your personal terminology focuses on features, use cases, user stories, or anything else.
What are they?
Requirements are a specification of what should be implemented. They are descriptions of how the system should behave, or of a system property or attribute. They may be a constraint on the development process of the system. This definition points out that requirements encompass multiple types of information. Most importantly, the concept of a requirement is a statement of a stakeholder need, which is the real starting point for all discussions about requirements.
- Requirements serve as a detailed delineation of the envisioned implementation, encompassing the desired system behavior and its properties or attributes.
- They function as guiding principles throughout the development process, ensuring adherence to specified constraints.
- The essence of requirements lies in their role as indispensable directives, shaping the trajectory of system development.
Key questions
- Why the project is being pursued? (Business Objectives/Vision for the project).
- What the desired outcome is? (Expectations)
- Who the stakeholders are? (PoC or Decision Maker)
- How success will be measured? (KPIs, Metrics).