AP scope  |  AP module  |  AP contents  |  AP index
Application module: Extended task element ISO/WD 10303-1479

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviations

4 Information requirements
   4.1 Required AM ARM
   4.2 ARM entity definitions
5 Module interpreted model
   5.1 Mapping specification
   5.2 MIM EXPRESS short listing

A MIM short names
B Information object registration
C ARM EXPRESS-G   EXPRESS-G
D MIM EXPRESS-G   EXPRESS-G
E Computer interpretable listings
Bibliography
Index

4 Information requirements

This clause specifies the information requirements for the Extended task element application module. The information requirements are specified as the Application Reference Model (ARM) of this application module.

NOTE 1  A graphical representation of the information requirements is given in Annex C.

NOTE 2  The mapping specification is specified in 5.1. It shows how the information requirements are met by using common resources and constructs defined or imported in the MIM schema of this application module.

The following EXPRESS specification begins the Extended_task_element_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Extended_task_element_arm;
(*

4.1 Required AM ARM

The following EXPRESS interface statement specifies the elements imported from the ARM of another application module.

EXPRESS specification:

*)
USE FROM Task_element_arm;    --  ISO/CD-TS 10303-1480
(*

NOTE 1   The schemas referenced above are specified in the following part of ISO 10303:

Task_element_arm ISO/CD-TS 10303-1480

NOTE 2   See Annex C, Figures C.1and C.2 for a graphical representation of this schema.

4.2 ARM entity definitions

This subclause specifies the ARM entities for this module. Each ARM application entity is an atomic element that embodies a unique application concept and contains attributes specifying the data elements of the entity. The ARM entities and definitions are specified below.

4.2.1 Decision_path   EXPRESS-GMapping table

A Decision_path is a component of a Multiple_decision_point that identifies the Condition associated with a particular path from the decision point and the Task_element to be executed if the condition is TRUE.

EXPRESS specification:

*)
ENTITY Decision_path;
  condition : Condition;
  defined_in : Multiple_decision_point;
  path_element : Task_element;
END_ENTITY;
(*

Attribute definitions:

condition: the Condition to be evaluated to TRUE for this Decision_path to be executed.

defined_in: the Multiple_decision_point for which this Decision_path has been defined.

path_element: the Task_element to be executed if the condition is TRUE.

4.2.2 Multiple_decision_point   EXPRESS-GMapping table

A Multiple_decision_point is a type of Structured_task_element. It identifies a number of alternative Decision_path of which only one may be taken based on the conditions associated with these paths. If the conditions associated with more than one Decision_path are true then it is undefined which of these decision paths is executed. Similarly, if no condition is satisfied, the execution path is undefined.

EXPRESS specification:

*)
ENTITY Multiple_decision_point
  SUBTYPE OF (Structured_task_element);
INVERSE
  paths : SET[2:?] OF Decision_path FOR defined_in;
END_ENTITY;
(*

Attribute definitions:

paths: the collection of possible Decision_path associated with this decision point.

4.2.3 Task_io   EXPRESS-GMapping table

A Task_io is a type of Task_element_assignment that identifies that the assigned task_item is either an input or an output from this Task_step.

EXPRESS specification:

*)
ENTITY Task_io
  SUBTYPE OF (Task_element_assignment);
  SELF\Task_element_assignment.assigned_task_element : Task_step;
END_ENTITY;
(*

Attribute definitions:

assigned_task_element: the Task_step for which the input or out put is assigned.

4.2.4 Task_io_hierarchy   EXPRESS-GMapping table

A Task_io_hierarchy is a relationship between two Task_io that asserts that the parent task io is represented by the child task io at the next level of breakdown.

EXPRESS specification:

*)
ENTITY Task_io_hierarchy;
  child : Task_io;
  parent : Task_io;
WHERE
  wr1: child.role = parent.role;
END_ENTITY;
(*

Attribute definitions:

child: the Task_io that represents the input or output specified in the parent at the next level of breakdown.

parent: the Task_io which is represented by the child at the next level of task step breakdown.

Formal propositions:

wr1: Ensure the parent and child relationships are for the same role.

4.2.5 Task_step_hierarchy   EXPRESS-GMapping table

A Task_step_hierarchy is a type of Task_element_relationship that represents the fact that a parent is broken down into a lower level child.

EXPRESS specification:

*)
ENTITY Task_step_hierarchy
  SUBTYPE OF (Task_element_relationship);
  SELF\Task_element_relationship.related_method RENAMED child : Task_step;
  SELF\Task_element_relationship.relating_method RENAMED parent : Task_step;
END_ENTITY;
(*

Attribute definitions:

child: the Task_step which represents a lower level breakdown component of the parent.

parent: the Task_step which represents a higher level composition of the child along with other children represented by other, similar relationships to the same parent.



*)
END_SCHEMA;  -- Extended_task_element_arm
(*


© ISO — All rights reserved