Requirements Engineering Principles
There is no single universally agreed definition of 'requirement'.
- Appreciate that each stakeholder may have their own.
IEEE based definition: Something needed to solve a problem or achieve an objective.
- Problems stand between you and your objectives.
Product requirements may be described as either functional or non functional.
- Functional requirements ('Affordances') define the services to be offered by a product.
- Non functional ('Quality') requirements constrain the product.
Requirements should not normally be obtained from a single stakeholder.
- But, requirements from different stakeholders may conflict.
Requirements Engineering is a risk based process.
- Perceived risk can affect the necessary amount of effort and formality.
A requirement that is not testable is not a requirement
- A requirement that cannot be afforded is not a requirement: Ian Alexander, "Writing Better Requirements.".
Capiro can help you establish a detailed set of Requirements Principles and Policies for your organisation.