AP scope  |  AP module  |  AP contents  |  AP index
Application module: Requirement assignment ISO/TS 10303-1233: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 ARM
   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
     5.2.2 MIM entity 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 Requirement assignment 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 Requirement_assignment_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Requirement_assignment_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 Requirement_view_definition_arm;    --  ISO/TS 10303-1141
(*

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

Requirement_view_definition_arm ISO/TS 10303-1141

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 requirement_assignment_item   EXPRESS-G

The requirement_assignment_item type is an extensible list of alternate data types. Additional alternate data types are specified in select data types that extend the requirement_assignment_item 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 requirement_assignment_item = EXTENSIBLE SELECT;
END_TYPE;
(*

4.2.2 requirement_source_item   EXPRESS-G

The requirement_source_item type is an extensible list of alternate data types. Additional alternate data types are specified in select data types that extend the requirement_source_item 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 requirement_source_item = 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 Requirement_assignment   EXPRESS-GMapping table

A Requirement_assignment is used to relate a requirement (via the Requirement_view_definition entity) to data types representing the items which are affected by the requirement.

EXAMPLE    A requirement "the vehicle shall have a maximum power output of at least 150BHP" could be assigned to the data types which are used to represent the vehicle's engine.

EXPRESS specification:

*)
ENTITY Requirement_assignment;
  id : STRING;
  description : OPTIONAL STRING;
  assigned_requirement : Requirement_view_definition;
  assigned_to : requirement_assignment_item;
END_ENTITY;
(*

Attribute definitions:

id: an identifier that distinguishes the Requirement_assignment.

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

assigned_requirement: the Requirement_view_definition which is assigned.

assigned_to: the item which has the requirement assigned to it.

4.3.2 Requirement_source   EXPRESS-GMapping table

A Requirement_source is a relationship between a requirement (via the Requirement_view_definition entity) and the data types representing the source of the requirement

EXAMPLE    The source of the requirement "the vehicle shall have a maximum power output of at least 150BHP" could be a document representing the findings of a market survey of sports car buyers.

EXPRESS specification:

*)
ENTITY Requirement_source;
  id : STRING;
  description : OPTIONAL STRING;
  source : requirement_source_item;
  sourced_requirement : Requirement_view_definition;
END_ENTITY;
(*

Attribute definitions:

id: the identifier that distinguishes theRequirement_source.

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

source: the item which is the source of the requirement.

sourced_requirement: the requirement which is to be related to its source.



*)
END_SCHEMA;  -- Requirement_assignment_arm
(*


© ISO 2004 — All rights reserved