![]() It comes from a group sitting around the table looking at a printout of the diagram, discussing it, usually thinking about how it could be better.Įffectively that means two things: First, label everything in your diagrams – not just activities, but subprocesses, intermediate events, gateways, sequence flows, end events and message flows. But maximizing shared understanding doesn’t come from individuals privately examining your model through the tool, nor from digging through 100 pages of documentation. The BPMN spec describes various shapes and connectors that print in the diagram, plus supplementary detail in attributes visible only through the modeling tool or in the detailed documentation that can be generated using the tool. This is absolutely fundamental, but is routinely ignored by beginning modelers. Make the process logic visible in the diagram.To illustrate the point, here are ten tips for effective modeling in BPMN. To do process modeling effectively, you need to go beyond the spec and learn a basic methodology, best practices, and specific diagram patterns to use in common situations. ![]() The BPMN specification presents lots of technical definitions and rules, but it does not teach you how to create process models that are effective in their primary mission - maximizing shared understanding of the as-is or to-be process.
0 Comments
Leave a Reply. |