Template:— task_composition (tsk_comp)
Context:— UK_Defence

Date: 2009/04/17 12:21:12
Revision: 1.2

Cover Contents Description Bus. perspective Bus. obj.Model diags.Input params.Ref. params.Instantiation path Instance diags.Characterizations Issues in situ

This section specifies the template task_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 a UK_Defence Task Composition using Task_method_version_relationship.

This represents the relationship between parent and child tasks in a task decomposition hierarchy.

Business perspective

The Task composition business object is used by those UK_Defence Data Exchange Specifications that require information about task composition.

Business object definition

Figure 1 — Graphical Representation for Business Object Task Composition

Task Composition:

This template encompasses the requirements of a UK_Defence Task Composition.

The definition of a UK_Defence Task Composition object is:

This information object represent the relationship between parent and child tasks in a task decomposition hierarchy. The record consists of the attributes for a task decomposition; listed below.

Attribute name	Attribute description	Attribute type	Optionality
Child	This is the reference to the child task in the decomposition hierarchy.	Task	Mandatory
ID	This is the identifier of the task composition	Identifier	Mandatory
Parent	This is the reference to the parent task in the decomposition hierarchy.	Task	Mandatory

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

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

Input parameters

The following input parameters are defined for this template:

child (Type= 'ENTITY (Task_method_version)' )

Identifies that the child task in the decomposition hierarchy.

ID (Type='STRING')

Current identifier of the task composition.

source_organization (Type='STRING')

The organization that created the associated task composition identifier. Additionally a Person or Information System could be defined when either of these are the source; see Identifier template characterizations

type (Type='CLASS')

This is the name of the type of the class used to classify the task composition identifier and so provide the role or reason for the identification.

The following classes and their sub-classes can be used:

classifications: "Identifier_type" (urn:plcs:rdl:std:Identifier_type)

parent (Type= 'ENTITY (Task_method_version)' )

Identifies that the parent task in the decomposition hierarchy.

Reference parameters

The following reference parameters are defined for this template:

task(Type='ENTITY (Identification_assignment)')

Allow the Identification_assignment entity instantiated in this path to be referenced when this template is used.

Note: The Identification_assignment entity can be referenced in a template path by:

%^target = $task_composition.task%

where target is the parameter to which the Identification_assignment is bound.

Uniqueness constraints

The following parameter combinations specify a uniqueness constraint:

Unique constraint: Unique task composition

Each instance of the entity (Identification_assignment) within the data set shall be uniquely identified by a combination of the following parameters on this template (task_composition) namely: ID, parent, child.
The instance is referenced by the following template parameter: task.

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.

Task_method_version_relationship

-- Mark the Task_method_version_relationship entity as
-- referable when this template is used by binding it to the reference
-- parameter task_ver_rel
%^task_ver_rel = Task_method_version_relationship%
Task_method_version_relationship.name = '/IGNORE'
Task_method_version_relationship.description = '/IGNORE'
Task_method_version_relationship.relating_method -> @parent
Task_method_version_relationship.related_method -> @child

-- instantiate the task_composition's identifier
/identifier(
    ID=@ID,
    source_organization=@source_organization,
    type=@type,
    items=^task_ver_rel)/

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Task_method_version_relationship.name	'/IGNORE'	Activity_method_relationship.name
Task_method_version_relationship.description	'/IGNORE'	Activity_method_relationship.description

Instance diagrams

The instance diagram in Figure 4 shows an example of the EXPRESS entities and templates that are instantiated by the template:

/task_composition(parent='@122', child='@1', id='TC1234', source_organization='BAE Systems', type='Task_method_identification_code')/

(an illustration of the consolidated task_composition template is shown in Figure 5 below.)

Figure 4 — Entities instantiated by task_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:

/task_composition(parent='@122', child='@1', id='TC1234', source_organization='BAE Systems', type='Task_method_identification_code')/

Figure 5 — Instantiation of task_composition template

Characterizations

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