How to solve the problem of loss of application knowledge


How to solve the problem of loss of application knowledge

  • The dearth of application knowledge is a solvable issue. Application mining tools and APM tools can solve the issue and have the potential to bring many additional benefits.
  • Fight the real problem. Most of the troubles that firms describe today as "legacy" issues are in fact problems with the loss of application knowledge. That problem is not unique to Cobol or Java - it is a symptom of the fact that we stop caring what happens to application knowledge at the end of the system's development lifecycle. Know which problem you are fighting, so that you can employ the right solution.
  • Recognise the start of application obsolescence. The productivity loss associated with the loss of application knowledge is what starts the cycle of application obsolescence.
  • Skyrocketing costs eventually trigger across-the-board cost-cutting, which exacerbates application knowledge loss. Fear of changing the application accelerates knowledge loss, beginning a death spiral for the application.
  • APM tools will bring the most benefit. The value derived from the management-level views that APM offers will far exceed the difference in cost between APM and mining tools. Unless that cost difference will kill the effort, implement APM instead of mining tools. Early implementers of APM tell Forrester that the ROI occurs in less than 12 months, and savings of 10% to 30% of the maintenance budget follow.

Source: Forrester Research


Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

This was first published in November 2005


COMMENTS powered by Disqus  //  Commenting policy