Requirement Analysis

Requirement Analysis is the capture and validation of requirements through ongoing analysis of the problem domain. This provides the tools for transforming the requirements from the inadequate to the adequate.

If the requirement set is satisfied, the level of risk of failing to satisfy the needs of relevant stakeholders is low. Requirements change with time, so the requirements analysis must be an ongoing activity.

A requirement should:
 * be complete: refer to all necessary information for it to be satisfied.
 * be consistent: not be in conflict with any other requirement.
 * be clear: requirements should be readily understandable with only one semantic interpretation.
 * be connected: all requirements should be adequately linked to other requirements and definitions should be consistent.
 * be singular: a requirement should not express two or more requirements having different subjects and actions.
 * be verifiable: an objective process should provide evidence that a requirement is satisfied
 * be modifiable: necessary changes to a requirement can be made consistently.
 * be feasible: the means to satisfy a requirement should exist.
 * be functional: the set of requirements should state what the system should do.

Stakeholder Identification
To identify stakeholders who are potential owners of requirements. or who can facilitate effective communication relating to requirements.

Context Flow Analysis
An analysis that tracks the state of the world outside of the system on a whole of life basis.

Stakeholders are mapped to the contexts, often resulting in the identification of additional stakeholders.

A Context analysis identified the main external interface requirements. This analysis also contributes to environmental requirements. Context analysis helps identify additional stakeholders in the system.

Additional stakeholders include the owners of inter-operating systems; the individuals that interact with the system; and organizational entities which the system will interface.