Summary: BPMN?s diagram semantics are expressive and precise, but the spec doesn?t tell you everything you need to know to create effective models. Here we go beyond the spec with nine tips for making your process diagram say exactly what you mean. Third of six parts. For text of the article, go to https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70c51475-3b7b-2a10-248c-f4cc7b4dc52c
Summary: A brief summary of the BPMN notation. BPMN describes process orchestration in terms of activities (tasks and subprocesses) connected by sequence flows. Branches, splits, and joins in the flow are modeled by various gateway types. Events specify how processes respond to signals received from external entities or other parts of the same process. Other parts of the notation are loosely specified and used to add business context only. Second of six parts.
[Posted 6 Sept 2007 on BPMInstitute.org] One of the most powerful features of BPMN is the least appreciated? by modelers and tool vendors alike. I?m talking about subprocesses. Most of the process models I have seen would be much improved if they were used more liberally, and more effectively. In BPMN, a process is viewed as a flow of activities, and an activity ? a rectangle in the diagram ? can signify only one of two things: a task, meaning it has no subparts of interest to the model, or a subprocess, meaning the activity has subparts of significance to the model.
If there is one standard that the BPM world can unite around, it's BPMN. Today, even those vendors initially reluctant to adopt it can no longer ignore it. But what exactly are the factors that drive this acceptance? How satisfied are end users of BPMN with the notation? Do user experiences on BPMN match those by BPA tool vendors? Jan Recker from the BPM Research Group at Queensland University of Technology is undertaking a worldwide survey on the use of BPMN by process modelers to shed light into this question.
After 3 days of "what is it?" and "where it's going" and "how great it's gonna be," attendees at the Gartner BPM Summit this week finally got to hear "how to do it" on the afternoon of the last day. Normally only a few diehards stick around to the bitter end, and I guess you can't blame Gartner for giving this slot to the outside consultants. Also, I had to compete with 4 other How-To sessions from topnotch guys like Paul Harmon and Tom Debevoise.
It's nuts to cram a 2-day course on BPMN into an hour and a half, but I guess I'm doing it anyway. If you're in San Diego at the Gartner BPM conference next week and staying around to the bitter end, check it out. I'm on Wednesday afternoon at 1:45. If you're interested in talking with me about the full course - either the online Flash video version or the 2-day classroom version, or possibly licensing it yourself - it's a good place to meet me.
I've been talking about it for a while, laboring over it for even longer. Now I'm announcing it: Process Modeling with BPMN, a comprehensive course on how to use the standard both correctly (per the OMG spec) and effectively - with a supplied best-practice top-down methodology - to model and analyze business processes.
This week OMG is putting on a 4-day workshop in San Francisco on Building a Service Oriented Architecture with BPM and MDA. Judging from the two sessions I attended, it's really a good program, kind of an IT perspective on BPM. Yesterday I got the chance to meet Stephen White, one of the principal authors of the BPMN spec, and hear about what it is, how it works, and where it's going... directly from the source.