AP scope  |  AP module  |  AP contents  |  AP index
Application module: Transformation input output ISO/WD 10303-1454

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 definition
   4.3 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 input output 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_input_output_arm schema and identifies the necessary external references.

The concept of function is the transformation of a set of inputs into a set of outputs. In chemistry inputs of oxygen and hydrogen are transformed by chemical reaction to produce water and heat. An electric power generation station transforms chemical energy to heat energy, heat energy to mechanical energy, mechanical energy to electrical energy, and electrical energy to the correct voltage level synchronized with the power grid. The concept of transformation is basic to science and engineering. In the EXPRESS modules, the word (Function) is not allowed as an entity name because of EXPRESS constraints. Instead the word (Transformation) is used as a synonym.

Several transformations may share a single resource such as bandwidth or computer memory. This Transformation_input_output_arm module both defines the entities needed to support and assess resource utilization by behavior execution.



Figure 1 —  Concept Model Slide 11

Figure 1 —  Concept Model Slide 11



Figure 2 —  Concept Model Figure 3

Figure 2 —  Concept Model Figure 3



Figure 3 —  Concept Model Figure 1

Figure 3 —  Concept Model Figure 1



Figure 4 —  Concept Model Slide 14

Figure 4 —  Concept Model Slide 14



Figure 5 —  Concept Model Figure 4

Figure 5 —  Concept Model Figure 4

NOTE    This module provides elements necessary for the representation of the upper left quadrant of Concept Model - Function Based Behavior Figure 4. Definitions used herein are extracted from the terminology dictionary of the Concept model and pointed to by the number codes shown in Figure 4.

Issue - The attribute , is a stub. It is from this point that we will need to spawn to transformation model detail. This may be anything form a simple logic or algebraic statement to a fully detailed analysis to some physical test model integrated into a large system behavior model.

EXPRESS specification:

*)
SCHEMA Transformation_input_output_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 Input_output_arm;    --  ISO/WD 10303-1459

USE FROM Transformation_arm;    --  ISO/WD 10303-1463
(*

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

Input_output_arm ISO/WD 10303-1459
Transformation_arm ISO/WD 10303-1463

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

4.2 ARM type definition

This subclause specifies the ARM type for this application module. The ARM type and definition is specified below.

4.2.1 i_o_queue   EXPRESS-G

A i_o_queue is a storage entity on a Input_port that accumulates Input_output_view_definition until needed by the function

EXPRESS specification:

*)
TYPE i_o_queue = ENUMERATION OF
   (fifo,
    lifo,
    priority,
    reverse_priority);
END_TYPE;
(*

Enumerated item definitions:

fifo: a fifo is a type of i_o_queue that uses a first in first out order release algorithm.

lifo: a lifo is a type of i_o_queue that uses a last in first out order release algorithm.

priority: a priority is a type of i_o_queue that uses a priority order release algorithm.

reverse_priority: a reverse_priority is a type of i_o_queue that uses a reverse priority order release algorithm.

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

A Script_language_reference is the computer sensible language used to define the Transformation_view_definition. ############# There's a better way to capture this and Script ######

EXPRESS specification:

*)
ENTITY Script_language_reference;
  citation : STRING;
  language_identification : Transformation_view_definition;
END_ENTITY;
(*

Attribute definitions:

citation: the name of the scripting language; e.g., Tcl, C++, MathML, etc. Transformation_view_definition.

language_identification: the Transformation_view_definition. that uses the Script_language_reference.

4.3.2 Script   EXPRESS-GMapping table

A Script is the actual executable code that defines the Transformation_view_definition. This is used to provide detail control of function transformation ordering. ############# There's a better way to capture this and Script_language_reference ######

EXPRESS specification:

*)
ENTITY Script;
  description : OPTIONAL STRING;
  transformation_control : Transformation_view_definition;
END_ENTITY;
(*

Attribute definitions:

description: the coded string which is the Script. The value of this attribute need not be specified. Reason: it is not required to define every Transformation_view_definition.

transformation_control: the Transformation_view_definition. that is defined the Script

4.3.3 Output_port   EXPRESS-GMapping table

An Output_port is an exit point for what is generated by the Transformation_view_definition

EXPRESS specification:

*)
ENTITY Output_port;
  generated_through : Input_output_view_definition;
  output_transformation_port : Transformation_view_definition;
END_ENTITY;
(*

Attribute definitions:

generated_through: that which is generated by the Transformation_view_definition

output_transformation_port: the Transformation_view_definition which is the output generator

4.3.4 Input_port   EXPRESS-GMapping table

A Input_port is an entry point for what is consumed by the Transformation_view_definition

EXPRESS specification:

*)
ENTITY Input_port;
  id : STRING;
  consumed_through : Input_output_view_definition;
  input_transformation_port : Transformation_view_definition;
  queue_type : i_o_queue;
END_ENTITY;
(*

Attribute definitions:

id: the identifier for the Input_port.

consumed_through: that which is consumed by the Transformation_view_definition

input_transformation_port: the Transformation_view_definition which is the input consumer.

queue_type: identification of the i_o_queue to be used at the Input_port

4.3.5 Control_port   EXPRESS-GMapping table

A Control_port is a type of Input_port that does triger the function.

EXPRESS specification:

*)
ENTITY Control_port
  SUBTYPE OF (Input_port);
END_ENTITY;
(*

4.3.6 Regular_port   EXPRESS-GMapping table

A Regular_port is a type of Input_port that does not triger the function.

EXPRESS specification:

*)
ENTITY Regular_port
  SUBTYPE OF (Input_port);
END_ENTITY;
(*



*)
END_SCHEMA;  -- Transformation_input_output_arm
(*


© ISO — All rights reserved