Hermeneutical Theodolite of Requirements

The evolution states of the software requirements and their respective sub-states

States

Sub-States

Identified

・ The requirement was identified individually for stakeholders.

・ The origin and classification of the requirement are clear.

・ The business rules and the restrictions imposed on the requirement are known.

・ The requirement has been described briefly and concisely.

Conceived

・ The requirement communicates its essential characteristics.

・ The requirement has been prioritized.

・ The requirement has no conflict with another requirement.

・ It is possible to trace the requirement.

Described

・ The requirement is clear in relation to its scope.

・ The requirement is consistent with the expectations of stakeholders.

・ Stakeholders accept that the requirement accurately captured it’s what it does what does not.

・ The allocation of the requirement has been made.

Declared

・ The requirement complies with the required standards.

・ The set of requirements items provides clear value to stakeholders.

・ The requirement has been specified consistently.

・ Is possible test and evaluate the requirement.

Approved

・ The requirement is complete and consistent.

・ The requirement has no omissions and no ambiguities.

・ There are no items pending in the requirement, preventing its acceptance by stakeholders.

・ The requirement was accepted by stakeholders as being fully meeting their needs.