This is a draft cheat sheet. It is a work in progress and is not finished yet.
quality criteria for requirements
whole sentence |
Requirements should always be formulated in complete sentences |
complete |
requirements should describe all details |
explicit |
requirements should be precise and measurably |
not reducible |
An application should always describe only the smallest possible circumstances |
realisable |
requirements should be realisable, especially with
regard to the given conversion time |
up-to-date |
Each time indication should be absolute and not refer to other things |
|
|
quality criteria for requirements
sortable |
A requirement should be able to be eliminated on its own. This should serve the sortability |
traceable |
Each requirement should have a unique number. This number should not change in the different versions of a document |
suitable scope |
A requirement document should only be as long as necessary to describe the desired situation |
consistent |
In a requirement document, two requirements should never contradict each other |
accessible together |
Requirements should be as transparent as possible and accessible to every stakeholder |
standardized structure |
Requirements documents should be based on a template |
|
