July 19, 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.

« Converging BPM and Business Rules Maturity Models | Main | More on rules and BPM »

February 14, 2007
Here's one way to strengthen weak application maintenance processes

I saw this Forrester piece on CIOs: Attack Weak Application Maintenance Processes That Stifle IT Productivity by Phil Murphy. He makes the great point that systems were built as if they would never have to change (instead of being built for change time) and that the current rapid pace of business change causes equally rapid systems change. Phil talks about the maintenance backlog winning the battle for application development resources and so limiting the ability of the IT department to add value. While I liked the paper, I felt that there was too much focus on the whole application - often there is a very variable level of maintenance between different parts of the application and I have discussed before a basic process for pulling out these high maintenance pieces and modernizing just them. There is a great customer story about renovating just the high maintenance/high value component from the DMV here in California. In general I think companies could well use business rules to improve application maintenance and that this could help particularly when modernizing legacy COBOL applications.

He made a couple of observations and recommendations I thought I would repeat:

  • Poor Knowledge Transfer Techniques Increase Maintenance Costs
    True. One of the attractions of using business rules to modernize legacy applications is the increased readability of business rules over code.
  • Use Tools And Technology To Leverage Greater Staff Productivity
    Could not agree more. You need to spend money to save money and, in this case I think companies could spend on enhancing some of their applications by moving the high-maintenance part over to business rules.
  • Streamline Maintenance Processes To Increase Innovation Capacity
    Build new systems to reduce future maintenance by using business rules to avoid write-only code

Technorati Tags: , , ,

Posted by jtaylor in Business Rules • Legacy Modernization |Digg This|Add to del.icio.us

Trackback Pings

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

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:
Getting Started with BPM
Date: Jul 29, 2008
Time: 12:00 PM ET
(16:00 GMT)

REGISTER TODAY!
Evolving Security Architectures and SOA for Better Business Collaboration
Date: Aug 06, 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