BPMN方法与风格：解析业务流程标准与实战指南

需积分: 9 131 浏览量更新于2024-07-18 收藏 3.4MB PDF 举报

BPMN方法与风格指南（2d版）深入探讨了业务流程模型和符号语言（Business Process Model and Notation，简称BPMN）在企业流程设计中的重要性。BPMN之所以被广泛接受并成为业界标准，是因为它是由对象管理组织（Object Management Group，OMG）维护的一个多供应商标准，这使得不同工具供应商能够实现互操作性，从而提高了跨平台的一致性和标准化。该书不仅仅是一本BPMN符号和形状的词典，而是以独特的视角来阐述如何理解和掌握这一过程建模标准。它基于两个核心原则展开：方法论和风格进化。作者强调，虽然BPMN 2.0版本经历了漫长的发展，但理解其背后的逻辑和应用场景更为关键。书中首先讨论了模型的含义，指出业务流程建模远不止于图形符号的使用，而是涉及概念框架的理解。活动和过程这两个基本概念被逐一解析，活动是构成流程的基本单元，而过程则代表了整个业务流程的执行路径。通过实例展示如订单处理过程，读者可以学习如何处理异常情况、泳道和活动类型，以及子过程的嵌套和层次结构。章节三着重通过实例演示如何在BPMN中表达过程逻辑，如协调（orchestration）、并行分支与合并、协作和黑盒池（用于表示参与者或系统组件）。同时，作者解释了起始事件（Start Events）、过程实例（Process Instance）以及顶层图的作用。第四个部分深入剖析了Level 1工具箱，包括各种类型的活动，如任务（Task）、发送与接收任务、手动与用户任务的区别，以及规则任务、子过程和非结构化子过程的使用。这些内容有助于读者根据实际需求选择合适的符号和结构。 BPMN方法与风格指南提供了丰富的实战经验和理论支持，帮助读者从概念层面到实践技巧全面掌握BPMN 2.0，以有效地进行业务流程建模和优化。通过阅读此书，模型者和工具开发者能够更好地理解和运用这一行业标准，提升工作效率和模型质量。

hierarchical modeling style, in which subprocesses are expanded on separate hyperlinked

diagrams, while others are geared toward “flat” process models with inline subprocess

expansion. Also, BPMN tools vary widely in the non-BPMN information they describe,

such as problems and goals, KPIs, organizational roles, and systems.

Prior to version 2.0, the BPMN spec did not even attempt to describe

requirements for “conformance”. As a consequence, many tools claim to support BPMN

but really do not. The BPMN 2.0 spec does spell out requirements for Process Modeling

Conformance. The Descriptive and Analytic subclasses, equivalent to our Level 1 and

Level 2 palettes (in fact, borrowed from my BPMN training!), specify the elements in

non-executable models that must be supported to claim conformance. The BPMN-I

Profile, described in Part IV of the book, provides serialization rules for non-executable

models that allow tool vendors to interchange those models automatically. At this

writing, no BPMN tool vendor yet claims full conformance with the BPMN-I Profile, but

some are close.

All this is a long way of saying that even though BPMN is a standard, BPMN

tools are not all the same, and your choice of tool may significantly impact your ability

to create “good BPMN” consistently.

The diagrams used in this book were created using Process Modeler for Visio, an

add-in to Microsoft Visio from itp commerce ltd, of Bern, Switzerland.

[5]

This is the tool

I primarily use in my BPMN training and certification. A key reason is it has the style

rule validation built in. Also, it supports the full BPMN 2.0 element set with proper

XML serialization and model export and import, and simplifies hierarchical modeling as

recommended by the Method.

A major strength of BPMN is that users enjoy a wide choice of

tools. Nevertheless, some readers will surely find that the BPMN tool they are currently

using does not support some of the shapes, symbols, and patterns described in this book.

One possible reason is that the tool is based on BPMN 1.x, while the book is based on

BPMN 2.0. Tool vendors are often loath to advertise which version of the standard they

support, so here is an easy way to tell.

If your tool includes a shape that looks like this

then it is based on BPMN 1.0. That was obsolete in 2008, so if you are serious

about process modeling, I would recommend upgrading your tool.

If your tool can draw a shape that looks like this

or a shape with a black envelope, like this

but not shapes like these

then it is probably based on BPMN 1.2. This is all right for Level 1 modeling, but

it doesn’t support important shapes such as non-interrupting event and data store. More

important, it doesn’t support the formal BPMN metamodel and XML interchange format.

xvii

Acknowledgments

I would like to acknowledge the efforts of two individuals in advancing the

standard and the Method and Style approach since publication of the original

edition. Without those efforts, this book could not have been written.

Robert Shapiro of Process Analytica, as member of the BPMN 2.0 Finalization

Task Force in OMG, succeeded where I could not, getting the Descriptive and Analytic

Process Modeling Conformance subclasses included in the compliance section of the

final BPMN 2.0 spec. Not only does this provide the only practical basis for model

interchange between tools, but it serves as official endorsement of the Level 1 and Level

2 palettes of BPMN Method and Style.

Stephan Fischli of itp commerce, maker of Process Modeler for Visio, has

continually added features to his BPMN tool that embrace and automate the Method and

Style approach. Notable examples include built-in support for style rule validation,

proper XML serialization, and import of global tasks and processes from external Visio

files. Good BPMN requires good tools, and Stephan’s is the best.

I also want to acknowledge the helpful responses of several individuals to my

questions on technical aspects of the BPMN 2.0 specification, including Matthias

Kloppmann of IBM, Ralf Mueller of Oracle, Denis Gagne of Trisotech, and Falko Menge

of Camunda.

I wish to thank Charles Souillard, Nicolas Chabanoles, and Aurelien Pupier at

BonitaSoft for providing the executable BPMN 2.0 model used in Chapter 23 and

answering my many questions about it. Thanks also to Carol Leyba of Leyba Associates

for great work on the cover design.

Finally, I would like to recognize those whose efforts will ultimately make this

book available in other languages and formats: Stephan Fischli and his team at itp

commerce (German translation), Miguel Valdes Faura and his team at BonitaSoft (French

translation), Brian Reale and his team at Colosa (Spanish translation), and Declan Chellar

for preparation of the Kindle version. Thanks to all of them for helping spread the word

on BPMN Method and Style.

Bruce Silver

October 2011

1. Bad BPMN, Good BPMN

BPMN stands for Business Process Model and Notation. For the vast majority of

BPMN users, the most important part is the N – the graphical notation – a diagramming

language for business process flows. The most important thing about it is that it is a

standard, maintained by the Object Management Group (OMG). That means it is not

owned or controlled by a single tool vendor or consultancy. You pay no fee or royalty to

use the intellectual property it represents. Today, virtually every process modeling tool

supports BPMN in some fashion, even though a few vendors may grumble that their own

proprietary notation is better or more business-friendly.

A key benefit of a process modeling standard is that understanding is not limited

to users of a particular tool. The semantics are defined by the standard, not by each

tool. BPMN is an expressive language, able to describe nuances of process behavior

compactly in the diagram. At the same time, the meaning is precise enough to describe

the technical details that control process execution in an automation engine! Thus

BPMN bridges the worlds of business and IT, a common process language that can be

shared between them.

The Paradox of BPMN

BPMN’s popularity begins with its outward familiarity, especially to business

people. Its boxes and arrows, diamonds and swimlanes look a lot like traditional

flowcharts, which have been around for 25 years. And that was by design. But here is

the paradox of BPMN. While outwardly familiar, BPMN’s unique capabilities come

from ways in which it differs from traditional flowcharting.

One difference, as mentioned above, is that modelers may not make up their own

meaning for the standard shapes and symbols. BPMN is based on a formal specification,

including a metamodel and rules of usage. Its expressiveness derives from the extensive

variety of markers, icons, and border styles that precisely refine the meaning of the basic

shapes. It has rules that govern the use of each shape, what may connect to what. Thus

you can validate a BPMN model, and any BPMN tool worth using can do that in one

click of the mouse.

A second key difference from traditional flowcharts is that BPMN can describe

event-triggered behavior. An event is “something that happens” while the process is

underway: The customer calls to change the order; a service level agreement is in

danger of being violated; an expected response does not arrive in time; a system is down.

These things happen all the time. If your model represents the “real” process it needs to

say what should happen when those exceptions occur. BPMN lets you do that, and

visualize that behavior in the diagram itself.

Third, in addition to the solid sequence flow connectors depicting flow within a

process, BPMN describes the communications between the process and external entities

like the customer, external service providers, and other internal processes. Those

剩余249页未读，继续阅读

廖先贵

粉丝: 24
资源: 1

BPMN方法与风格：解析业务流程标准与实战指南

BPMN Method and Style, Second Edition, with BPMN Implementer's Guide

bpmnModel转bpmn

business process driven soa using bpmn and bpel (english edition)

bpmn-xpdl-and-bpel

activiti bpmn visualizer 和activiti bpmn有什么区别

nodejs 如何使用bpmn

python 有没有bpmn

vue bpmn-js

bpmn.js 流程图实例

bpmn.js bpmn-js-token-simulation

最新资源