home

The Business Rules Approach

by David Wright

“The biggest risk to your company is not being able to change fast enough… Business Rules are the answer.” …Ron Ross 

I am a great appreciator of Mr. Ross. He has written extensively on the topic of Business Rules, offers excellent training on the subject, and is the keynote speaker at each year’s International Business Rules  Forum. I would like to start my own article on Business Rules with an ‘icebreaker’ he used on a seminar I attended.

AttachmentSize
The Business Rules Approach.pdf165.55 KB

Where do Rules stop and Data Handling Conditions begin?

I agree that you've presented an interesting article, the best bit is coupling Rules concepts with the ideas in the Zachman Framework.

Now, here's a struggle: Rules for an enterprise-wide, health insurance company include references to tabled data and the way that the system must deal with the data. The list of "rules" for handling 5 million subscriber's information are legion!

Where do "business rules" stop here when it comes to the conditional logic the code employs as it encounters data? I am encountering differing opinions.

IF
AND patient is member of
THEN route call to [member skill group S]
ELSE GOTO [play benefit detail-msg]

These rules are changing constantly; they do not fit the "atomic" definition of a BR, and they are dynamic, based on the market, the contract, etc.

I look forward to others' replies.

~Kimber
Dallas, Tx

    Sponsored Announcements & Special Offers

view counter

Whitepaper from HP - Why Focus on Requirements Definition Management in the Application Lifecycle?

Increasingly, smart businesses are looking much closer at requirements definition (RD) and requirements management (RM) (sometimes grouped together under the Gartner-coined phrase, requirements definition management (RDM)) to streamline the entire application lifecycle. Why? Because systematic and effective RDM captures software defects earlier in the lifecycle, and it reduces the overall likelihood that defects will be introduced. That’s important. How important? According to one study, the cost to fix a defect after delivery is more than 100 times the cost to fix it in the requirement and design phase. No business wants to be hit with that bill. Now to add to this the growing interest in agile development techniques as a way to deliver higher quality applications and we have an interesting recipe for success.

Download a Free Copy

view counter
© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group