We work with a lot of business rules architects and we see that more and more of them are using decision modeling as part of their business rules management system (BRMS) implementations. I recently wrote a series of blog posts – 3 Reasons Rules Architects Are Adopting Decision Modeling – over on our company blog. You can find the posts here:
- #1 Business Engagement
Rules architects find that building a decision model (especially one using the Decision Model and Notation (DMN) standard immediately engages their business partners – business analysts, subject matter experts and business owners – because decision modeling let’s everyone see the forest not just the trees. - #2 Expanded Traceability and Impact Analysis
Decision models link the business context to the business rules, enabling traceability all the way to the knowledge sources that drive rules and impact analysis all the way to the business objectives. - #3 Using Agile Not Waterfall to Write the Rules
Unlike traditional rules-first approaches, decision models lend themselves to iterative development and agile project approaches.
Of course you need a decision modeling tool to make this work, one that is integrated with your BRMS. If you are interested, you can see how we have done this with our DecisionsFirst Modeler – BRMS integrations in action in these demonstrations:
- DecisionsFirst Modeler and IBM Operational Decision Manager
- DecisionsFirst Modeler and RedHat JBoss BRMS
