Succession in the Business Process Definition MetaModel namespace.
Immediate Succession in the Business Process Definition MetaModel namespace.
Behavior Steps is a kind of Happening Part which typed is a Behavior. This enables it to "invoke" other Behavior and to build Behavior composites (made of sub- Behaviors).
A Behavior Step Group is a kind of Part Group that is also a Behavior Step typed by the Behavior Occurrence in user models (M1). This gives a group of Behavior Steps as a whole the capacity to produce start and end changes playing the standard Event Part, such as Start and End.
For example, most process languages have a way of modeling sub-processes without defining a separate process. This is a Behavior Step Group.
A Behavior is a kind of Course that order happenings in time, as in the activities of a process model and or the interactions in a choreography.
Behavior introduces capabilites shared by both choreography and orchestration:
Its steps are typed by Courses which provide them with start/end capabilities
As a Course it can organize its part with Succession. It adds the ability to order its steps according to their start and ends (Succession).
Rich connections can be establish between its steps to enable time sychronization between them (Compound Behavioral Connection).
The reuse of the same Behavior is enabled by (Behavior Step).
Detection of events in conditions, such as time events, Fact Changes, or Course Events can be to influence its course (Event Monitor)
Its steps can be organize in groups to which start/end constraints can be applied (Behavior Step Group)
A Bindable Connection is a kind of Part Connection defined just to categorize those connections that can carry Connected Part Binding.
A Race Connection is a kind of Compound Behavioral Connection which has for compound connection type the Racing Behavior.
The Racing Behavior ensures that all the connected Behavior Step start at the same time, and that the first one to finish aborts the others.
A Compound Behavioral Connection is a Part Connection that enables dedicated lifecycle rule connections to apply between Behavior Steps. These rules are described by the compound connection type of the Compound Behavioral Connection, which is itself a Behavior.
This makes Compound Behavioral Connection be itself a Typed Part.
Behavior Event Conditions are Event Conditions for detecting Events in Courses, for example the start and ending of a Course.
It specifies the conditioning behavior step , such as a step in a process or interaction in choreography, and the conditioning event part , such as the Event Part for starting and ending (see the Happening and Event Model).
A Behavior Event Condition can be the condition for an Event Monitor, enabling detection of the starting and ending of Courses identified by Behavior Steps. For example, a Behavior Event Condition can refer to a message and the Normal End in it to specify that the message has arrived (The Business Process Definition MetaModel represents messages as process steps themselves, see Interactive Behavior Model).
A Group Abort Connection is a kind of Compound Behavioral Connection which has for compound connection type the Group Abort Behavior, an M1 instance of Behavior defined in the Behavior Library user (M1) library.
It is applied to Behavior Step Groups and their enclosed steps to ensure that the steps are aborted when the group is. (See more details in Group Abort Behavior).
An Event Monitor is a kind of Behavior Step that monitors the occurrence of an Event Condition and that has an effect on the course of a Behavior. For instance, an Event Monitor can be used to react to the Abort Event of a specific Course.
A Connected Part Binding is an Element specifying that individuals playing the part at an end of a Part Connection also play a Part within the connection. For example, one of the interactions between businesses in a choreography might be a subchoreography composed of many communications between the businesses. Businesses playing a particular role in the larger choreography also play one of the roles in the subchoreography.
The player is part of the composite owning the bindable connection. The played is part of the bindable connection. The binding requires the (M0) individuals playing these parts to be the same. They are found by navigating from an individual composite, to the player individuals, and to the played individuals in the connection part of the same composite. The two sets of individuals found this way must be exactly the same.
Connected Part Binding is different from Part Connection because part bindings are about which individuals are playing certain parts in a whole, whereas connections are about links between the individuals themselves due to playing parts in the whole. As a convenience, it is assumed that a connection typed by a composite that has only one (non-connection) part implies bindings where that one part is played by all the parts at all the ends of the connector. This is useful for symmetrical connectors.