Most inter-tool data transfer standards deal with protocol and syntax of the transfer, with a shared semanticbasis assumed. This standard provides an explicitly defined metamodel (and meta-metamodel) forspecifying system and software behavior. It defines a semantic basis of observables that allows each tool,whatever its own internal ontology, to communicate facts about the behavior of a subject system asprecisely as the tool s metamodel allows. Conventional tool model elements are reduced into simpler,directly observable fact statements about system behavior. This metamodel is much expanded over theoriginal metamodel for software behavior in Part 3 of IEEE Std 1175(TM)-1991.
Purpose
This reference model provides a common interpretation basis by which tools may express andcommunicate the observable features of system/software behavior to users and to other tools. Toolsincorporating this metamodel in their import/export facilities enable engineers to interconnect best-in-classanalysis and specification tools for integrated problem solving. Another feature of this metamodel is that it provides a specification that is directly testable. Finally, the provision of an explicit meta-metamodelenables tool builders to extend the reference metamodel for particular purposes.
Abstract
New IEEE Standard - Active.The reference model that provides a common interpretation basis by which tools can express and communicate the observable features of system/software behavior to users and to other tools is presented in this standard. This standard specifies a conceptual metamodel for understanding and describing the causal behavior for a system. The purpose of this conceptual metamodel is to express causal behavior and compositions of causal behavior in a model that integrates all observable operational features of a system into one behavior specification. This conceptual metamodel is useful for analyzing systems, for constructing particular system behavior models, and for using those models in the specification, design, and evaluation of engineered systems. It provides the necessary semantic elements for describing general hardware/software systems, including hardware-only, software-only, or mixed system components, and it allows these different types of components to be treated in a consistent manner, providing a basis for representing a wide variety of systems.
