| Categorized Class |
BehaviorA Behavior is an Operating Asset that describes any action or reaction of an Agent to external or internal Behavioral Events. Behaviors include Action Processes (action), Interaction Processs (stories) or interactions (Service Interface). The course of actions of a Behavior is constrained ( Rule Enforcement) by the application of Behavioral Rules that define what is allowed and not allowed to do. |
|---|
| Name | Description |
|---|---|
Action Process |
An Action Process is a Behavior that describes a typical course of action intended to produce Outcome Events, through the involvement of Agents as Active Participants. During its course of action, a process consumes or produces Functional Assets, including Information Assets. 1) It may memorize or access Information Assets from and to its Process Stores. 2) It may receive Functional Assets at its boundary: Outcome Consumptions. 3) It may signal the production of Functional Assets at its boundary: Outcome Productions. The course of actions of a Action Process is constrained ( Rule Enforcement) by the application of Behavioral Rules that define what is allowed and not allowed to do. Within SysFEAT, we can examine Action Processes from two distinct perspectives: a) A conceptual standpoint is provided by Value Streams. b) A concrete implementation standpoint is provided by Resource Action Processes. |
Interaction Process |
An Interaction Process is a story (Behavior) that describes how the components of an Agent interacts to produce and consume Outcome Events. This includes: 1) A course of events represented by Object Flows depicting the succesion of intermediate Outcome Events towards the production of the final Outcome Events. 2) Interacting Agents who participate to the story. |
Service Interface |
A Service Interface is an interaction Behavior that describes a typical course of Flow Connections, coordinated by Behavioral Events and Outcome Events, and intended to produce Outcomes through the involvement of Agents. |