Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

A SysML Operational Domain Model

Systems engineering is an interdisciplinary field of engineering that takes a whole-of-system view of a problem and its solution. The operational domain model is a central part of any model-based approach and describes the system in the context of its environment. This includes the humans that are intended to operate and interact with the system, external objects that might influence the system, and environmental elements that could impact the system. The operational domain model is a useful starting point to get an overview of a system and how it will operate.

Enterprise Architect provides a range of features that help the engineer to construct an operational domain model, including standard SysML block definition and Internal Block diagrams, and the ability to include pictorial representations of elements that make the diagrams more compelling. The elements can also be hyper-linked, enabling the viewer to use a diagram as a launching pad to more detailed models and diagrams.

The SysML Operational Domain Model defines the system's operating environment, which describes the operating conditions that the system is intended to operate within. This diagram shows an example Operational Domain model for a Portable Audio Player; the SysML Block Definition Diagram describes the Operational Domain (in this example - the ListeningDomain) as a system composition.

In the example, the ListeningDomain is defined as a system containing other subsystems; the domain contains subsystems that define the Listener (that is, User), the Portable Audio Player, Clothing (which the user wears), and the External Environment.

Details of the ListeningDomain system are further detailed in the ListeningDomain's Internal Block Diagram:

In the example, the ListeningDomain system's detailed composition shows how the Portable Audio Player and other sub-systems fit together to form the Listening Domain; it also describes the binding relationships between the parts, which define how the parts are functionally bound to one another.