Chapter 6 Building an Analysis Business Process Model

Defining Processes in an Analysis BPM

A process can be the design of a service (implementation process) or the invocation of a manual or automated action, like "getting money from an incoming order", or "building a software system according to the specifications" for example. When the process gains the control, it performs the action, then, depending on the result of the action, the flow is passed to another process. A process can be viewed as an action to reach a goal.

A process must have one input flow and one output flow at least.

A process can be atomic or composite:

An atomic process does not contain any sub-processes. It is called process in a BPM, or sometimes activity
A composite process uses sub-processes to describe its actions. It is called composite process in a BPM

For more information about composite processes, see section Defining composite processes.

Activity processes in an analysis BPM do not detail the way they are implemented but rather insist on their functional aspects. Implementation details are defined in the executable languages.

For more information about executable processes, see section Defining processes in an executable BPM in chapter Building an Executable BPM: Managing Data and Choreography.

Reusing existing processes

You can use internal and external shortcuts of processes to reference your model.

For more information about shortcuts, see chapter Managing shortcuts in the General Features Guide.