Business DEX (UK_Defence027):— requirement | Date: 2009/04/16 17:23:05 Revision: 1.8 |
The information requirements table for the requirement DEX is shown below:
Information requirement |
Business Object(s) |
---|---|
The representation of a need by a person or an organisation. | Requirement |
Identification of the requirement. | Requirement |
Objective description of what is required, including property values and units. This can be for any aspect related to Through Life Support. | Requirement |
The representation of the decomposition of requirements into sub requirements. | Requirement Composition |
The representation of the derivation of a requirement from another requirement. | Requirement Derivation |
The approval status of the requirement and the date on which the status was assigned. | Status Assignment |
The date upon which the requirement was defined. | Requirement |
The date by which the requirement shall be satisfied. | Requirement |
The validity period of the requirement. | Requirement |
The priority of the requirement. | Requirement |
The category of the requirement. | Requirement |
Versioning of the requirement and the date of each version. | Requirement |
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. | Requirement |
The context that gave rise to the requirement. | Requirement |
The justification for the requirement, typically a business case or cost benefit analysis. | Requirement |
Documentation associated with the requirement. | Document, Document Association |
Table 1 — requirement information requirements
In terms of business objects, these information requirements are modelled as shown below in Figure 1.
NOTE For clarity, not all of the dependent business objects are included on the diagram.
© UK MOD 2010 — All rights reserved