Business processes often need to be cancelled. An error condition can cause a process to terminate, or an incoming message can cause a process to be terminated. Error conditions occur within transactional subprocesses and a cancel intermediate event is used to describe any special cancellation steps.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Play Catch With Intermediate Errors
Business Processes might start out as easy-to-diagram simple processes. Over time, these processes get more complex, as they have to deal with real-world considerations and unanticipated situations. Things can go wrong. Classical flow diagramming gets complex when dealing with errors or exceptions in a process, while BPMN modeling keeps things simple.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
Approval Process Pain Management
Gathering requirements is a fun job. But once they are gathered and documented, we have to get them approved before anyone can use them. Approval is important. We can do it the easy way or we can do it the hard way.
Consulting / Presentation / Requirements management software
Posted on:
Building the Case for Requirements Management Tools
Marcus Ting-A-Kee has assembled a great presentation on the value to his company of requirements management tools. In addition to creating the presentation and sharing it with all of us, he shares the process of creating the presentation in several articles.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Never Too Late For An Intermediate Timer Event
Business process modeling in the real world requires us to represent how processes deal with exceptions, delays and deadlines. Intermediate timer events can be used to model deadlines and the business processes for handling them. See an example of how to model a business process where two deadlines expire and the business responds.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Wait For An Intermediate Timer Event
Business process modeling requires us to model behaviors of people and organizations. Those behaviors often involve waiting. Prescribed delays, or waiting for a specific time or date is what we can represent with an intermediate timer event in the sequence flow of a BPMN diagram. This article shows an example of how to model this delay in a business process.
Requirements / Software development
Posted on:
Alphabet Soup – Requirements Documents
This is my requirements document. There are many like it, but this one is mine. My requirements document is my life. [Kubrick, with some editing]. Michael provides a comparison of requirements documentation formats seen in the wild. A good companion to our earlier piece, Michael provides some “what to expect” guidance about how different companies use the different documentation formats. Check it out.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Boundary Intermediate Message Events
Intermediate message events can be placed on an activity boundary in BPMN. This use represents a form of exception handling for a task or sub-process, in response to an incoming message. This is a very different behavior than the ones we previously described, which show how to use intermediate message events in the course of the normal sequence flow of a business process.
Administrivia / Business Process Modeling / Requirements / Requirements gathering
Posted on:
Yesterday’s BPMN Post Was A Big Fat Lie
Yesterday’s post contained a pretty significant mistake (aka “Big Fat Lie”). I showed a diagram that was in violation of the BPMN specification for intermediate message events. The post has been corrected, showing both the “bad” instructions, and the associated corrections. The proper way to use intermediate message events within […]