Basic Flowchart and Cross-Functional Flowchart

Flowchart notations describe algorithm (script) of process performance and allow to specify cause and effect relationships and the time sequence of process steps. Each step can be decomposed. In addition to all the shapes that a Basic Flowchart has, Cross-functional Flowchart has a Swimlane shape that is used to display actors of process steps. An org unit or a functional object can be an actor. Table 1 contains description of the Flowchart notation elements.

Element Button Shape Description
Action An action is a box. Inside the box there is its name.
Decision Decision is used to represent branches. Use the Decision shape when you need to model selection of a further process step.
Decision either represents an action that leads to the selection of one of the further process steps or checks the condition.
When the Decision shape represents an action, all possible result options are modeled by the outgoing arrows (Figure 1).
Figure 1. Decision represents an action

When it is used to check the condition, then usually it follows an action on a diagram. The name of the Decision shape is the name of the condition. Outgoing arrows are attached to the Decision shape and represent all the possible condition values like Yes or No, see Figure 2.

Figure 2. Decision represents condition check

Decision element is similar to the XOR element that is used in other process notations.

Precedence The Precedence arrow is used to order process steps: the previous step should end before the next step starts. The Precedence arrows should be attached to the top and bottom sides of an action shape (Figure 3).
Figure 3. Precedence arrows

An arrow may be unnamed if it’s used to order process steps only. Name the arrow in case you want to show that functional objects are transferred from one action to another (functional objects are added to the Activity objects list in the Properties Window of an arrow).

Object Flow Object flows are used to model objects transferring from action to action. This arrow doesn’t activate action performance though. The object flow arrow has a tunneled start in case there is no need to specify its source (Figure 4).
Figure 4. The Object Flow with a tunneled start
Swimlanes (symbol used for Cross-functional Flowcharts) An actor of actions and sub-processes. Actor’s name is placed inside the block. An org unit or a functional object can be an actor. 
Start and end points of the process. A start event is the event symbol that has only outgoing arrows of the precedence type. An end event is the event symbol that has only incoming arrows of the precedence type.
Separator Represents a phase on a Cross-functional Flowchart.
Applications, Databases, Material objects, Other functional objects (symbols used for Cross-functional Flowcharts) Applications, databases, material objects, other functional objects that are used to perform an action or produced as a result of this performance. The functional object name is placed near the arrow shape.
External Reference An External reference is an element that models a place, entity, or an org unit that is outside the boundaries of the system being modeled. External references are used to define a source or receiver of the arrow that goes outside the model frame.
Table 1. Flowchart Notation Elements
« PreviousLevel upNext »
() ()
Driven by DokuWiki