| Recent
Articles |
2 Faces Of Demand Management
As I continue my journey through the terminology difficulties of modern IT management, one issue that keeps coming up (as recently as this week's IQPC IT Governance conference, where I spoke) is the...
An Appropriate S, G & A For "IT As A Business"?
Your CMDB budget depends on it...Last of tonight's triple play (I must be feeling inspired). Let's consider the "Run IT as a Business" concept. Let's say your IT budget is $250 million for a $25 billion corporation.
Specializations For Outsourcing
Google's in the press again, and this time about information security, and a host of other "specializations" that can be, and maybe should be outsourced. In "Out Souring the Grunge Work," I talked about taking...
Understanding The Basics Of ITIL
In the world of IT management, ITIL is the buzzword being heard around the globe. So what is ITIL and how does it affect your organization? Let's take a closer look! Today's IT management has become more and more complex causing organizations worldwide to seek...
Is IP Your Most Cost Effective Choice?
Too often a business assumes that IP based solutions are the best choice to satisfy their communication requirements. Particulalrly with convergence issues. But....don't get caught making a hasty decision.
Choosing The Right Project Management Software
Project management continues to become an important and popular topic today. This is understandable because project management done correctly will help an organization get better at what it does, and make...
|
|
02.22.07
The Risks Of Reuse And Business Rules
 By
James Taylor
Dian over at BPM Enterprise had this post that led me to this piece on The RIsks and Rewards of Reuse by Marcia Kaufman of Hurwitz & Associates.
Dian highlighted the problem of "Poor Process" as an issue from a BPM point of view but I was struck by a second point Marcia made - Poor Management of Code. She says:
"it goes without saying that the software code that codifies a specific business service may also change frequently"
and thus if you reuse the service widely you may have problems when it needs to change. It seems to me that business rules offers two benefits that help with this.
Firstly the use of business rules to define the service makes it easier to modify it and manage it over time.
Not only do business rules help eliminate write-only code, they also allow more effective IT and business collaboration on the logic of the service.
Because the business and IT can work together on the business rules changes are more likely to be right and more likely to be understood by the business, reducing impact analysis problems.
In addition business rules can be easily reused between services, while still being managed once in a rule repository.
This allows several similar services to be developed (helping to reduce unintended consequences) while still ensuring consistency and reuse because many of the rules are the same between them.
She goes on to say:
"A strategy for reuse of business services must include an approval process for changes which begins with the "owner" of the business service"
It seems to me that this too leads you inevitably to the use of business rules to help close the gap between IT and the business and deliver the gap between IT and the business that can be managed by the business.
Comments
About
the Author:
VP of Product Marketing with a passion for the technologies of decision automation. 15 years designing, developing, releasing and marketing advanced enterprise software platforms and development tools. Across the board experience in software development, engineering and product management and product marketing.
http://www.edmblog.com
|
|
