Necessity – SCA Components

The components of Service Component Architecture (SCA) are defined by interaction with other components within the same digital twin or in different digital twins. And, software implements the services for each interaction.

Finding and Examining a Domain of Actors

Here is an example of SCA in the Otter Demo showing all the domains having SCA components:

By hovering over the PizzaStoresSCA domain, the visual changes to show more detail about this domain:

Then by selecting the PizzaStoresSCA domain, the SCA components within the domain are shown:

Any of the components may be selected for a closer examination. For this example, by hovering over the SimComponent, more detail is shown about this component:

Actors and Assemblies

Then by selecting the SimComponent, an SCA assembly of components is shown:

In this case, the assembly shows that five components will dialog in this component. A component is formed by the assembly of two or more components. Each component can be prompted for dialog as shown by the green connections on the left side of the components. A component can also initiate dialog by prompting another component’s service. Initiation of a dialog is shown as a purple arrow on the right side of the component. Each prompted dialog receives a response for the requested service. The dialog connections are shown by the arrows.

By selecting the ContractsServices component, only the component is shown:

This view shows the dialogs that may be prompted by another component’s service, as well as those that may be a prompt for another component’s service. The details of the expectation of the dialog is given by buttons below the dialog. In this example, the OrderFromMenu prompt is examined. When selected, the first button on the left shows the logic graph needed to be prompted in the form of a Service Data Object. The logic graph includes the named objects required by the logical graph’s metadata.

The second button, when selected, shows the logic graph of named objects expected to be received from the prompted actor. This logic graph is also in the form of a Service Data Object:

Navigation Summary