We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

James Taylor's Decision Management

James Taylor

Keeping business rules out of your use cases with decisions

user-pic
Vote 0 Votes

Adrian Marchis had a nice article on Use Case Recycling by Extracting Business Rules. Now making sure decisions are identified explicitly in use cases avoids one of the seven deadly sins of decision management and is something I think is critical. Indeed I wrote an article on the topic on the same network as Adrian's - Using Decision Management to improve Requirements. I have also blogged before about the need to keep process, decisions (rules) and requirements nicely separated as one develops a specification and Scott Sehlhorst and I posted a slide deck on the topic too:

The bottom line is this:
  • Look for decisions in your use cases
  • Make them explicit
  • Track but don't embed the rules that drive them
This way your requirements will easily support decision management and business rules going forward.

James Taylor blogs about decision-management technologies such as predictive analytics and business rules, discussing how they deliver agility, improve business processes and bring intelligent automation to SOA.

James Taylor

James Taylor blogs on decision management for ebizQ, and is an independent consultant on decision management, predictive analytics, business rules, and related topics.

Sponsored Links

Fico

Subscribe

 Subscribe to this blog by RSS
Subscribe by email:

Recently Commented On

Recent Webinars

    Monthly Archives

    Blogs

    ADVERTISEMENT