This section describes the criteria which have been established for requirements documentation and from which organizations or companies they come from. It must always be decided as to what criteria should be used for the requirements documentation for each project.
The Institute of Electrical and Electronic Engineers (IEEE) already defined the standard IEEE 830 in 1998. This stipulates the basic quality criteria for the documentation of requirements.
The criteria formulated in the standard IEEE 830 are:
The book by the Sophist Group “Requirements Engineering and Management” is a standard reference for dealing with requirements for many requirements analysts.
The Sophist Group is extending the IEEE 830 standard with the following criteria:
Necessary: each requirement should describe a performance or feature that is actually required by the customer or required to adapt to an external system. A requirement is only necessary if you fulfill a system objective.
The INVEST-features according to Cohn are specially formulated for user-stories (a type of requirements documentation in agile process models), but can also be used without these requirements.
There are the following features:
If you would like to know how to deal with requirements in Scrum professionally, refer to the chapter “Professional Requirements Management with Scrum”.