Requirements Risk Management 97
1) Develop a standard software requirements specification (SRS) outline for
their own organizations;
2) Define the format and content of their specific software requirements
specifications;
3) Develop additional local supporting items, such as an SRS quality check-
list or an SRS writer’s handbook.” (IEEE 830)
But from a risk mitigation standpoint, we are most interested in the qualities of
goodness for requirements document that are described. ese are
correct ◾
unambiguous ◾
complete ◾
consistent ◾
ranked for importance and/or stability ◾
verifiable ◾
modifiable ◾
traceable ◾
Let us describe each of these qualities in some detail.
Correctness
Correctness means that any requirement listed is one that needs to be me ...