AP scope  |  AP module  |  AP contents  |  AP index
Application module: Product view definition ISO/TS 10303-1019:2006(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 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 Product view definition 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 Product_view_definition_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Product_view_definition_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 Product_version_arm;    --  ISO/TS 10303-1018
(*

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

Product_version_arm ISO/TS 10303-1018

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 Product_view_definition   EXPRESS-GMapping table

A Product_view_definition is a characterization of a Product_version, relevant in one or more application domains and for one or more life cycle stages.

A Product_view_definition is a collector of the properties that characterize the Product_version in the initial_context and additional_contexts.

EXAMPLE 1   The design of the SS Titanic and the as-built description of the SS Titanic can be represented as two instances of Product_view_definition.

EXPRESS specification:

*)
ENTITY Product_view_definition;
  id : OPTIONAL STRING;
  name : OPTIONAL STRING;
  additional_characterization : OPTIONAL STRING;
  initial_context : View_definition_context;
  additional_contexts : SET[0:?] OF View_definition_context;
  defined_version : Product_version;
WHERE
  WR1: NOT (initial_context IN additional_contexts);
  WR2: EXISTS(id) OR (TYPEOF(SELF\Product_view_definition) <> TYPEOF(SELF));
END_ENTITY;
(*

Attribute definitions:

id: the identifier that distinguishes the Product_view_definition.

NOTE    The value of this attribute may be an empty string.

name: the words by which the Product_view_definition is known. The value of this attribute need not be specified.

NOTE 1   This attribute is mapped onto description for compatibility with pre-existing application protocols.

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

NOTE 2   This attribute may be used to precise the kind of definition.

EXAMPLE 2   In case the Product_view_definition characterizes a mating, this attribute may identify the kind of mating. 'clipping', 'welding' are examples of additional_characterization for a mating definition.

initial_context: the View_definition_context in which the defined_version has been primarily characterized by the Product_view_definition .

additional_contexts: the set of instances of View_definition_context in which this Product_view_definition is also relevant.

defined_version: the Product_version of which the Product_view_definition provides a characterization.

Formal propositions:

WR1: The additional_contexts shall not contain the instance of View_definition_context that is referenced as the initial_context.

WR2: If SELF is exact instance of Product_view_definition, then id shall be provided.

4.2.2 View_definition_context   EXPRESS-GMapping table

A View_definition_context is the grouping of an application domain and a life cycle stage. It identifies a universe of discourse suitable for the description of products.

NOTE    Requirements and vocabularies vary among the industrial activity fields. This entity intends to identify such a domain.

EXPRESS specification:

*)
ENTITY View_definition_context;
  application_domain : STRING;
  life_cycle_stage : STRING;
  description : OPTIONAL STRING;
WHERE
  WR1: (SIZEOF (USEDIN(SELF, 'PRODUCT_VIEW_DEFINITION_ARM.' + 'PRODUCT_VIEW_DEFINITION.INITIAL_CONTEXT')) > 0) OR (SIZEOF (USEDIN(SELF, 'PRODUCT_VIEW_DEFINITION_ARM.' + 'PRODUCT_VIEW_DEFINITION.ADDITIONAL_CONTEXTS')) > 0);
END_ENTITY;
(*

Attribute definitions:

application_domain: the text that identifies the application context that bounds the universe of discourse.

EXAMPLE 1   'assembly study', 'digital mock-up', 'electrical design', 'mechanical design', 'preliminary design', 'process planning' are examples of application domains

If application_domain is an empty string, the View_definition_context shall be considered as not specific of any application domain.

life_cycle_stage: the text that identifies a stage in the life cycle of a product.

EXAMPLE 2   'design phase', 'production', 'recycling phase' are examples of life cycle stages.

If life_cycle_stage is an empty string, the View_definition_context shall be considered as not specific of any life cycle stage.

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

Formal propositions:

WR1: A View_definition_context has to be referenced by at least one Product_view_definition in the role initial_context or additional_contexts.

Informal propositions:

IP1: application_domain and life_cycle_stage shall not be both no-word strings.



*)
END_SCHEMA;  -- Product_view_definition_arm
(*


© ISO 2006 — All rights reserved