Swimlane

Diagram in flowcharts

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Swimlane" – news · newspapers · books · scholar · JSTOR (February 2024) (Learn how and when to remove this message)

|

A swimlane (as in swimlane diagram) is used in process flow diagrams, or flowcharts, that visually distinguishes job sharing and responsibilities for sub-processes of a business process. Swimlanes may be arranged either horizontally or vertically.

Swimlane flowchart. Here, the swimlanes are named Customer, Sales, Contracts, Legal, and Fulfillment, and are arranged vertically.

## Attributes

[edit]

The swimlane flowchart differs from other flowcharts in that processes and decisions are grouped visually by placing them in lanes. Parallel lines divide the chart into lanes, with one lane for each person, group or sub process. Lanes are labelled to show how the chart is organized.

In the accompanying example, the vertical direction represents the sequence of events in the overall process, while the horizontal divisions depict what sub-process is performing that step. Arrows between the lanes represent how information or material is passed between the sub processes.

Alternately, the flow can be rotated so that the sequence reads horizontally from left to right, with the roles involved being shown at the left edge. This can be easier to read and design, since computer screens are typically wider than they are tall, which gives an improved view of the flow.

Use of standard symbols enables clear linkage to be shown between related flow charts when charting flows with complex relationships.

## Usage

[edit]

When used to diagram a business process that involves more than one department, swimlanes often serve to clarify not only the steps and who is responsible for each one, but also how delays, mistakes or cheating are most likely to occur.

Many process modeling methodologies utilize the concept of swimlanes, as a mechanism to organize activities into separate visual categories in order to illustrate different functional capabilities or responsibilities (organisational roles). Swimlanes are used in Business Process Modeling Notation (BPMN) and Unified Modeling Language (UML) activity diagram modeling methodologies.

## Origin

[edit]

Swimlane diagrams first appeared in the 1940s as a variation of the flow process chart called multi-column charts.[1] They were called Swim Lane diagrams by Geary Rummler and Alan Brache in their book Improving Performance (1990). They were first introduced to computer-based diagramming by iGrafx. Swimlanes are also known as "Rummler-Brache Diagrams". Another possible origin of the term swimlane is as part of the JBoss jBPM jPDL (Process Definition Language) graphical process designer a part of the JBoss jBPM framework for process languages.[2]

The Swimlane presentation was developed in the early 1980s by Prof. Dr.-Ing. Binner as part of his doctoral thesis on the requirements of the IT and CIM concept at the Institute for Factory Facilities at Prof. Wiendahl at TU-Har.

A process model was developed in which the role-based process analysis and modeling was the starting point for the IT-based IT solution or, in the case, the CIM solution with which the development of an IT-CIM concept was possible.

## Alternative terms

[edit]

A Swimlane was first introduced to computer-based Process Modeling by IGrafx in 1993 and trademarked in 1996. It may also be referred to as a functional band (as it is in Microsoft Visio 2007) and is used in the same way, to create a cross functional flowchart to map a process within the functional units of a business.[3] The term functional band came after the use of swimlane and is seemingly in decline as the acceptable term as BPMN has been more widely accepted as a modeling standard.

Another term used is "Functional Flowchart" useful for productivity improvement and systems design projects. After establishing the 'as is' workflow and systems interfaces, work steps are simplified to automate processes whenever practical and transfer steps to subsequent work processes. A 'to be' model is then created for human processes and a related systems design document developed for those that are automated. Typically over 30% productivity gains are accomplished even for processes that remain manual.

## See also

[edit]

* Workflow
* Event-driven process chain
* Flowchart

## References

[edit]

1. ^ http://www.worksimp.com/articles/processcharting.pdf?pdf=1945-Process-Charting [dead link]
2. ^ Chapter 18. jBPM Process Definition Language – Swimlane
3. ^ Create a cross-functional flowchart, Microsoft Office Visio Help

## External links

[edit]

* Swimlane Guidelines, Agile Modeling, Process Mapping