July 09, 2008   Sign In |  About ebizQ |  Contact Us |  Join ebizQ Gold Club
James Taylor
James Taylor's Decision Management
James is one the leading experts in enterprise decision management, a published author and a principal of Smart (enough) Systems LLC. His blog discusses the use of decision management technologies like predictive analytics and business rules to deliver agility, improve business processes and bring intelligent automation to SOA.

« SOA Patterns - your chance to contribute | Main | Extract rules, don't integrate them »

December 18, 2007
Building alignment and compliance into your systems

Yesterday I saw an interesting article over on TechRepublic - Sanity check: The 10 biggest headaches of 2007 for CIOs and IT managers. It was a nice list and a couple of items struck me as being great justifications for taking a more thoughtful approach to decision management and the technologies of decision management. The two headaches in question were "Alignment between IT and business goals" and "Dealing with compliance". In both cases the author took a different perspective to mine which is that alignment and compliance, especially in combination, are great drivers for adopting decision management.
My perspective on these two issues is that, with companies automating more and more business processes, ensuring alignment and compliance means making sure that what is coded into the processes and services being automated is aligned and compliant. The best way I know for doing this is to focus on the decisions in those processes and to automate those decisions using business rules. Why does this work?

  • Decisions, business decisions, are one of the most critical areas where the business and IT must be aligned. Focusing on decisions explicitly is key
  • Business rules, being declarative and amenable to business user management, ensure that the decision logic can be developed collaboratively by the business and IT. This helps ensure alignment
  • Business rules are easier to check for compliance than code both because those who understand the regulations can read the rules (but probably could not read the code) and because it is very easy to tell which rules executed for which transaction and this makes it much easier to show compliance
Business rules used to manage decisions allow for the business and IT to collaborate, and ensure compliance, in the critical business logic that would otherwise be buried in code. They allow for alignment and support compliance and should be on your list of technologies to consider.

Posted by jtaylor in Business Rules • Compliance • Decision Technologies |Digg This|Add to del.icio.us

Trackback Pings

TrackBack URL for this entry:
http://www.ebizq.net/mt/mt-tb.cgi/2978

Comments Post a comment




Remember Me?

(you may use HTML tags for style)

We ask that you type your code (displayed below) in the text box.This code is an image that cannot be read by a machine. It prevents automated programs from submitting comments.


Code:



Most Recent ebizQ Blog Entries
ADVERTISEMENT
This Work
Accountability:The opinions expressed in this blog are solely representative of the blog's author, and not of ebizQ

Subscribe to our Newsletters
ebizQ Weekly Gold Club Update
Live Webinar Updates
Updates from ebizQ Partners
ebizQ SOA Update
ebizQ BPM Update
ebizQ Security Update
ebizQ BI Update
ebizQ Open Source Software Update
Virtual Show Newsletter
ebizQ Web 2.0 and the Enterprise
Your E-mail Address:
Changing Tires on a Moving Car
Case studies and solutions for governing the continuous evolution of complex SOA systems

Date: Jul 15, 2008
Time: 12:00 PM ET
(16:00 GMT)

REGISTER TODAY!
Roundtable Discussion: MDM's Role as a Critical Enabler for SOA
Date: Jul 16, 2008
Time: 12:00 PM ET
(16:00 GMT)

REGISTER TODAY!
Archived Webinars | Upcoming Webinars

Marketing Solutions | Feedback | About ebizQ | Unsubscribe | Privacy Policy | Site Map

Live Chat