UML behavioral modeling

This article or section is a stub. It does not yet contain enough information to be considered a real article. In other words, it is a short or insufficient piece of information and requires additions.

Draft

UML behavioral modeling includes refers to a set of modeling languages

## Behavioral modeling in the UML architecture[edit | edit source]

The UML specification is fairly complex and its organisation is not so easy to understand. Within each UML part, the concepts are grouped into clauses according to modeling capability and that covers a specific modeling formalism. For instance, all concepts related to the state machine modeling capability are gathered in the State Machines clause and all concepts related to the activities modeling capability are in the Activities clause.

Part II - Behavior specifies the dynamic, behavioral constructs (e.g., activities, interactions, state machines) used in various behavioral diagrams:

* UML activity diagrams
* UML use case diagrams
* State machine diagrams
* Various interaction diagrams, i.e. sequence diagrams, communication diagrams, interaction overview diagram and timin diagram.

## Actions[edit | edit source]

Actions in the UML framework are "lower-level behaviors". The basic concept of activity and all other behavior diagrams are actions. "An action is the fundamental unit of behavior specification. An action may takes a set of inputs and may convert them into a set of outputs. Some of the actions modify the state of the system in which the action executes. The values that are the inputs to an action may be described by value specifications. (See UML, version 2.1.2)".

## UML activity metaclasses[edit | edit source]

UML defines activities with activity packages, each of which is modeled with aa UML class diagram. There several kinds of activity packages. (however, it is not clear to us whether these are really use in practice or whether they just represent a modular way to define languages).

1. Fundamental activities: defines activites as nodes that include actions
2. Basic activities: adds squencing (without forks/joins and decision)
3. Intermediate activities: Supports modeling of activity diagrams. Supports activity diagrams, e.g. includes dataflow, concurrent control and decision.
4. Complete activities: adds constraints such as edge weights
5. Structured activities: supports structured programming constructs and is compatible with intermediate and complete activities.
6. Complete structured activities: Adds support for data flow output pins os sequences, conditions and loops to structured activities.
7. Extra structured activities: Adds exception handling to structured activities.