Flow is a composite activity. A flow can extend another flow and inherit its elements, which it can override or suppress.

Flow extension/inheritance can be used to define generic flows at higher levels of an organization and specialize them at lower levels. Base flows can also be defined by standard bodies and flows can be organized into a “Flow continuum”, similar to TOGAF’s Enterprise Continuum. Flows can be defined as abstract and contain abstract elements, i.e. placeholder elements which specify what needs to be done, but not how. Abstract elements must be overridden or suppressed in concrete flows.

Flows can also specify final elements which cannot be overridden. It can be used to enforce decision authority, e.g. if some activity must be done in one particular way for regulatory or legal reasons then that activity would be defined as final at the higher levels of the organization to prevent overriding at lower levels.

Flows also can be defined as final, i.e. they cannot be extended. Note that a final abstract flow makes no sense.

Supertypes

Subtypes

Uses

  • Flow

If true, this flow shall be displayed as a partition on the parent flow diagram.

Type EBoolean
Cardinality 0..1
Changeable true
Derived false

Elements of this flow.

Type FlowElementEntry
Cardinality 0..*
Changeable true
Derived false