AP scope | AP module | AP contents | AP index | |
Application module: Issue management | ISO/WD 10303-1489 |
This clause specifies the information requirements for the Issue management 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 Issue_management_arm schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Issue_management_arm;
(*
The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Activity_arm;
--
ISO/TS 10303-1047
USE FROM
Activity_as_realized_arm;
--
ISO/TS 10303-1259
USE FROM
Approval_arm;
--
ISO/TS 10303-1012
USE FROM
Identification_assignment_arm;
--
ISO/TS 10303-1021
USE FROM
Issue_arm;
--
ISO/WD 10303-1490
USE FROM
Work_order_arm;
--
ISO/TS 10303-1043
USE FROM
Work_request_arm;
--
ISO/TS 10303-1042
(*
NOTE 1 The schemas referenced above are specified in the following part of ISO 10303:
Activity_arm ISO/TS 10303-1047 Activity_as_realized_arm ISO/TS 10303-1259 Approval_arm ISO/TS 10303-1012 Identification_assignment_arm ISO/TS 10303-1021 Issue_arm ISO/WD 10303-1490 Work_order_arm ISO/TS 10303-1043 Work_request_arm ISO/TS 10303-1042
NOTE 2 See Annex C, Figures C.1and C.2 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 issue_activity_item type is an extension of the activity_item type. It adds the data type Issue 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
issue_activity_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT
BASED_ON
activity_item
WITH
(Issue);
END_TYPE;
(*
The issue_approval_item type is an extension of the approval_item type. It adds the data types Activity_actual, Work_order and Work_request 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
issue_approval_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT
BASED_ON
approval_item
WITH
(Activity_actual,
Work_order,
Work_request);
END_TYPE;
(*
The issue_identification_item type is an extension of the identification_item type. It adds the data type Disposition 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
issue_identification_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT
BASED_ON
identification_item
WITH
(Disposition);
END_TYPE;
(*
This subclause specifies the ARM entity for this module. The ARM entity is an atomic element that embodies a unique application concept and contains attributes specifying the data elements of the entity. The ARM entity and definition is specified below.
NOTE 1 A Disposition will normally reference both the Work_order or Work_request in the role of "subject", and the Activity_actual at which the disposition was made, here in the role of "disposing action".
NOTE 2 Where a meeting decides the disposition of several issues, an Activity_actual would provide the record of each individual disposition, and a collector Activity_actual would define the overall meeting parameters, such as the date and the attendance list.
EXPRESS specification:
*)
ENTITY Disposition
SUBTYPE OF (Approval);
name : STRING;
END_ENTITY;
(*
Attribute definitions:
name: the words by which the Disposition is known.
*)
END_SCHEMA; -- Issue_management_arm
(*
© ISO — All rights reserved