Template:— activity_composition (act_comp)
Context:— UK_Defence
Date: 2009/04/16 21:09:13
Revision: 1.2

This section specifies the template activity_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 how to represent the relationship between parent and child activities in an activity decomposition hierarchy.

Business perspective

The activity_composition business object is used by those UK_Defence Data Exchange Specifications that require information about the decomposition of actual activities .

Business object definition


Figure 1 —  Graphical Representation for Business Object Activity

Figure 1 —  Graphical Representation for Business Object Activity

Activity_composition:

The definition of an activity_composition object is: Data about the relationship between parent and child activities in an activity decomposition hierarchy.

Attribute name

Attribute description

Attribute type

Optionality

Child This is the reference to the child activity in the decomposition hierarchy. Activity Mandatory
Parent This is the reference to the parent activity in the decomposition hierarchy. Activity Mandatory
ID This is the Identifier of the activity_composition. Currently the requirement for this is the subject of an issue. Identifier Mandatory

Table 1 — Activity_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 "activity_composition". The text highlighted in blue shows the template parameters.


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

Figure 2 —  An EXPRESS-G representation of the Information model for activity_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 activity_composition template

Figure 3 —  The graphical representation of the activity_composition template

Input parameters
The following input parameters are defined for this template:
child (Type= 'ENTITY (Activity)' )
This is the reference to the child activity in the decomposition hierarchy.
parent (Type= 'ENTITY (Activity)' )
This is the reference to the child activity in the decomposition hierarchy.
Reference parameters
The following reference parameters are defined for this template:
act_rel(Type='ENTITY (Activity_relationship)')
Allow the Activity_relationship entity instantiated in this path to be referenced when this template is used.
Note: The Activity_relationship entity can be referenced in a template path by:
%^target = $activity_composition.act_rel%
where target is the parameter to which the Activity_relationship is bound.
Uniqueness constraints

The following parameter combinations specify a uniqueness constraint:
Unique constraint: Unique activity_composition
Each instance of the entity (Activity_relationship) within the data set shall be uniquely identified by a combination of the following parameters on this template (activity_composition) namely: child, parent.
The instance is referenced by the following template parameter: act_rel.
There should be one parent and child activity within the relationship.
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.
-- instantiate Activity_relationship
Activity_relationship
%^act_rel = Activity_relationship%
^act_rel.name = '/IGNORE'
^act_rel.description = '/IGNORE'
^act_rel.relating_activity -> @parent
^act_rel.related_activity -> @child
The following entities are instantiated with attributes as specified:
Entity in path Value Inherited from
Activity_relationship.name '/IGNORE'
Activity_relationship.description '/IGNORE'
Instance diagrams
The instance diagram in Figure  4 shows an example of the EXPRESS entities and templates that are instantiated by the template:
/activity_composition(child='@91', parent='@2')/
(an illustration of the consolidated activity_composition template is shown in Figure 5 below.)


Figure 4 —  Entities instantiated by activity_composition template

Figure 4 —  Entities instantiated by activity_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:
/activity_composition(child='@91', parent='@2')/


Figure 5 —  Instantiation of activity_composition template

Figure 5 —  Instantiation of activity_composition template

Characterizations
No common characterizations of the template activity_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