Scope

The representation of a need by a person or an organisation.
Identification of the requirement.
Objective description of what is required, including property values and units. This can be for any aspect related to Through Life Support.
The representation of the decomposition of requirements into sub requirements.
The representation of the derivation of a requirement from another requirement.
The approval status of the requirement and the date on which the status was assigned.
The date upon which the requirement was defined.
The date by which the requirement shall be satisfied.
The validity period of the requirement.
The priority of the requirement.
The category of the requirement.
Versioning of the requirement and the date of each version.
The acceptance criteria by which the requirement will be deemed to have been satisfied. This may include specification of the constraints applied to the requirement, for example cost, location, resource, applicable standards, solution directive, deadline or timescale by which it is to be satisfied.
The context that gave rise to the Requirement.
The justification for the requirement, typically a business case or cost benefit analysis.
Documentation associated with the requirement.

Task resource requirements.
Resource lists.
Requirements for the provision of resources, the movement of goods or other activities supported by the OAGIS 9.0 supply chain transaction messages.
Authority to commit effort or expenditure.
The representation of a work_requirement.
Issues, observations, symptoms and requests which may prompt action by a recipient, but do not explicitly define the required outcome.