Académique Documents
Professionnel Documents
Culture Documents
User Guide
CONTENTS
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Introduction
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . . .7
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .8
. . . . . . . . . . . . . . . . . . . . . . . . .9
. . . . . . . . . . . . . . . . . . . . . . . . .9
. . . . . . . . . . . . . . . . . . . . . . . . .9
. . . . . . . . . . . . . . . . . . . . . . . . 10
. . . . . . . . . . . . . . . . . . . . . . . . 11
Organizational Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Example Overview . . . . . . . . . . . . . . . . . . . . . . . . .
Defining an Operation . . . . . . . . . . . . . . . . . . . . . .
Conditioning a Sequence Flow . . . . . . . . . . . . . . . .
Creating a Sequence Flow . . . . . . . . . . . . . . . . . . .
Moving Sequence Flows . . . . . . . . . . . . . . . . . . . .
Defining a Condition on a Sequence Flow . . . . . . . .
Defining Message Flows . . . . . . . . . . . . . . . . . . . . .
Defining Message Flow Content . . . . . . . . . . . . . . .
Creating a Message Flow With Content . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . . . 14
. . . . . . . . . . . . . . . . . . . . . . . . . 18
. . . . . . . . . . . . . . . . . . . . . . . . . 19
. . . . . . . . . . . . . . . . . . . . . . . . .19
. . . . . . . . . . . . . . . . . . . . . . . . .19
. . . . . . . . . . . . . . . . . . . . . . . . .19
. . . . . . . . . . . . . . . . . . . . . . . . . 21
. . . . . . . . . . . . . . . . . . . . . . . . .21
. . . . . . . . . . . . . . . . . . . . . . . . .22
Contents
Using an Organizational Process. . . . . . . . . . . . .
Using an Existing Organizational Process . . . . . . .
Accessing an Organizational Process Diagram . . .
Using Data Objects . . . . . . . . . . . . . . . . . . . . . . .
Creating a Data Object . . . . . . . . . . . . . . . . . . .
Associating a data object with a sequence . . . . . .
Using Data Stores . . . . . . . . . . . . . . . . . . . . . . .
Using Gateways. . . . . . . . . . . . . . . . . . . . . . . . . .
Placing a Process in its Context . . . . . . . . . . . . .
Creating an Organizational Process in a Diagram .
Calling an Organizational Process in an Operation .
Initializing an Organizational Process Diagram . . .
Defining Process Events . . . . . . . . . . . . . . . . . . .
Creating an Event . . . . . . . . . . . . . . . . . . . . . . .
Connecting Events to Sequence Flows . . . . . . . . .
Accessing Preceding or Succeeding Processes. . . .
Attaching an Event to a Process . . . . . . . . . . . . .
Using Participants . . . . . . . . . . . . . . . . . . . . . . . .
Creating an Org-Unit Participant . . . . . . . . . . . . .
Assigning Several Org-Units to a Participant. . . . .
Positioning a Participant in a Swimlane . . . . . . . .
Improving Presentation . . . . . . . . . . . . . . . . . . .
Adding Notes to Objects . . . . . . . . . . . . . . . . . .
Modifying Object Shapes . . . . . . . . . . . . . . . . . .
Modifying Object Name Presentation . . . . . . . . . .
Formatting Links. . . . . . . . . . . . . . . . . . . . . . . .
Changing Fonts. . . . . . . . . . . . . . . . . . . . . . . . .
Refining Flowchart Appearance . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Functional Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Creating a Functional Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Representing a Functional Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
System Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Managing a System Process . . . . . . . . . . . . . . . .
Creating a System Process. . . . . . . . . . . . . . . . .
Connecting a System Process to an Organizational
Creating a System Process Diagram . . . . . . . . . .
Example:. . . . . . . . . . . . . . . . . . . . . . . . . . .
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a task in a system process . . . . . . . .
Sequence Flows, Events and Message Flows . . .
Sequence flows . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Process . . . . . . . . . . . . . . . . . . . . . . . 56
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Contents
Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message flows . . . . . . . . . . . . . . . . . . . . . . . . . .
Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing Step Output Gateways . . . . . . . . . . . . . .
Processing Step Input Gateways . . . . . . . . . . . . . . .
Creating a Gateway . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Gateway . . . . . . . . . . . . . . . . . . . . . . .
Creating a System Process Participant. . . . . . . . . . .
Specifying Process Behavior. . . . . . . . . . . . . . . . . . .
Compensation description . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . .60
. . . . . . . . . . . . . . . . . . . . . . .61
. . . . . . . . . . . . . . . . . . . . . . . 62
. . . . . . . . . . . . . . . . . . . . . . .62
. . . . . . . . . . . . . . . . . . . . . . .62
. . . . . . . . . . . . . . . . . . . . . . .63
. . . . . . . . . . . . . . . . . . . . . . .63
. . . . . . . . . . . . . . . . . . . . . . . 65
. . . . . . . . . . . . . . . . . . . . . . . 66
. . . . . . . . . . . . . . . . . . . . . . .67
Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Creating a Business Process. . . . . . . . . . . . . . . . . . . .
Creating a Business Process Diagram . . . . . . . . . . . . .
Representing Product Offerings . . . . . . . . . . . . . . . . .
Defining Offerings . . . . . . . . . . . . . . . . . . . . . . . . . .
Representing Process Contextualization . . . . . . . . . .
Defining a Contextualization . . . . . . . . . . . . . . . . . . .
Creating a contextualization . . . . . . . . . . . . . . . . .
Defining context . . . . . . . . . . . . . . . . . . . . . . . . .
Launching a Report Illustrating Contextualizations . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . 86
. . . . . . . . . . . . . . . . . . . . . . .86
. . . . . . . . . . . . . . . . . . . . . . . 87
. . . . . . . . . . . . . . . . . . . . . . .87
. . . . . . . . . . . . . . . . . . . . . . . 89
. . . . . . . . . . . . . . . . . . . . . . .89
. . . . . . . . . . . . . . . . . . . . . . .90
. . . . . . . . . . . . . . . . . . . . . . .90
. . . . . . . . . . . . . . . . . . . . . . .90
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Contents
INTRODUCTION
Introduction
Explaining how your enterprise operates
A diagram explaining a business process can provide a better understanding of how
an enterprise operates in cases such as:
Defining IT requirements
Process descriptions can be supplemented by details of IT means required,
functionalities to be implemented, applications or services used.
Describing processes
You can write comments for each process element directly from the diagram. This
offers many advantages:
Introduction
Producing documents
Documents are automatically generated from the elements entered when describing
the diagram.
This User Guide is designed to help you quickly discover the power of MEGA
Process BPMN Edition.
Introduction
CONVENTIONS USED IN THE GUIDE
10
Introduction
Presentation of this Guide
organizational process described in the Quick Start guide. It also presents how to
complete and integrate it with other processes of your organization. Process
descriptions can be completed by specifying the information system components
they require.
"Business Processes", page 85 presents how to specify enterprise product and
service offerings, and the breakdown of the processes producing these.
"Functional Processes", page 49 describes representation of enterprise value
chains in terms of activities. It enables freeing from the existing organization to
imagine new organization solutions for your processes.
"System Processes", page 55 enables description of the IT process required for
implementation of an organizational process by sequencing of the tasks executed.
"Organizational Charts and Responsibilities", page 69 describes how to create an
enterprise organizational chart and how to define responsibilities of persons and
org-units.
"Glossary", page 93, summarizes definitions of the main concepts covered in this
guide.
This guide is complemented by the Quick Start Guide guide, which will help you
create your first diagram with MEGA.
It is also complemented by the MEGA Common Features guide, which presents
functions common to all MEGA products, as well as by Online Help, accessible by
pressing key <F1>, which opens context-sensitive help in each MEGA Process
BPMN Edition dialog box.
More advanced technical functions are described in the MEGA Publisher guide.
11
Introduction
12
1
ORGANIZATIONAL PROCESSES
This chapter describes how to use MEGA Process BPMN Edition functions to improve business
process efficiency.
This presentation is based on the example of purchase request processing introduced in the MEGA
Process BPMN Edition Quick Start guide. Organization of this business process is modified to take
account of evolutions aimed at improving its efficiency.
13
1
EXAMPLE OVERVIEW
The existing organization is represented by the following diagram.
14
Organizational Processes
Example Overview
See"Using Participants", page 39 for more details on assignment of orgunits to participants in the process.
15
1
In the existing process, the purchasing manager must systematically approve all
purchase requests entered by the purchasing assistant.
This approval phase causes delay in the processing of purchase requests, which can
be reduced by partially entrusting the task to the assistant. The majority of
purchase requests concern supplies in current use, and most rejections can be
decided by the assistant alone (outside-catalog purchases for example).
Two axes for improvement of process delay are decided:
16
Organizational Processes
Example Overview
(1)
(2)
(3)
(4)
Create an operation.
Move a sequence flow.
Create a sequence flow and define a condition.
Define a default sequence flow.
Points described here are also presented in the Quick Start guide.
17
1
DEFINING AN OPERATION
An operation is a step in a process.
An operation is an elementary step in an organizational process
executed by an org-unit. It cannot be broken down. An operation can be
industrial (manufacturing a component), logistical (receiving a
delivery), or can involve information processing (entering an order).
You will create an operation and connect it to the org-unit responsible for its
execution.
To create an operation:
1.
2.
3.
18
Organizational Processes
Conditioning a Sequence Flow
19
1
2.
20
Organizational Processes
Defining Message Flows
21
1
4.
Select the name of the content, for example "Purchase Request" and
click OK.
2.
3.
Click the first object representing the start step, and, holding the mouse
button down, draw a line to the object representing the next step.
The Creation of Message Flow With Content dialog box opens.
In the Content drop-down list, select the content you wish to associate
with the flow.
The message flow and its content are displayed in the diagram.
22
Organizational Processes
Using an Organizational Process
Restocking.
Supplier contract negotiation.
The diagram takes a new form.
23
1
To use an existing organizational process:
1.
24
Organizational Processes
Using an Organizational Process
The purchase request is analyzed by the purchasing manager, who checks product
availability and requests that the product be made available.
The purchasing manager also checks stock, and if this is insufficient, requests a
buyer to send a supplier order.
Finally, based on current contracts, the buyers send orders to suppliers.
25
1
USING DATA OBJECTS
In an organizational process diagram, a data object can be used to represent the
fact that data or objects (correspondence, raw materials, finished products, etc.)
are in stock awaiting use.
In the example of the "Process Purchase Order" process, data relating to stock is
represented by the "Stock Data" data object.
A data object is used to explain how documents, data, and other
objects are used and updated during the process. A data object can
represent an electronic document, or any other type of object,
electronic or physical.
3.
Click the arrow at the right of the Content text box and select List
Content in the drop-down list.
The list of contents of the library appears in the dialog box.
Select the content, "Contract Data", and click OK.
4.
button.
By default the data object carries the same name as its content.
The state appears between brackets.
26
Organizational Processes
Using Data Objects
6.
Click OK.
The data object appears in the diagram.
2.
Click the data object , for example "Stock Data" and, holding the mouse
button down, draw a link to the operation.
2.
Click the operation representing the start step, and, holding the mouse
button down, draw a line to the operation representing the next step.
The Creation of Sequence Flow With Data Object dialog box opens.
27
1
3.
In the Content drop-down list, select the content you wish to associate
with the flow.
The sequence flow and its content are displayed in the diagram.
In the example of the "Process Purchase Order" process, data relating to suppliers
is represented by the "Supplier Data" data store.
button.
28
Organizational Processes
Using Gateways
USING GATEWAYS
The following example presents a case in which processing progress is conditioned:
following analysis of a purchase request, the process either ends, or an order is sent
to a supplier.
29
1
PLACING A PROCESS IN ITS CONTEXT
The "Process Purchase Request" and "Process Purchase Order" processes comply
with the general process of standard purchasing, operation of which is described by
the following diagram:
30
Organizational Processes
Placing a Process in its Context
2.
toolbar.
Click within the frame of the described organizational process and within
the frame of the participant responsible for this process.
The Add Organizational Process dialog box opens.
3.
4.
Call.
2.
3.
Click in the diagram within the shape of the participant responsible for its
execution.
The Creation of Organizational Process Call dialog box opens.
In theOrganizational Process box, enter the name of the process
called, for example "Process Purchase Request", that could be replaced
by "Process Urgent Purchase Request".
31
32
Organizational Processes
Defining Process Events
Creating an Event
To create an event:
1.
2.
3.
You can directly click the Finish button of the wizard. A catching
event without type is created.
4.
Click Next and select the type of event you wish to create.
6.
Click Finish.
The new event appears in the diagram. The shape of the event respects
conventions linked to its type and nature.
2.
33
1
Event natures
The nature of the event enables specification of its position in the processing.
Event types
Event type enables specification of what will trigger the event and what will be
triggered by the event.
34
Organizational Processes
Defining Process Events
35
1
When this latter process is described by a diagram, the process that precedes it can
be shown.
36
Organizational Processes
Defining Process Events
3.
4.
37
38
Organizational Processes
Using Participants
USING PARTICIPANTS
A participant enables:
39
3.
4.
5.
To create an org-unit from this participant, enter the name of the new
org-unit in the Org-Unit text box.
Indicate the name of the participant if you wish to specify the org-unit
role in the process.
Click the Finish button.
The participant is positioned in the diagram. If you have not specified a
name, it will carry the name of the assigned org-unit.
To hide the name of the participant, open its pop-up menu and
select Shapes and Details. In the tree on the left, click the "Short
Name" folder, then in the Content tab, clear the Short Name check
box.
40
Organizational Processes
Using Participants
2.
3.
4.
5.
6.
7.
Click Close.
Names of assigned org-units appear in the title bar of the participant with
the name of the participant.
41
1
2.
3.
4.
5.
In the Characteristics tab, select the line of the actor of which you wish
to condition assignment.
Click in the Conditioning column.
42
Organizational Processes
Improving Presentation
IMPROVING PRESENTATION
2.
3.
button.
4.
The note Name is automatically generated by MEGA and does not have
any special meaning.
You can choose different types of note: "Correction", "Documentation",
"Improvement", "Example", "Question", "Remark", etc.
Select for example "Remark" type and enter your note in the text box.
5.
43
If you wish to use additional shapes, give them a name using the
first four letters of the name of the standard shape and copy them into
the Standard\MEGA_USR folder of the environment.
The shape used for certain objects, such as messages, varies as a
function of the type attributed to them.
If you manually indicate the shape to be used following the explanation
above, the drawing will no longer reflect the type of object.
44
Organizational Processes
Improving Presentation
3.
In the Content tab, confirm that the check box on the right of character
string name is selected.
4.
5.
If this box is not selected, the name will be masked in the diagram.
45
1
6.
Click OK.
Formatting Links
The "Edit" toolbar at the right of the diagram enables formatting of links.
If this toolbar is not displayed by default:
1. Select View > Toolbars > Edit.
This toolbar now appears on your workspace.
2. Select each link then click the button corresponding to the desired line
style (simple, orthogonal, curved, double):
You can also select a link, hold down the <Ctrl> key, and then
move this link. A "nail" now appears on the link allowing you to give it
the desired form.
3.
Changing Fonts
To configure the font of the text displayed.
1. Select the text.
2. In the menu bar, select Format > Font.
A dialog box appears. You can select another font or font size in this dialog box.
46
Organizational Processes
Improving Presentation
2.
3.
4.
You can create your own custom shapes or use images from other
software. For more information on creating new shapes, see the online
help or the Advanced guide.
47
48
2
FUNCTIONAL PROCESSES
This chapter presents why and how to describe value chains of the enterprise in the form of
functional processes.
When an enterprise operates out of numerous geographical locations, organization of business
process operations can vary significantly between regions.
It is therefore useful to have a summary view, independent of organizational structure, to represent
steps in the value chain connected to enterprise business and common to all organizational variants.
A functional representation of the value chain also facilitates improvement in enterprise operation.
When the operation of each organizational process is represented, this enables local optimization of
each process as explained in the previous chapter.
This structure however remains partitioned by existing organizational structures. More significant
changes require a broader view of the value chain, independent of organization. This global view is
represented by the functional process diagram.
MEGA enables the creation and description of enterprise value chains.
49
2
CREATING A FUNCTIONAL PROCESS
To create a functional process from the navigator:
1. Right-click the current library.
2. Select New > Functional Process.
The Create Functional Process dialog box appears.
3. Enter the name of the functional process in the Name box.
4. Click Finish.
The functional process is created and added to the list of functional processes in the
menu tree.
50
Functional Processes
Representing a Functional Process
Diversity of variants
Most variants of a process are the result of organizational choices such as giving
preference to urgent orders, special processing for large or export orders, etc.
It is necessary to overcome this diversity in order to move on to a new set of
variants, for example processing orders via telephone or the Internet. Representing
a business process in terms of activities gives a unique representation of the value
chain, highlighting what must be done irrespective of organization choices.
Number of steps
Certain steps in an organizational process are exclusively linked to the chosen
organization. In such cases, it is useful to check whether these steps provide any
real added value to clients or only concern the way things are done.
Delivery times can also be reduced by restructuring the order of these steps.
To highlight possible improvements, you can represent a value chain by flows
exchanged between enterprise activities.
A functional activity is a step in a process. This step represents the
contribution of a business line to the process value chain.
51
2
The following diagram presents a functional process example:
The purchase request is recorded and must then be approved. The requester is
informed of approval or rejection of the request. If the request is validated, an
analysis of the required order is carried out.
If stock is lower than a given threshold, an order is prepared and sent to the supplier
for resupply.
If the product is available, or as soon as it is received from the supplier, it is made
available to the requester.
52
Functional Processes
Representing a Functional Process
The first step consists of analyzing the purchase request. If the total amount is
large, normal processing is carried out.
Otherwise, the availability request and a restock request are sent, if necessary. The
rest of the functional process is identical to the normal case: when the order has
been received, it is made available to the requester.
53
2
We can define a new organizational process for processing of urgent purchase
requests, in which responsibilities of the purchasing assistant are extended.
The purchasing assistant begins by analyzing the purchase request. If the amount
is large, the normal process purchase request process is implemented. If the
product is available, the assistant sends the availability request.
If not, the assistant sends a purchase order to the supplier. The rest of the
processing is carried out within the framework of the normal "Process Purchase
Requests" organizational process.
To analyze the purchase request and send the order, the purchasing assistant
requires data on stock levels. He will have access to the "Equipment Purchasing"
application.
This new variation of the organizational process enables faster processing for urgent
orders. It demands higher qualifications of the purchasing assistant who has more
responsibilities.
54
3
SYSTEM PROCESSES
MEGA allows you to model the IT system process implemented when using an organizational
process. This description is made in a BPMN model detailing the sequence flow of tasks performed
when executing the application in the particular context.
The BPMN (Business Process Modeling Notation) specification was created to formalize graphical
representation of IT and business processes, offering notation easily used by all participants
concerned.
The points covered are:
55
3
MANAGING A SYSTEM PROCESS
A system process represents automated execution of an organizational process.
The system process diagram uses notation proposed by BPMN standard.
2.
3.
buttons appear
5.
Click in the diagram where you wish to position the system process.
The Add System Process dialog box opens.
In the System Process box, enter the name you wish to give your
process.
Click Finish.
6.
7.
56
System Processes
Managing a System Process
For example, the "Process Urgent Purchase Request" process is implemented by the
"Analyze Purchase Request" system process to assure speed and efficiency of
processing.
buttons appear in
57
3
Example:
The diagram below represents purchase request processing.
58
System Processes
Tasks
TASKS
Tasks correspond to process steps.
A task is an elementary step that is included within a system
process. A task is used when the work in the system process is not
broken down to a finer level of the process. Generally, an end-user and/
or an IT service are used to perform the task when it is executed.
then click in
59
3
SEQUENCE FLOWS, EVENTS AND MESSAGE FLOWS
Sequence flows
Organization of tasks in the system process is represented by sequence flows
between tasks.
A sequence flow is used to show the order in which steps of a
process will be performed. Each sequence flow has only one source and
only one target.
Events
Events represent facts occurring during process execution.
An event represents a fact occurring during execution of a process,
for example a new contract concluded with a supplier. An event marks
the impact on process progress of a phenomenon internal or external to
the process. There are different natures of events: start events, catch
events, throw events and end events.
Start
Final
60
System Processes
Sequence Flows, Events and Message Flows
Message flows
Message flows represent exchanges between the system process and the exterior.
A message flow is information flowing within an enterprise or
exchanged between the enterprise and its business environment. A
message flow can carry a content.
61
3
GATEWAYS
Complying with BPMN standard, several gateway types are proposed in the diagram
insert toolbar.
Gateways are modeling elements that are used to control how
sequence flows interact as they converge and diverge within a process.
In the case of a Complex gateway, one or several output branches can be selected
from those available.
A Complex gateway represents a combination of those above.
When the gateway has been created, its type can be modified in its properties dialog
box.
At output of a step, a gateway represents a point of divergence of sequence flows
of a process.
62
System Processes
Gateways
In the case of a Parallel gateway, all input branches are processed simultaneously.
Creating a Gateway
To create a gateway:
1. Click the arrow at the right of the Gateway button in the diagram insert
toolbar and select the gateway type you wish to create.
2.
Modifying a Gateway
To modify a gateway:
1. Right-click the gateway and select Properties.
The properties dialog box opens.
63
3
In the Characteristics tab, modify the name or type of the gateway.
The different gateway types proposed are:
Complex: the process can take a complex combination of paths.
Exclusive (Data): the process can take a single path from several
possible paths depending on the value of the data available. This is the
default gateway type.
Exclusive (Start): the process is triggered by the first event
occurring; others are ignored.
Exclusive (Event): the process can take a single path from several
possible paths depending on the events occurring.
Inclusive: the process can take one or several paths simultaneously.
Parallel: the process takes several parallel paths simultaneously.
Parallel (Start): the process is triggered by the first event occurring.
The other events occurring during progress of the process are also
taken into account.
3. Click OK.
2.
To display the name of a gateway, masked by default, see "Modifying Object Name
Presentation", page 45.
64
System Processes
Creating a System Process Participant
2.
3.
4.
65
3
SPECIFYING PROCESS BEHAVIOR
Complying with BPMN standard, a process can have different behaviors. With MEGA
Process BPMN Edition, these behaviors are available for organizational processes,
operations, system processes and tasks.
To describe for example that a system process is executed by a loop:
1. Right-click the process and select Properties.
The properties dialog box opens.
2. In the Characteristics tab, click the arrow at the right of the Loop box.
A list of loop types appears.
3. Select the loop type corresponding to process behavior.
4. Click OK.
Shape of the process is modified to display the symbol of the loop.
66
System Processes
Specifying Process Behavior
In the Characteristics tab, click the arrow at the right of the Task Type
box.
A list of task types appears.
Compensation description
Compensation is caused by an event occurring during process execution. This event
is placed at the edge of the interrupted process. It can be moved along the edge of
the process.
To free the event from the process, use the detach command in its pop-up menu.
This event can trigger a compensation operation.
67
68
4
ORGANIZATIONAL CHARTS AND
RESPONSIBILITIES
MEGA enables representation of enterprise structure It indicates the hierarchy of org-units in the
enterprise, specifies the persons that play the role of these org-units, and shows at which site the
org-unit is located.
MEGA also enables definition of organizational process responsibilities by means of the RACI matrix
(Responsible, Accountable, Consulted, Informed) as well as business processes.
69
4
CREATING AN ORGANIZATIONAL CHART
"Drawing an Organizational Chart", page 70
"Consulting the RACI Matrix of Org-Units", page 74
The organizational chart presents the structure of the enterprise. MEGA Process
BPMN Edition allows you to design your organizational charts using the same tools
and methods as applied to processes.
MEGA Process BPMN Edition organizational charts contain the following
descriptive objects:
3.
70
To simultaneously add all the org-units involved in your processes that were not
automatically inserted at diagram initialization:
1.
2.
3.
diagram.
In the Add Org-Unit dialog box, Select Query in the drop-down list.
In the dialog box that appears, click the Find button.
4.
When you click on an object while holding down the <Ctrl> key,
you add it to the list of selected objects if it was not previously selected,
or you remove it from the selection if it was.
71
4
5.
Drag-and-drop the selected objects from the result dialog box into the
diagram.
You may keep your query results in order to reuse them later. To
do this, click button Keep result in new window.
You can select several objects in the diagram. To do this, hold down
the <Shift> key while clicking on each object you wish to select. You
can also use the mouse to drag a rectangle around the desired objects.
You can assign the same size to several objects by selecting them and
then applying the Make Same Size command in the Drawing menu.
Follow the same steps to align objects: from the Drawing menu, select
Align object. Note that the last object selected is used as the
reference.
If you perform an action that you want to cancel, select Edit > Cancel.
6.
You will now add the sites where the org-units are located.
A site is the geographical location of an organization. Examples:
Boston subsidiary, Seattle plant, and more generally the headquarters,
subsidiaries, plants, warehouses, etc.
7.
72
When you create a link between two org-units, always drag from the org-unit higher
in the hierarchy down to the subordinate. Once the link is drawn, an arrowhead
indicates the direction of the hierarchy.
button.
If the Person
button does not appear in the toolbar, add it by
selecting it in the Views window.
73
4
3.
You can also specify its details (company name, e-mail address,
telephone number, etc.).
In the properties dialog box of the org-unit, select the RACI tab.
To generate the matrix to search for org-units in depth, you must
use report "Org-Unit and Sub-Org-Unit RACI Matrix (BPMN)". For more
details, see "Launching an RACI matrix from an object", page 81
(operation identical to business processes).
74
75
4
Generating an RACI matrix from a business process
From a business process you can generate a matrix presenting:
76
(RACI)
on an operation
on an organizational process.
The proposed responsibilty levels are as follows:
Responsibility
Meaning
Responsible
Accountable
Consulted
Informed
Defining Responsibilities
Organizational process and operation responsibilities
To indicate the responsibility of an org-unit in an operation or organizational
process:
1. Open the properties dialog box of the operation or process.
2. Select the Characteristics tab.
3. In the "Org-Unit" frame, click the Connect button.
4. In the dialog box that opens, select Candidate Org-Units (RACI).
A dialog box proposes the list of org-units that execute the operation or
the process via a participant.
77
4
6.
Icon
Meaning
Indicates that responsibility is deduced from the participant.
The icon appears when the selected org-unit is:
- assigned to the participant, and
- declared with default responsibility: Responsible.
No icon
Responsibility of a participant
To indicate responsibility of each of the org-units attached to a participant in the
different operations or organizational processes it executes:
1. Open the participant properties dialog box.
78
2.
79
3.
Click button
.
The context of responsibility of the org-unit is indicated. You can view:
4.
80
5.
6.
7.
8.
Click button
For more details on the use of analysis reports, see the MEGA
Common Features guide.
81
4
4.
5.
In the properties dialog box of the report setting, go to the bottom, using
the scroll bar if necessary.
Create a level.
Indicate a value in the field provided.
6.
7.
82
8.
Click OK.
The report appears in the Reports tab.
org-units in columns
operations or organizational processes in rows
Click button
on the right to refresh the report if you have
modified objects or parameters of the report.
83
84
5
BUSINESS PROCESSES
This chapter presents how to describe products or services supplied by processes of the enterprise
to its customers.
The business process diagram enables representation of product or service offerings proposed by
the enterprise to each of its markets, as well as the processes that produce these.
MEGA enables creation and definition of enterprise business processes.
85
5
CREATING A BUSINESS PROCESS
To create a business process from the navigator:
A business process represents a system that offers products or
services to an internal or external client of the company or organization.
At the higher levels, a business process represents a structure and a
categorization of the business. It can be broken down into other
processes. The link with organizational processes will describe the real
implementation of the business process in the organization. A business
process can also be detailed by a functional view.
1.
2.
3.
4. Click OK.
The business process is created and added to the list of business processes.
2.
86
In the dialog box that opens, select "Business Process Diagram and
click the Create button.
The diagram window opens.
Business Processes
Representing Product Offerings
Defining Offerings
Offerings are proposed by enterprise business processes to participants outside the
enterprise.
An offering represents the making available of a product or service
supplied by an enterprise through a specific process.
Creating an offering
To create an offering:
1.
button
87
5
2.
3.
Click the business process and, holding the mouse button down, draw a
link to the participant.
Release the mouse button.
The link representing the offering appears in the diagram.
88
Business Processes
Representing Process Contextualization
Defining a Contextualization
Contextualizations enable association of processes between themselves.
A contextualization allows specification of the implementation of a
process by another process in a specific context, such as the
geographical location on a site.
89
5
Creating a contextualization
To create a contextualization:
1.
2.
Defining context
To specify the context in which a process implements another process:
1. Right-click the contextualization and select Properties.
The properties dialog box opens.
2. Select the Characteristics tab.
3. Click the Connect button in the Implementation Context section.
4. Enter the context type, org-unit or site, in the dialog box that opens.
5. Click the Find button.
6. In the list that appears, select the org-units or sites concerned and click
OK.
7. Click the Close button.
The implementation contexts appear in the diagram.
90
Business Processes
Representing Process Contextualization
4.
91
92
6
GLOSSARY
application
business function
business process
constraint
content
contextualization
dashboard
93
94
data object
data store
diagram
event
external org-unit
functional activity
functional process
gateway
issue
IT service
Glossary
junction
keyword
message flow
objective
offering
operation
organizational process
org-unit
95
96
parallelism
participant
participant (org-unit)
person
product
project
sequence flow
site
Glossary
system process
A
system
process
is
the
executable
representation of a process. The elements that
formalize a system process are the following: the
events of the workflow, the tasks to be carried
out during the processing, the algorithmic
elements used to specify the way in which the
tasks follow each other, the information flows
exchanged with the participants.
system used
task
97
98
INDEX
accountable
org-unit . . . . . . . . . . . . . . . . . . . . . . . . 74, 77
RACI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Ad Hoc
process . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
cancel
object . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
catching
system used . . . . . . . . . . . . . . . . . . . . . . . . 54
compensation
adding notes
application
assignment
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
participant . . . . . . . . . . . . . . . . . . . . . . . . . 40
event type . . . . . . . . . . . . . . . . . . . . . . . . 34
event nature . . . . . . . . . . . . . . . . . . . . . . . 34
event type . . . . . . . . . . . . . . . . . . . . . . . . 34
process. . . . . . . . . . . . . . . . . . . . . . . . . . . 66
conditional
event type . . . . . . . . . . . . . . . . . . . . . . . . 34
conditioned
sequence flow . . . . . . . . . . . . . . . . . . . . . . 19
consulted
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . 77
responsibility. . . . . . . . . . . . . . . . . . . . . . . 78
content
BPMN activity
activity (functional) .
functional process . .
operation . . . . . . . .
task . . . . . . . . . . . .
business function
functional process .
manager . . . . . . .
business process . . .
contextualization . .
RACI matrix . . . . .
responsibility . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 51
. 51
. 18
. 59
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 53
. 75
. 85
. 89
. 76
. 75
message flow . . . . . . . . . . . . . . . . . . . . . . 21
contextualization
business process . . . .
functional process . . .
organizational process
process. . . . . . . . . . .
report. . . . . . . . . . . .
system process . . . . .
control
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
89
89
89
89
90
56
business process . . . . . . . . . . . . . . . . . . . . 75
process. . . . . . . . . . . . . . . . . . . . . . . . . . . 75
correction
note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
99
Index
D
data object
folder
organizational process . . . . . . . . . . . . . . . . . 26
data store
organizational process . . . . . . . . . . . . . . . . . 28
default
sequence flow . . . . . . . . . . . . . . . . . . . . . . 20
shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
diagram
pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
swimlane
pool . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
font
text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
functional
process . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
functional process
activity. . . . . . . . . . . . . . . . .
business function. . . . . . . . . .
value chain . . . . . . . . . . . . . .
functional process diagram . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 51
. 53
. 50
. 52
functionality
system used . . . . . . . . . . . . . . . . . . . . . . . . 54
E
G
end
event nature . . . . . . . . . . . . . . . . . . . . . . . 34
error
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
example . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
organizational process . . . . . . . . . . . . . . . . . 29
system process . . . . . . . . . . . . . . . . . . . . . . 62
escalation
event
event nature
..............
event type . . . . . . . . .
organizational process .
system process. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
34
34
33
60
catching. . . .
combination .
end . . . . . . .
start . . . . . .
throwing . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
34
35
34
34
34
event nature
event type
.
.
.
.
.
cancel . . . . . .
combinations .
compensation .
conditional . . .
error . . . . . . .
escalation . . .
link . . . . . . . .
message . . . .
multiple . . . . .
none . . . . . . .
signal . . . . . .
terminate. . . .
timer . . . . . . .
100
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
34
35
34
34
34
34
34
34
34
34
34
34
34
generic
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
I
improvement
note. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
improving
presentation . . . . . . . . . . . . . . . . . . . . . . . . 43
informed
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
responsibility . . . . . . . . . . . . . . . . . . . . . . . 78
inserting
IT
shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
manager
process . . . . . . . . . . . . . . . . . . . . . . . . . 75
IT service
system used . . . . . . . . . . . . . . . . . . . . . . . . 54
Index
link
object
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
formatting . . . . . . . . . . . . . . . . . . . . . . . . . 46
offering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
creating . . . . . . . . . . . . . . . . . . . . . . . . . . 87
product. . . . . . . . . . . . . . . . . . . . . . . . . . . 88
loading
location
shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
loop
system process . . . . . . . . . . . . . . . . . . . . . . 66
adding notes . . . . . . . . . . . . . . . . . . . . . . . 43
operation
creating . . . .
organizational
RACI . . . . . .
responsibility .
......
process
......
......
organizational chart . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
18
18
77
77
69
.
.
.
.
.
.
.
.
.
.
.
organizational process diagram .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
26
28
33
14
29
21
18
24
77
77
19
24
organizational process
M
management
quality
process . . . . . . . . . . . . . . . . . . . . . . . . . 75
risks
process . . . . . . . . . . . . . . . . . . . . . . . . . 75
manager
business function . . . . . . . . . . . . . . . . . . . . 75
IT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
manual
data object . .
data store . . .
event . . . . . .
example . . . .
gateway . . . .
message flow
operation . . .
organizational
RACI . . . . . .
responsibility .
sequence flow
............
............
............
............
............
............
............
process diagram
............
............
............
org-unit
accountable. .
assignment . .
generic . . . . .
participant . .
responsibility.
structure. . . .
type . . . . . . .
shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
message
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
message flow
content . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
organizational process . . . . . . . . . . . . . . . . . 21
system process . . . . . . . . . . . . . . . . . . . . . . 61
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
74
40
74
40
77
74
73
assignment . . .
org-unit . . . . .
process. . . . . .
responsibility. .
system process
task . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
40
40
39
78
65
65
multiple
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
process . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
P
participant
note
note type . . . . . . . . . . . . . . . . . . . . . . . . . . 43
pool
diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 42
presentation
improving . . . . . . . . . . . . . . . . . . . . . . . . . 43
procedure
responsibility. . . . . . . . . . . . . . . . . . . . . . . 77
101
Index
process
Ad Hoc . . . . . . . . . . . . . .
compensation . . . . . . . . . .
contextualization . . . . . . .
functional. . . . . . . . . . . . .
loop . . . . . . . . . . . . . . . .
multiple . . . . . . . . . . . . . .
organizational. . . . . . . . . .
participant . . . . . . . . . . . .
task type . . . . . . . . . . . . .
transaction. . . . . . . . . . . .
viewing external processes
product
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
66
66
89
50
66
66
14
39
67
66
37
creating . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
offering . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
S
send
event nature . . . . . . . . . . . . . . . . . . . . . . . . 34
sequence flow
conditioned. . . . . . . .
conditioning . . . . . . .
creating . . . . . . . . . .
default . . . . . . . . . . .
moving. . . . . . . . . . .
organizational process
sequence flow . . . . . .
system process . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
default . . .
folder . . . .
inserting. .
manual. . .
modifying .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . 44
. . . . 44
. . . . 46
. . . . 44
. 44, 45
shape
signal
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19
. 19
. 19
. 20
. 19
. 19
. 19
. 60
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
quality
management
process. . . . . . . . . . . . . . . . . . . . . . . . . 75
question
note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
start
event nature . . . . . . . . . . . . . . . . . . . . . . . . 34
structure
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
style
row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
swimlane
pool
diagram . . . . . . . . . . . . . . . . . . . . . . . . 42
system process
RACI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77, 81
business process. . . . . . . . . . . . . . . . . . . . . 76
organizational process . . . . . . . . . . . . . . . . . 77
RACI matrix
depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
remark
note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
resource
contextualization .
creating . . . . . . .
event . . . . . . . . .
gateway . . . . . . .
message flow . . .
sequence flow . . .
task . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
system process diagram .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 56
. 56
. 60
. 62
. 61
. 60
. 59
. 56
system used
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
system used. . . . . . . . . . . . . . . . . . . . . . . . 54
responsibility
level . . . . . . . . . . . . .
organizational process .
org-unit . . . . . . . . . . .
participant . . . . . . . . .
responsible
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
78
77
77
78
org-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
responsibility . . . . . . . . . . . . . . . . . . . . . . . 78
task
management
process. . . . . . . . . . . . . . . . . . . . . . . . . 75
task type
risk
row
style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
102
participant . . . . . . . . . . . . . . . . . . . . . . . . . 65
system process . . . . . . . . . . . . . . . . . . . . . . 59
business rule . . . . . . . . . . . . . . . . . . . . . . . 67
manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Index
process . . . . . . . .
receive. . . . . . . . .
script . . . . . . . . . .
send . . . . . . . . . .
system process call
terminate
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 67
. 67
. 67
. 67
. 67
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
text
font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
timer
event type . . . . . . . . . . . . . . . . . . . . . . . . . 34
transaction
process . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
type
org-unit
properties . . . . . . . . . . . . . . . . . . . . . . . 73
V
value chain . . . . . . . . . . . . . . . . . . . . . . . . . . 51
creating . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
functional process . . . . . . . . . . . . . . . . . . . . 50
W
warning
note. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
103
Index
104