Once stakeholder and business needs have been identified they must be translated into Requirements.
Requirements are formal structured statements. These requirements are published in Business, Stakeholder or System Requirements Specifications.
Each need may translate into one or more requirements. In order to ensure that the requirements are well written there is a standard set of quality checks which ask the following questions:
Atomic - each requirement should only address a single aspect of the system
Unambiguous – the requirement should not be open to multiple interpretations
Testable – a requirement which cannot be tested is not very useful
Necessary – requirements which are not necessary add cost to the system which has not been requested.
Contact us if you would like to discuss the definition of requirements for your next project.