Application module: System behaviour ISO/TS 10303-1448:2011-10(E)
© ISO

Cover page
Table of contents
Copyright
Foreword
Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
    3.1 Terms and definitions
    3.2 Abbreviated terms

4 Information requirements
   4.1 Required AM ARMs
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
F Application module implementation and usage guide
G Change history
Bibliography
Index

Annex F
(informative)

Application module implementation and usage guide

Behaviour is the dynamic response to excitation of an engineering thing. The emergent properties of the associated response can be either dynamic, what it does in response to excitation, or static, associated with its composition and structure. Behaviour is the subclass of emergent property. It includes what it does in response to excitation and excludes static properties.

Function Based Behaviour and State Based Behaviour are two different and complimentary views of what a system is to do in response to excitation. Each has advantages for modelling particular problems and engineers have personal preferences about the two representations.

State Based Behaviour is a representation of what a system is to do based on descriptions of its relevant characteristics or conditions at particular intervals. What a thing does can be described by citing a set of significant conditions.

Function Based Behaviour is a representation of what a system is to do based on descriptions of the transformations it performs. What a thing does can be described by citing a set of significant transformations it performs. In science and engineering all changes can be represented by transformations that follow well known transformation laws like conservation of matter and energy.

NOTE    There are no type extends lists placed in this module. The reason for this is that the modelling paradigms of Function Based and State Based Behaviour are very different and hence are rarely used in a closely coupled manner at the abstraction level of "system behaviour". All necessary type extends are placed in the respective Function Based and State Based Behaviour modules.



© ISO 2011 — All rights reserved