Show TOC

Using BPMN Process ModelsLocate this document in the navigation structure


BPMN Specification

The use of process modeling on a large scale called for one standard notation for creating process models. The Business Process Modeling Notation (BPMN), which is a standardized graphical notation for drawing the steps of a business process, was developed by Business Process Management Initiative (BPMI). BPMN allows modeling of end-to-end business processes in a standard manner that is understandable by a wide range of professionals, for example business analysts, managers and developers. In other words, BPMN makes easier the communication and coordination between non-technical and technical users by offering a common language.

For more information about BPMN, see http://www.bpmn.orgInformation published on non-SAP site.

BPMN Process Model

BPMN model is a process model that includes a small set of graphical elements and connectors representing the process flow. This process model is designed to be an easy to use and understand description of what a business process is. A process model can describe also more complex business process that includes different subprocesses producing results that the main process use to reach its goal. BPMN goes further with allowing the process model to show exactly who does what by separating respective events and activities in a graphically differentiated area.

The process composer adopts the BPMN and allows you to model business processes with different scope and granularity. When using the BPMN in the process composer, the modeling can include the following steps:

  • Defining process participants

    These are the participants in the process itself and external business units (not part of the process itself). In the process composer you use pools to differentiate between internal and external participants. The participants who are internal for the process are included in an active pool. Internal and external participants communicate through message flows.

    You use lanes to separate the different participants contained in one pool. The lanes allow you to organize and separate activities, associated with different functions or roles in the process.

    For more information, see Pools and Lanes .

  • Defining a start point of the process

    In the process composer, you define a start point of the process using BPMN's start message event.

    For more information, see Events .

  • Defining process steps and their sequence

    In the process composer, you define the process steps using the following graphical objects, specified by BPMN:

    • Activities

      You use human or automated activities to indicate that a process step is performed respectively by a human or system. You create a subprocess activity to represent another process, which is referenced by the process you are modeling.

      For more information, see Activities .

    • Events

      You use intermediate events in the process model to indicate that the flow is delayed and is waiting for a certain time to pass before resuming.

      For more information, see Events .

    • Gateways

      You use gateways to indicate that a decision must be made, or that the process flow must be split or merged depending on the given conditions.

      For more information, see Gateways .

    • Artifacts

      You use data object and annotation types of artifacts to provide additional information about the process. You connect data objects to other graphical objects using data flow connections. You connect annotations to other graphical object using association connections.

      Unlike the other graphical objects (activities, events, gateways), artifacts do not affect directly the process flow.

    In the process composer, you define the sequence of process steps with sequence flow connections.

  • Defining an end point of the process

    In the process composer, you define an end point of the process using BPMN's end message event or termination event.

    You can also use error end events to indicate that an error happens in the process and boundary events to show how this error is handled.

    For more information, see Events .