Template:— requirement_composition (req_comp)
Context:— UK_Defence
Date: 2009/04/17 11:42:30
Revision: 1.3

This section specifies the template requirement_composition.

NOTE  The template has been defined in the context of UK_Defence. Refer to the business context for details of related templates.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Description

This template describes the relationship between parent and child requirements, in a requirement decomposition hierarchy.

Business perspective

Requirement information is the means of identifying the relationship between two requirements where the child has been derived from the parent.

Business object definition

This information object represents the information about the decomposition of one requirement from another requirement.



Figure 1 —  A MOOD Business Architect representation of the Business Object: requirement composition.

Figure 1 —  A MOOD Business Architect representation of the Business Object: requirement composition.

The attributes of the Requirement_derivation object are tabled below.

Attribute name

Attribute description

Attribute type

Optionality

ID This is the identifier of the the requirement composition. Identifier Mandatory
Identifier.id This is the value of the id attribute of the Identifier applied to the requirement composition. Intrinsic Mandatory
Identifier.type This attribute is the type associated with the id of the Identifier given to the requirement composition. This must be one of the classes provided. Requirement_composition_identification_code Mandatory
Identifier.source_organization This attribute is the value representing the source organization that provides the id of the Identifier given to the requirement composition. This value is assumed to be a type of Organization_identification_code. Organization_identification_code Mandatory
Parent This is a reference to the originating requirement Relationship to parent requirement Mandatory
Child Relationship to child requirement Mandatory

Table 1 — Requirement_composition attribute details

Model diagrams
The EXPRESS-G diagram in Figure 2 shows the templates and EXPRESS entities that are required to represent the template "requirement_composition". The text highlighted in blue shows the template parameters.


Figure 2 —  An EXPRESS-G representation of the Information model for requirement_composition

Figure 2 —  An EXPRESS-G representation of the Information model for requirement_composition

The graphic for the template to be used in other EXPRESS-G diagrams is shown in Figure  3 below.


Figure 3 —  The graphical representation of the requirement_composition template

Figure 3 —  The graphical representation of the requirement_composition template

Input parameters
The following input parameters are defined for this template:
id (Type='STRING')
The identifier for the requirement composition.
source_organization (Type='STRING')
The organization or information system that created the associated identifier. Alternatively this could be set to /NULL when Person or Information System is the source; see Identifier template characterizations.
parent (Type= 'ENTITY (Requirement_view_definition)' )
child (Type= 'ENTITY (Requirement_view_definition)' )
Reference parameters
The following reference parameters are defined for this template:
requirement_composition(Type='ENTITY (Requirement_collection_relationship)')
Allow the Requirement_collection_relationship entity instantiated in this path to be referenced when this template is used.
Note: The Requirement_collection_relationship entity can be referenced in a template path by:
%^target = $requirement_composition.requirement_composition%
where target is the parameter to which the Requirement_collection_relationship is bound.
Instantiation path
The instantiation path shown below specifies the entities that are to be instantiated by the template.
A description of templates and the syntax for the instantiation path is provided in the Templates Help/Information section.
-- Mark the Requirement_collection_relationship as referable
%^requirement_composition = Requirement_collection_relationship%

-- Link it to the Requirement_version objects.
Requirement_collection_relationship.relating_view -> @parent
Requirement_collection_relationship.related_view -> @child

-- assign the id
/identifier(
    items= ^requirement_composition,
    ID=@id,
    source_organization=@source_organization,
    type='Requirement_composition_identification_code')/
Instance diagrams
The instance diagram in Figure  4 shows an example of the EXPRESS entities and templates that are instantiated by the template:
/requirement_composition(id='UOR125', source_organization='19374', parent='#26', child='#27')/
(an illustration of the consolidated requirement_composition template is shown in Figure 5 below.)


Figure 4 —  Entities instantiated by requirement_composition template

Figure 4 —  Entities instantiated by requirement_composition template

The instance diagram in Figure 5 shows the graphic symbol for the template that is to be used in other instance diagrams. The example template is:
/requirement_composition(id='UOR125', source_organization='19374', parent='#26', child='#27')/


Figure 5 —  Instantiation of requirement_composition template

Figure 5 —  Instantiation of requirement_composition template

Characterizations
No common characterizations of the template requirement_composition have been identified. However, the ISO 10303-239 EXPRESS model may enable other assignments to the entities instantiated by the template.

© UK MOD 2010 — All rights reserved