Template:— representing_task_method_state_relationship (rep_task_state_rel) Capability:representing_task |
Date: 2011/05/20 09:01:08 Revision: 1.2
|
This section specifies the template representing_task_method_state_relationship.
NOTE
The template has been defined in the context of the capability
representing_task
which provides an overall description of the
relevant parts of the ISO 10303-239 information model and a description
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 a relationship between a task and a defined state.
The EXPRESS-G diagram in
Figure
1
shows the templates and EXPRESS entities that are required
to represent the template
"representing_task_method_state_relationship".
The text highlighted in blue shows the template parameters.
Figure 1 — An EXPRESS-G representation of the Information model for representing_task_method_state_relationship
The graphic for the template to be used in other EXPRESS-G diagrams
is shown in Figure
2
below.
Figure 2 — The graphical representation of the representing_task_method_state_relationship template
The following input parameters are defined for this template:
The name of the
External_class
being used to categorize the relationship.
The following classes and their sub-classes can be used:
The following reference parameters are defined for this template:
%^target = $representing_task_method_state_relationship.task_method_state_rel%
The following parameter combinations specify a uniqueness constraint:
Unique constraint: Task method state relationship
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.
The instance diagram in Figure
3
shows an example of the EXPRESS entities and templates that are instantiated by the template:
/representing_task_method_state_relationship(rel_type='Task_objective_state', rel_type_ecl_id='urn:plcs:rdl:sample', task_method='#1', state='#2')/
(an illustration of the consolidated representing_task_method_state_relationship template is shown in
Figure
4 below.)
Figure 3 — Entities instantiated by representing_task_method_state_relationship template
The instance model in STEP ASCII exchange file format (ISO 10303 Part
21 syntax) is:
#1 = TASK_METHOD_VERSION('/IGNORE','/IGNORE','/IGNORE','/IGNORE',$,$);
#2 = STATE_DEFINITION('/IGNORE','/IGNORE');
#3 = TASK_METHOD_STATE_RELATIONSHIP(#2,#1);
#5 = CLASSIFICATION_ASSIGNMENT(#6,(#3),'/IGNORE');
#6 = EXTERNAL_CLASS('/NULL','Task_objective_state','/IGNORE',#7);
#7 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:sample','/IGNORE');
The instance diagram in
Figure
4
shows the graphic symbol for the template that is to be
used in other instance diagrams. The example template is:
/representing_task_method_state_relationship(rel_type='Task_objective_state', rel_type_ecl_id='urn:plcs:rdl:sample', task_method='#1', state='#2')/
Figure 4 — Instantiation of representing_task_method_state_relationship template
Characterizations
No common characterizations of the template
representing_task_method_state_relationship
have been identified. However, the ISO 10303-239 EXPRESS model
may enable other assignments to the entities instantiated by the template.