One of the 9 intermediate events in BPMN is the message intermediate event. There are two ways to use the message intermediate event, as an element in the sequence flow, or as an attachment to the boundary of an activity for exception processing. See how to use message intermediate events in a sequence flow. [Updated with correction of glaring error on Aug 22nd, 2006]
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Undefined Intermediate Events
There are 9 different intermediate events in BPMN. One of them, called the none intermediate event, is “undefined” in that it doesn’t specify a distinct behavior. Unlike the other intermediate events, the none intermediate event has a single interpretation, and will only be used with a specific methodology.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Introduction to Intermediate Events
Intermediate events are one of the more complex and expressive elements of BPMN diagrams. Here we introduce the different intermediate events.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – How To Use End Events (Part 2)
This is part two of a two part article. The first part is “How To Use End Events (Part 1)”. End events describe how a process ends. Often, the end of one process can initiate other behaviors within a business process. Like death and taxes, every business process has an end. Sometimes more than one.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – How To Use End Events (Part 1)
End events describe how a process ends. Often, the end of one process can initiate other behaviors within a business process. Like death and taxes, every business process has an end. Sometimes more than one.
Product Management / Requirements
Posted on:
Inside Out is Backwards – Feature Focused or Goal Driven
Kathy Sierra has another great post on the problems people face when using products. One of the sources of the problems is when engineers think “from the inside out” and focus on features or capabilities. People have goals, and they want to achieve goals, not use capabilities.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Digging Artifacts
Artifacts are more than business detritus. Documents are created in business processes that represent actionable information. See how to represent these useful artifacts in business process modeling notation.
Requirements / Requirements gathering / Software development / Testing
Posted on:
Quality and Requirements – You Got Chocolate In My Peanut Butter
Quality writers are writing about requirements. Requirements writers are writing about quality. Just like the Reese’s Peanut Butter Cup – Two Great Tastes that Taste Great Together. You can’t have one without the other.
Agile / Prioritization / Project Management
Posted on:
Agile Prioritization and Tracking
Stealing a couple cool ideas for managing project priorities with something you can touch.