AP scope  |  AP module  |  AP contents  |  AP index
Application module: System modelling ISO/WD 10303-1477

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 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

Introduction

ISO 10303 is an International Standard for the computer-interpretable representation of product information and for the exchange of product data. The objective is to provide a neutral mechanism capable of describing products throughout their life cycle. This mechanism is suitable not only for neutral file exchange, but also as a basis for implementing and sharing product databases, and as a basis for archiving.

This part of ISO 10303 specifies an application module for the representation of the variety of general model classifications used to support model-based systems engineering. This includes all models used to characterize the physical structure and its behavior and the full range of models used to support system engineering trade studies.

This module is one of AP233's two top level modules. Its focus is on the variety of modeling paradigms used to represent the physical and functional system along capabilites used to support associated verification, validation and trade studies. It links to but does not include capabilities that support the managment activities of systems engineering.

Begin - Notes from SC4 Meeting in Hangzhou and post meeting email exchanges

There is an accepted need and desire to insure that AP233 and SysML work together to the greatest degree posssible. Much of the capability provided via SysML can be logically viewed as belonging within the scope of this module. In a sense, this is where SysML meets Configuration Management. Detail is under development.

Re: "Analysis"

Decision-making is an integral part of any systems engineering activity. Decisions are assumed to be rational (what, why, how). They are made by people and organizations; somewhere, and at some point in time (who, when, where). The proposed concept model seeks to provide the basic the network of concepts and relationships necessary for the representation and exchange of all computer sensible information associated with the systems engineering decision-making process. Within this context; "analysis" supports decision making. An associated concept model is available at:. http://www.ap233.org/Concept%20Model/Analysis%20and%20Decision-making/Analysis%20and%20decision%20making%20Draft%20%238-1.pdf. This model has been reviewed at several 2005 AP233 meetings. It is presently under more careful in depth review by members of the Vivace Project under the leadership of Phil Spiby and Mats Lindeblat.

It is presently expected that capabilities necessary to enable "analysis" representation, within AP233, as it supports system engineering decision making will placed in this module.

End - Notes from SC4 Meeting in Hangzhou and post meeting email exchanges

Clause 1 defines the scope of the application module and summarizes the functionality and data covered. Clause 3 lists the words defined in this part of ISO 10303 and gives pointers to words defined elsewhere. The information requirements of the application are specified in Clause 4 using terminology appropriate to the application. A graphical representation of the information requirements, referred to as the application reference model, is given in Annex C. Resource constructs are interpreted to meet the information requirements. This interpretation produces the module interpreted model (MIM). This interpretation, given in 5.1, shows the correspondence between the information requirements and the MIM. The short listing of the MIM specifies the interface to the resources and is given in 5.2. A graphical representation of the short listing of the MIM is given in Annex D.

In this International Standard, the same English language words may be used to refer to an object in the real world or concept, and as the name of an EXPRESS data type that represents this object or concept.

The following typographical convention is used to distinguish between these. If a word or phrase occurs in the same typeface as narrative text, the referent is the object or concept. If the word or phrase occurs in a bold typeface or as a hyperlink, the referent is the EXPRESS data type.

The name of an EXPRESS data type may be used to refer to the data type itself, or to an instance of the data type. The distinction between these uses is normally clear from the context. If there is a likelihood of ambiguity, either the phrase "entity data type" or "instance(s) of" is included in the text.

Double quotation marks " " denote quoted text. Single quotation marks ' ' denote particular text string values.



© ISO — All rights reserved