-
Useful guidelines for documenting business rules in their various forms (and, like processes, there will most likely be more than one form/technology used).
-
Basic RuleSpeak 2.0 guidelines for expressing business rules in structured natural language. Available in Spanish, German, Dutch and English.
-
Using pools and lanes in BPMN.
-
More examples of signal use within BPMN. I love that we're finally starting to see a good number of posts about actual use cases for complex modelling concepts: that's a great indicator of the adoption trend.
-
An article by Tom Debevoise on a business rules approach, with strong tie-ins to BPM and analytics. Especially important to consider how analytics tie in with rules-based decisioning that occurs in the execution of a business process.
-
James Taylor on separating business rules and use cases, including some good links to other articles on the same theme. I have seen many cases of organizations who over-document use cases and requirements by including every possibly business rule; not only does this make the requirements gathering longer, but the rules tend to change fairly frequently. In most cases, the particular rules matter very little to design and implementation, particularly when they are embodied in a BRM, so this can be a huge waste of time.
Leave a Reply
