Building a Model with Elementary Components

Splitter Component

The transaction entering the Splitter leaves down all arcs away from the splitter. A single instance of the transaction leaves the Splitter multiple times so it is in multiple places at once. It appears that these are multiple copies but they all refer to the same transaction instance. This means that any change to the transaction can be detected in multiple places in the model. This is the same behavior as with a Port or Connector. The additional behavior that is provided by the Splitter comes when an "Are You Busy" message is sent to it. This behavior differs from both the Port and Connector.

The following list documents the logic of the Splitter component.

Transaction Arrival

The transaction flows down each arc directed away from the component.

Request for Transaction

If none of the components on arcs directed out of the Splitter is busy, then pass on the request to all components on arcs leading into the Splitter; else, deny the request.

Are You Busy Message

If any of the components on arcs directed out of the Splitter is busy, then return TRUE; else, return FALSE.

Query Message

Trigger Message