UML.Semantic.BehavioralElements.StateMachines
Class ActivityModel

java.lang.Object
  |
  +--UML.Semantic.Foundation.Core.ModelElement
        |
        +--UML.Semantic.BehavioralElements.StateMachines.StateMachine
              |
              +--UML.Semantic.BehavioralElements.StateMachines.ActivityModel

All Implemented Interfaces:

Element, ElementAtt, LinkAtt

public class ActivityModel

extends StateMachine

An activity model is a special case of a state machine that defines a computational process in terms of the control-flow and object-flow among its constituent actions. It does not extend the semantics of state machines but it does define shorthand forms that are convenient for modeling computational processes.

The primary basis for ActivityModels is to describe a state model of an activity or process involving one or more Classifiers. ActivityModels can be attached to Packages, Classifiers (including UseCases) and BehavioralFeatures. Most of the States in an activity model are ActionStates, i.e., states in which an action is being performed, typically the execution operations. As in any state machine, if an outgoing transition is not explicitly triggered by an event then it is implicitly triggered by the completion of the contained actions. An ActivityState represents structured subactivity that has some duration and internally consists of a set of actions. That is, an ActivityState is a “hierarchical action” with an embedded activity submodel that ultimately resolves to individual actions.

Ordinary “wait states” can be included to model situations in which the computation waits for an external event. Branches, forks, and joins may also be included to model decisions and concurrent activity.

ActivityModels include the concept of Partitions to organize states according to various criteria, such as the real-world organization responsible for their performance.

Activity modeling can be applied in the context of organizational modeling for business process engineering and workflow modeling. In this context, events often originate from ‘outside’ the system (e.g. ‘customer call’). Activity models can also be applied to system modeling to specify the dynamics of operations and system level processes when a full interaction model is not needed.

Constructor Summary

ActivityModel()

Method Summary

boolean

check() Checks if well-formedness rules are respected in this model element.

Methods inherited from class UML.Semantic.BehavioralElements.StateMachines.StateMachine

add, getTop, getTransitions, setTopState

Methods inherited from class UML.Semantic.Foundation.Core.ModelElement

add, add, getBindingList, getConstraintList, getElementType, getErrors, getHref, getId, getIdentification, getIdref, getIndex, getInfo, getIsOwned, getLabel, getLocator, getName, getNamespace, getNamespaceId, getStereotype, getTemplate, getTemplateParameterList, getTitle, getUuid, getUuidref, getVisibility, getVisibilitySymbol, getWarnings, setElementType, setErrors, setHref, setId, setIdref, setIndex, setIsOwned, setLabel, setName, setNamespace, setTemplate, setTitle, setUuid, setUuidref, setVisibility, setWarnings

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ActivityModel

public ActivityModel()

Method Detail

check

public boolean check()

Checks if well-formedness rules are respected in this model element.

Overrides:

check in class StateMachine

Returns:

True if check was successful, false otherwise.