AP scope  |  AP module  |  AP contents  |  AP index
Application module: Transformation ISO/WD 10303-1463

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 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 Transformation 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 Transformation_arm schema and identifies the necessary external references.

EXPRESS specification:

*)
SCHEMA Transformation_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 Product_identification_arm;    --  ISO/TS 10303-1017

USE FROM Product_version_arm;    --  ISO/TS 10303-1018

USE FROM Product_view_definition_arm;    --  ISO/TS 10303-1019

USE FROM Product_view_definition_relationship_arm;    --  ISO/TS 10303-1041
(*

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

Product_identification_arm ISO/TS 10303-1017
Product_version_arm ISO/TS 10303-1018
Product_view_definition_arm ISO/TS 10303-1019
Product_view_definition_relationship_arm ISO/TS 10303-1041

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

An Transformation is a type of Product. It is a specification for the transformation associated with a model used for response to excitation analysis. It is executable in tools that enable the development of a time line that can be used for the discovery and recording of logical errors that would inhibit as-required system execution.

EXPRESS specification:

*)
ENTITY Transformation
  SUBTYPE OF (Product);
END_ENTITY;
(*

4.2.2 Transformation_version   EXPRESS-GMapping table

A Transformation_version is a type of Product_version that identifies a particular version for the transformation associated with such a model.

NOTE    This entity is used to record different versions of transformation. In this case, the word "version" implies "revision" - that is a particular release of transformation for a function based behavior model.

NOTE    The inherited "of_product" attribute has been renamed for purposes of clarity.

EXPRESS specification:

*)
ENTITY Transformation_version
  SUBTYPE OF (Product_version);
  SELF\Product_version.of_product RENAMED of_transformation : Transformation;
END_ENTITY;
(*

Attribute definitions:

of_transformation: the Transformation for which the Transformation_version identifies a version.

4.2.3 Transformation_view_definition   EXPRESS-GMapping table

A Transformation_view_definition is a type of Product_view_definition that provides a view of an transformation version relevant for one or more application domains. This view collects transformation data together for specific engineering purposes.

Some behavior models in a Transformation_view_definition might impact on different disciplines. Multiple Transformation_view_definition objects may be used to present different model based views of a given aspect of behavior transformation for each discipline.

EXPRESS specification:

*)
ENTITY Transformation_view_definition
  SUBTYPE OF (Product_view_definition);
  SELF\Product_view_definition.defined_version : Transformation_version;
  bounce : BOOLEAN;
END_ENTITY;
(*

Attribute definitions:

defined_version: the Transformation_version that the Transformation_view_definition defines.

bounce: bounce is used as an optional logical control flag within Transformation_view_definition. It supports the need for function based behavor execution tools to provide users with the the option to "bounce over" Transformation_view_definition detail.

NOTE    In application, executable models are hierarchial with complex detail. There is a an application need to skip (bounce over) work previously validated deep detail. The logical flag bounce is intended to provide for this tool supported run time application option.

4.2.4 Transformation_view_definition_relationship   EXPRESS-GMapping table

A Transformation_view_definition_relationship is a type of View_definition_relationship. It is an association between two instances of Transformation_view_definition.

This association represents a relationship between the transformation versions, indirectly identified by the instances of Transformation_view_definition, relevant in the definition contexts of the related instances of Transformation_view_definition.

EXPRESS specification:

*)
ENTITY Transformation_view_definition_relationship
  SUBTYPE OF (View_definition_relationship);
  SELF\View_definition_relationship.relating_view RENAMED parent : Transformation_view_definition;
  SELF\View_definition_relationship.related_view RENAMED child : Transformation_view_definition;
END_ENTITY;
(*

Attribute definitions:

parent: one of the instances of Transformation_view_definition

child: the other instance of Transformation_view_definition that is part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.



*)
END_SCHEMA;  -- Transformation_arm
(*


© ISO — All rights reserved