AP scope  |  AP module  |  AP contents  |  AP index
Application module: Activity method implementation ISO/TS 10303-1261:2004(E)
© ISO

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 ARMs
   4.2 ARM type definitions
   4.3 ARM entity definitions
5 Module interpreted model
   5.1 Mapping specification
   5.2 MIM EXPRESS short listing
     5.2.1 MIM type definitions

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 Activity method implementation 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 Activity_method_implementation_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Activity_method_implementation_arm;
(*

4.1 Required AM ARMs

The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.

EXPRESS specification:

*)
USE FROM Activity_method_arm;    --  ISO/TS 10303-1049

USE FROM Classification_assignment_arm;    --  ISO/TS 10303-1114
(*

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

Activity_method_arm ISO/TS 10303-1049
Classification_assignment_arm ISO/TS 10303-1114

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

4.2 ARM type definitions

This subclause specifies the ARM types for this application module. The ARM types and definitions are specified below.

4.2.1 activity_method_implementation_classified_item   EXPRESS-G

The activity_method_implementation_classified_item type is an extension of the classification_item type. It adds the data types Activity_method_realization and Activity_method_realization_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 activity_method_implementation_classified_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON classification_item WITH
   (Activity_method_realization,
    Activity_method_realization_relationship);
END_TYPE;
(*

4.2.2 activity_realization_select   EXPRESS-G

The activity_realization_select type is an extensible list of alternate data types. Additional alternate data types are specified in select data types that extend the activity_realization_select type.

NOTE   This empty extensible select requires extension in a further module to ensure that entities that refer to it have at least one valid instantiation.

EXPRESS specification:

*)
TYPE activity_realization_select = EXTENSIBLE SELECT;
END_TYPE;
(*

4.3 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.3.1 Activity_method_realization   EXPRESS-GMapping table

An Activity_method_realization is a further specification of how an activity method is to be performed with the Activity_method.

NOTE 1   More than one specification can be associated with the same Activity_method.

EXAMPLE 1   For a given planned activity there may be a task specification, a statement of how task performance is to be logged and a schedule that all apply.

EXPRESS specification:

*)
ENTITY Activity_method_realization;
  id : STRING;
  name : STRING;
  description : OPTIONAL STRING;
  activity_method : Activity_method;
  realized_by : activity_realization_select;
END_ENTITY;
(*

Attribute definitions:

id: an identifier for the Activity_method_realization.

name: the word or group of words by which the realization is known.

description: the text that provides further information about the manner in which the Activity_method is realized by the item. The value of this attribute need not be specified.

activity_method: the Activity_method for which further specification is being provided.

realized_by: the item that realizes the Activity_method.

EXAMPLE 2   A plan, schedule, or task description may realize the activity method.

NOTE 2   More than one such item can be associated with the activity.

4.3.2 Activity_method_realization_relationship   EXPRESS-GMapping table

An Activity_method_realization_relationship is a relationship between two Activity_method_realization entity instances.

NOTE    An Activity_method_realization_relationship may be used to specify sequencing and other constraints between different realizations for the same Activity_method.

EXPRESS specification:

*)
ENTITY Activity_method_realization_relationship;
  id : STRING;
  name : STRING;
  description : OPTIONAL STRING;
  relating : Activity_method_realization;
  related : Activity_method_realization;
END_ENTITY;
(*

Attribute definitions:

id: an identifier for the relationship.

name: the word or group of words by which the relationship is known.

description: the text that provides further information about the relationship. The value of this attribute need not be specified.

relating: one instance of Activity_method_realization that is a part of the relationship.

related: the other instance of Activity_method_realization that is a part of the relationship. If one Activity_method_realization in the relationship is dependent upon the other, this attribute shall be the dependent one.



*)
END_SCHEMA;  -- Activity_method_implementation_arm
(*


© ISO 2004 — All rights reserved