-
Notifications
You must be signed in to change notification settings - Fork 0
System Output
Conditions or occurrences that we observe in the System are considered system outputs.
Typically, we are only interested in selected outputs occurring in some anticipated sequence which is why we model these as Interactions. From the Elevator Case Study, we might be interested in the following output:
EVMAN >|| UI : XFER<S1> Set destination( Floor=3 )
Here we have an Action Type external event (as indicate by the >|| symbol) with a source Actor named EVMAN:XFER<S1> (an instance of XFER in the EVMAN domain) and an Output Target UI (the UI domain).
The Interaction name is Set destination (the external event name) and there is one Supplied Parameter Floor with the value 3.
When (and if!) the System issues this external event, in the specified Interaction sequence OR10, appropriate debugger action will be taken (most likely just recording and or announcing the occurrence and moving on to the next Interaction).
- Number
No non-referential attributes.
Copyright © 2025-2026, Leon Starr at Model Integration, LLC under the MIT Open Source License