AP scope | AP module | AP contents | AP index | |
Application module: Task specification | ISO/TS 10303-1262:2004(E) © ISO |
This clause specifies the information requirements for the Task specification 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 Task_specification_arm schema and identifies the necessary external references.
$Id: arm.xml,v 1.23 2006/03/24 19:09:59 thendrix Exp $ ISO TC184/SC4/WG12 N3181 - ISO/TS 10303-1262 Task specification - EXPRESS ARM Supersedes ISO TC184/SC4/WG12 N2447 *
EXPRESS specification:
*)
SCHEMA Task_specification_arm;
(*
The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
State_observed_arm;
--
ISO/TS 10303-1256
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:
State_observed_arm ISO/TS 10303-1256 Task_element_arm ISO/CD-TS 10303-1480
NOTE 2 See Annex C, Figures C.1, C.2, C.3and C.4 for a graphical representation of this schema.
This subclause specifies the ARM types for this application module. The ARM types and definitions are specified below.
The constraint_context type is an extensible list of alternate data types that allows for the designation of the data types Task_element and Task_method_version.
NOTE The list of entity data types may be extended in application modules that use the constructs of this module.
ISO/TS 10303-1256
EXPRESS specification:
*)
TYPE
constraint_context =
EXTENSIBLE
GENERIC_ENTITY
SELECT
(Task_element,
Task_method_version);
END_TYPE;
(*
The method_or_method_version type allows for the designation of the data types Task_method and Task_method_version.
EXPRESS specification:
*)
TYPE
method_or_method_version =
SELECT
(Task_method,
Task_method_version);
END_TYPE;
(*
The state_or_state_definition_select type allows for the designation of the data types Applied_state_assignment, Applied_state_definition_assignment, State and State_definition.
EXPRESS specification:
*)
TYPE
state_or_state_definition_select =
SELECT
(Applied_state_assignment,
Applied_state_definition_assignment,
State,
State_definition);
END_TYPE;
(*
The task_classification_item type is an extension of the classification_item type. It adds the data types Activity_method, Activity_method_relationship, Applied_activity_method_assignment, Task_element_state_relationship, Task_method, Task_method_state_relationship, Task_objective and Task_objective_state_relationship to the list of alternate data types.
NOTE The list of entity data types may be extended in application modules that use the constructs of this module.
EXPRESS specification:
*)
TYPE
task_classification_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT
BASED_ON
classification_item
WITH
(Activity_method,
Activity_method_relationship,
Applied_activity_method_assignment,
Task_element_state_relationship,
Task_method,
Task_method_state_relationship,
Task_objective,
Task_objective_state_relationship);
END_TYPE;
(*
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.
EXPRESS specification:
*)
ENTITY Element_constraint
SUBTYPE OF (Task_element_relationship);
applies_in :
OPTIONAL
constraint_context;
END_ENTITY;
(*
Attribute definitions:
applies_in:
the Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task_element
is incorrectly specified.
The data type Task_specification_arm.Task_element does not exist.
Note linkend is case sensitive.
Task_element within which the constraint applies.
The value of this attribute need not be specified.
EXAMPLE Within a specific method, use of test equipment must be preceded by callibration. Or a 30 minute wait is required between stages of a method.
EXPRESS specification:
*)
ENTITY Simultaneous_elements
SUBTYPE OF (Concurrent_elements);
END_ENTITY;
(*
NOTE This can be used to provide defferent levels of description of a task for people with varying levels of experience or expertise.
EXPRESS specification:
*)
ENTITY Task_element_levels
SUBTYPE OF (Task_element);
alternatives : SET[2:?] OF Task_element;
END_ENTITY;
(*
Attribute definitions:
alternatives:
the Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task_element
is incorrectly specified.
The data type Task_specification_arm.Task_element does not exist.
Note linkend is case sensitive.
Task_elements describing two or more ways in which the same work may be undertaken.
EXPRESS specification:
*)
ENTITY Task_element_state_relationship;
state : state_or_state_definition_select;
task_element : Task_element;
END_ENTITY;
(*
Attribute definitions:
state:
the State
or Error ER-7: The express_ref linkend
state_definition:arm:State_definition_arm.State_definition
is incorrectly specified.
The data type State_definition_arm.State_definition does not exist.
Note linkend is case sensitive.
State_definition
being related.
task_element:
the Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task_element
is incorrectly specified.
The data type Task_specification_arm.Task_element does not exist.
Note linkend is case sensitive.
Task_element being related.
EXAMPLE
A Error ER-7: The express_ref linkend
task_specification:arm:Task_specification_arm.Task_element
is incorrectly specified.
The data type Task_specification_arm.Task_element does not exist.
Note linkend is case sensitive.
Task_element
calls a pre-defined task to perform an instrument calibration.
EXPRESS specification:
*)
ENTITY Task_invocation
SUBTYPE OF (Task_element);
task_method : method_or_method_version;
END_ENTITY;
(*
Attribute definitions:
task_method: the Task_method to be invoked.
NOTE The task method may be implemented using people, machines or a combination.
EXPRESS specification:
*)
ENTITY Task_method
SUBTYPE OF (Activity_method);
objective : SET[0:?] OF Task_objective;
END_ENTITY;
(*
Attribute definitions:
objective: the intended result or results of the task.
EXPRESS specification:
*)
ENTITY Task_method_assignment
SUBTYPE OF (Applied_activity_method_assignment);
SELF\Applied_activity_method_assignment.assigned_activity_method : Task_method;
SELF\Applied_activity_method_assignment.items : SET[1:?] OF task_item;
END_ENTITY;
(*
Attribute definitions:
assigned_activity_method: the Task_method being assigned.
items: the set of things that are associated to the Task_method.
NOTE The nature of the relationship is determined from its classification.
EXPRESS specification:
*)
ENTITY Task_method_relationship
SUBTYPE OF (Activity_method_relationship);
SELF\Activity_method_relationship.related_method : Task_method;Error a2: "relating" attribute must precede "related" attribute
SELF\Activity_method_relationship.relating_method : Task_method;
END_ENTITY;
(*
Attribute definitions:
related_method: the other instance of Task_method that is a part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.
relating_method: one of the instances of Task_methods that is a part of the relationship.
A Task_method_state_relationship is a relationship between a state and a Task_method.
The meaning of the entity is determined by classification. Candidate meanings include:EXPRESS specification:
*)
ENTITY Task_method_state_relationship;
state : state_or_state_definition_select;
task_method : Task_method_version;
END_ENTITY;
(*
Attribute definitions:
state: the mode of being that is related.
task_method: the Task_method being related.
EXPRESS specification:
*)
ENTITY Task_method_version
SUBTYPE OF (Activity_method);
content :
OPTIONAL
Task_element;
of_task_method : Task_method;
END_ENTITY;
(*
Attribute definitions:
content: the way in which the task is to be carried out. The value of this attribute need not be specified.
of_task_method: the Task_method which this is a version of.
EXPRESS specification:
*)
ENTITY Task_method_version_assignment
SUBTYPE OF (Applied_activity_method_assignment);
SELF\Applied_activity_method_assignment.assigned_activity_method RENAMED assigned_task_method : Task_method_version;
SELF\Applied_activity_method_assignment.items : SET[1:?] OF task_item;
END_ENTITY;
(*
Attribute definitions:
assigned_task_method: the Task_method_version being assigned.
items: the set of things that the Task_method_version is assigned to.
EXPRESS specification:
*)
ENTITY Task_method_version_relationship
SUBTYPE OF (Activity_method_relationship);
SELF\Activity_method_relationship.related_method RENAMED related_task_method : Task_method_version;Error a2: "relating" attribute must precede "related" attribute
SELF\Activity_method_relationship.relating_method RENAMED relating_task_method : Task_method_version;
END_ENTITY;
(*
Attribute definitions:
related_task_method: the other instance of Task_method_version that is a part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.
relating_task_method: one instance of Task_method_version that is a part of the relationship
NOTE More than one Task_method may be defined for a given objective, if there can be several ways to accomplish the objective.
EXPRESS specification:
*)
ENTITY Task_objective;
name : STRING;
description : STRING;
END_ENTITY;
(*
Attribute definitions:
name: the word or group of words by which the Task_objective is known.
description: the text that provides further information about the Task_objective.
EXPRESS specification:
*)
ENTITY Task_objective_state_relationship;
state : state_or_state_definition_select;
task_objective : Task_objective;
END_ENTITY;
(*
Attribute definitions:
state: the mode of being that is related.
task_objective: the Task_objective being related.
This subclause specifies the ARM subtype constraints for this module. Each subtype constraint places constraints on the possible super-type / subtype instantiations. The ARM subtype constraints and definitions are specified below.
The restrict_activity_method_relationship constraint specifies that instances of subtypes of Activity_method_relationship shall not be simultaneously of type Task_element_relationship, Task_method_relationship and Task_method_version_relationship.
EXPRESS specification:
*)
SUBTYPE_CONSTRAINT restrict_activity_method_relationship FOR Activity_method_relationship;
ONEOF (Task_element_relationship,
Task_method_relationship,
Task_method_version_relationship);
END_SUBTYPE_CONSTRAINT;
(*
The restrict_activity_method_subtypes constraint specifies that instances of subtypes of Activity_method shall not be simultaneously of type Task_element, Task_method and Task_method_version.
EXPRESS specification:
*)
SUBTYPE_CONSTRAINT restrict_activity_method_subtypes FOR Activity_method;
ONEOF (Task_element,
Task_method,
Task_method_version);
END_SUBTYPE_CONSTRAINT;
(*
The restrict_task_element_subtypes constraint specifies that instances of subtypes of Task_element shall not be simultaneously of type End_task, Exit_loop, Structured_task_element, Task_element_levels, Task_invocation and Task_step.
EXPRESS specification:
*)
SUBTYPE_CONSTRAINT restrict_task_element_subtypes FOR Task_element;
ONEOF (End_task,
Exit_loop,
Structured_task_element,
Task_element_levels,
Task_invocation,
Task_step);
END_SUBTYPE_CONSTRAINT;
(*
*)
END_SCHEMA; -- Task_specification_arm
(*
© ISO 2004 — All rights reserved