Chapter List

Part Overview

System-level design cannot be performed in a single engineering domain. By definition, system-level design integrates heterogeneous system views to predict effects of local decisions on system-level properties. These local decisions are made by domain specialists using the languages and semantics of their domains.

Part IV describes the Rosetta domain interaction systems used to define modeling domains and relationships between modeling domains. Domains describe units-of-semantics, models-of-computation, and engineering design domains by defining vocabulary and semantics used by domain experts. Interactions define how specifications in one domain relate to impact specifications in another. Domains provide the specialist's modeling languages while interactions compose them.

After completing the chapters in Part IV, you will understand how to use domains to define semantic models for facets, how domains are defined, how facets are composed, how functors, translators, and combinators define interactions, and how to use interactions to define system-level impacts of local design decisions.

Overview

The essence of systems engineering is the need to compose and understand specifications from multiple engineering domains. Because different engineering activities use different modeling vocabularies, any language purporting to be a system-level modeling language must support heterogeneous specification. More specifically, a system-level modeling language must support and integrate multiple modeling paradigms, models of computation, and communication models.

Rosetta's support for heterogeneous specification is embodied in domains and interactions. Domains provide a basic modeling vocabulary for a facet...