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.

This template describes how to represent the relationship between the Required PSE Constituent Usage Role and the Configuration

Figure 1 — Graphical Representation for Business Object usage_role_configuration_relationship

usage_role_configuration_relationship

The definition of a usage_role_configuration_relationship object is: This information object represents information about an actual usage_role_configuration_relationship of an individual product.

Attribute name	Attribute description	Attribute type	Optionality
ID	This is the identifier of the relationship.	Identifier	Mandatory
Identifier.id	This is the value of the id attribute of the Identifier applied to the relationship.	intrinsic	Mandatory
Identifier.type	This attribute is the type associated with the id of the Identifier given to the relationship.	usage_role_configuration_relationship_id_code	Mandatory
Identifier.source_organization	This attribute is the value representing the source organization that provides the id of the Identifier given to the relationship. This value is assumed to be a type of Organization_identification_code.	Organization_identification_code	Mandatory
Related configuration	This is a reference to the related configuration.	Relationship to Configuration Management Breakdown	Mandatory
Related usage role	This a reference to the Required PSE Constituent Usage Role.	Relationship to Required PSE Constituent Usage Role	Mandatory

Table 1 — usage_role_configuration_relationship attribute details

The following input parameters are defined for this template:

The following reference parameters are defined for this template:

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

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

%^target = $usage_role_configuration_relationship.usage_role_configuration_relationship%

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

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.

-- create the assignment to link the reqd_pse_cont_usg_role
Task_method_version_assignment
Task_method_version_assignment.role = '/IGNORE'
Task_method_version_assignment.assigned_activity_method -> @related_usage_role
Task_method_version_assignment.items -> @related_configuration
%^usage_role_configuration_relationship = Task_method_version_assignment%

-- id identifier
/identifier(
    ID=@id,
    source_organization=@source_organization,
    type='usage_role_configuration_relationship_id_code',
    items=^usage_role_configuration_relationship)/

The following entities are instantiated with attributes as specified:

Entity in path	Value	Inherited from
Task_method_version_assignment.role	'/IGNORE'	Applied_activity_method_assignment.role

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

/usage_role_configuration_relationship(related_configuration='@2', related_usage_role='@82', id='role_config_relationship_14', source_organization='6421')/

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