2007 11-09 mm (costa rica - incae cit omg) modeling with bpmn and xpdl

© 2007 IBM Corporation

Business Process Modeling with BPMN & XPDL

Mike Marin, November 9, 2007

BPM Product Architect,

IBM

© 2007 IBM Corporation 2

Topics

Process Modeling

BPMN

Process Modeling Methodologies

Orchestration vs. Choreography

XPDL

WS-BPEL

Putting all together

Future


Process Modeling

Documenting the organization business processes using a formal notation

Business processes describe how a business pursues its objectives

Graphical description of organization business process


Need for Process Modeling

Documentation of processes

Ability to publish and share processes across the enterprise

Create process catalogs

Not all processes are automated

E.g Retail sales is heavily manual

E.g. Manufacturing automated by machines


Level of Abstraction

High Level Documentation

Process Maps

• Simple flow charts of activities

Process improvement

Process Descriptions

• Extended with additional measurable information

Executable Models

Process Models

• Enough information to analyze, simulate, and execute

Automated processes may execute in multiple engines


Why Process Modeling?

Create complete documentation of processes and procedures

Communicate with subject matter experts

Provide visibility into the enterprise

Facilitate communication between the business side and the IT department


Topics

Process Modeling

BPMN



XPDL

WS-BPEL


Future


BPMN

Business Process Modeling Notation (BPMN)

BPMN a flow-chart based notation for defining Business Processes

Describe interaction between processes

Goal

Design to be used by business analysts

Check

Supply

Cabinet

Deny

Request

Complain

About

Requester

E.G., New Pen

Ord

erin

g O

ffic

e S

up

plie

s

Receive

Supply

Request


Origins of BPMN

BPMN 1.0 (05/2004)

Specification was released to the public.

Under the Business Process Management Institute (BPMI)

BPMN 1.0 (02/2006)

Adopted as an OMG standard

BPMN 1.1 (2007)

Completed and available soon

An Object Management Group (OMG) specification


BPMN Development Drivers

Acceptable and usable by the business community for general process modeling

Generate executable processes from a model

BPMN is intended to be Methodology Agnostic

Methodologies will give guidance as to the purpose and level of detail for modeling

Conflicting Requirements!


BPMN Design Guidelines

Use a top-down approach for notation design

Decided what should be graphically displayed

• Allow extensibility

The main end-user is a business analyst

Usable on paper

• But modeling tools are expected for complete models

Make different concepts as visually distinguishable as possible

Define the line between simplicity and complexity

Flow through the process should be unambiguous


BPMN Design for Complexity

Business Processes do include complex behavior. Yet, most users desire a simple notation and supporting methodologies

BPMN approach

Use a basic, familiar flow-chart structure

Create a small set of core elements

• Reuse familiar shapes where possible

Create variations of the core elements to introduce complexity.

• Some of the variations are not required for simple modeling


Diagram Elements

Activities Events Gateways Connectors


BPMN Basic Concepts

Events

Activities

Gateways

Flow Objects

Pool

Lanes (within a Pool)

Na

me

Swimlanes

Na

me Na

me

Na

me

Sequence

Flow

Message Flow

Association

Connectors


BPMN Example


Topics

Process Modeling

BPMN



XPDL

WS-BPEL


Future



BPMN is intended to be methodology independent

Simple or complex diagrams can be created based on the chosen methodology

Methodologies determine what information is captured about a process and how the process is constructed

Many methodologies can be used for modeling with BPMN

Some require extended Artifacts

Examples of methodologies:

LOVeM, EPCs, RAD methodology, IDEF

Consulting organization methodologies


General Modeling Concepts

A process is chronological

Accurate models should be oriented on a time line

Processes generally begin with triggering events, and work their way through to significant business results

They can also represent smaller segments of re-usable work

All tasks or activities are assigned to roles that are meaningful to people in the business.

A complete model should display how objects or data (or both) are transferred and where they are going

A process can be modeled in a hierarchical fashion

The choices made for decisions, which occur within a process, determine which of all potential paths will be taken


General Modeling Guidelines

Establish organization standards or guidelines for developing models and naming model elements

Establish naming conventions for each type of modeling object.

Avoid redundancy in naming

Establish a set of standard nouns, verbs, and acronyms that are used for naming objects

Establish standards for versioning methods associated at the process model and artifact level to provide requirement traceability


Topics

Process Modeling

BPMN



XPDL

WS-BPEL


Future



Orchestration: Workflow, internal processes, private processes

Contained within one Pool

Choreography: Collaboration, global processes, B2B processes

Defined by the interaction between Pools


Orchestration

Orchestration defines processes that are internal to a specific organization

They are contained within a single Pool

Ship Order

Send

Invoice

Make

Payment

Receive

Order

Fill OrderAccepted

Accept

Payment

Close Order

Rejected

Su

pp

lier

Accepted or

Rejected?



Process Orchestration

A Process that uses other external Processes

It has control over the process

It is executable

A End-To-End System view from the point of one of the participants


Choreography

A Choreography process depicts the interactions between two or more business entities

Shown by the Message Flow between the Pools

Or a sequence of interaction (global) types of activities

Pa

tie

nt

Re

ce

ptio

nis

t/

Do

cto

r

Send Doctor

Request

1) I want to see doctor

Illness

Occurs

Send Appt.

Receive Appt.

5) Go see doctor

Send

Symptoms

Receive

Symptoms

6) I feel sick

Receive

Prescription

Pickup

8) Pickup your medicine

and you can leave

Send Medicine

Request

Receive

Medicine

Request

9) need my medicine

Receive

Medicine

10) Here is your medicine

Receive

Doctor

Request

Send Medicine

Send

Prescription

Pickup

Illness

Occurs

Request

Doctor

Arrange

Appt.

Arrange

Prescription

Pickup

Evaluate

Symptoms

Fill

Prescription

Pick-up

Prescription



Choreography

Away to define message interaction between systems

It is not executable

Purchase

Order

Message

Rejected

Message

Order

Response

Message

Shipment

Message


Choreography

Organization

A

Organization

B

Purchase

Order

Message

Rejected

Message

Order

Response

Message

Shipment

Message

WSDL


Orchestration Example Organization B

Purchase Order Process

Purchase

Order

Message

Rejected

Message

Order

Response

Message

Shipment

Message

Start

Process

Check

Inventory

Reject

request

Approve

Accepted

request

Dispatch

Shipment

Reply to

Customer

Reject

Reject

Approved

OrchestartionChoreography


Topics

Process Modeling

BPMN



XPDL

WS-BPEL


Future


XPDL

XML Process Definition Language (XPDL)

A modeling language for process definition

Goals

Process definition model interchange between tool


Origins of XPDL

WPDL 1.0 (10/1999)

Workflow Process Definition Language

XPDL 1.0 (10/2002)

XML version of Process Definition Language

XPDL 2.0 (10/2005)

Incorporated BPMN constructs

A Workflow Management Coalition (WFMC) specification

WfMC Reference Model Interface 1 – process definition


XPDL 2.0 Purpose

A persistent format for BPMN

XPDL provides an XML file format

BPMN provides a graphical notation

Back compatible with XPDL 1.0

XPDL and BPMN address the same modeling space


Tool Specific Graphical Information

Each tool adds its own graphical information

Same XPDL can be displayed different by different tools


XPDL – BPMN

BPMN

Graphical notation

No file format

XPDL

XML file format

No graphics

Both are modeling languages

Addressing the same process space


Topics

Process Modeling

BPMN



XPDL

WS-BPEL


Future


WS-BPEL

Business Process Execution Language (BPEL)

An executable process definition language for web services composition

Goal

Complement the Service Oriented Architecture (SOA) with executable process definitions


Origins of BPEL

BPEL4WS 1.0 (7/2002)

Original proposal from BEA, IBM, Microsoft

Combined ideas from IBM’s WSFL and Microsoft’s XLANG

BPEL4WS 1.1 (5/2003)

Revised proposal submitted to OASIS

With additional contributions from SAP and Siebel

WS-BPEL 2.0 (4/2007)

Approved as OASIS standard

An OASIS specification


XPDL and BPEL

XPDL

Modeling language

For process diagram interchange

Graphical information

Simulation information

Participants

Etc.

BPEL

Executable language

For Web Services composition

Transaction semantics

Abstract processes

Nicely fit in Web Services stack

Etc.


BPEL and XPDL Usage Patterns

Simulation Tools

Modeling Tools

Design Tools

Execution Engine B

Execution Engine A

XPDL

XPDL

XPDL + Extensions BPEL

BPEL

XPDL


Topics

Process Modeling

BPMN



XPDL

WS-BPEL


Future


BPMN


BPEL Engine BPM Engine

XPDL BPEL

Web Services

BPMN

Process modeling

XPDL

File format

BPM functionality

BPEL

BPM functionality

Web services composition

one way bidirectional

Pool 2

Pool 1


Topics

Process Modeling

BPMN



XPDL

WS-BPEL


Future


Current Standards Situation

BPM

N S

pecifi

catio

n

Diagram Projection of Metamodel

BPMN 1.1

BPDM 1.0 Implicit BPMN

Semantics

Current

Implementations

Not in

BPMN

XDPL 2.0

Model Exchange


Planned Standards Situation

BPMN 2.0 Specification

Diagram Projection of Metamodel

BPMN 2.0

BPDM 2.0

XDPL 3.0?

Model Exchange


Thank You!

Technology

2007 11-09 mm (costa rica - incae cit omg) modeling with bpmn and xpdl