Consultants' Advisory Home Page Consultants' Advisory Home Page Reports Archive Register(Free) for the Online or Printed version of Consultants' Advisory

Business & software reviews
visit evaluationcentre.com

The Evaluation Centre's aim is to be the No.1 Software and technology assistant to decision makers with their IT requirements. Providing detailed Vendor reports, White papers, Case studies and Best practice guidelines

   

Home > 2001 > B&A Software (January) > Change Management - Part ...

You are not signed in to view the full issue > Sign In

Summary of Reports


 Access Accounting

 Cedar Group

 CODA

 Index Computer Systems

 NavisionDamgaard

 OpenAccounts

 QSP Group

 Sage Enterprise Solutions

 Strategix

 VBX

 Welcom Software



Management Briefings



 Market Overview | Part 2 | Part 3

 Expert Opinion

 Round Table | Part 2 | Part 3

 Trends Analysis | Part 2

 Strategy | Part 2

 Case Study

 Financial Management | Part 2

 Change Management | Part 2

 Case Study

Issue Summary

Trends like the internet are forcing finance professionals to increasingly change their software. Mike Dawson of MERANT shows how they can manage this process.

Living with change - Part 2 | Part 1

Go to Part 1

The following are some of the most common problems related to managing changes in ERP-based financial applications:

  • Change identification. You cannot determine, in a timely manner, what changes have been made to forms, reports, libraries or databases. It may not be immediately apparent what the vendor has changed, or what the users have customised, without laborious code sleuthing.
    Furthermore, database administrators and developers may spend hours attempting to find out why code works in TEST but not in PROD. They spend more hours determining why code that worked fine yesterday is broken today. What has changed?
  • Assessing the impact of change. It is not possible to perform impact analysis on modifications to forms, libraries and database objects in a timely manner. Other parts of the application will break, costing downtime and research time to resolve the problem.
    Inconsistencies will appear in the application because some modules needing modification will be missed.

    Read the rest of this article...

    If you are not registered with the site, please register now to read the rest of this page.

    If you are registered, please sign in to read the rest of this page.


Home > 2001 > B&A Software (January) > Change Management - Part ...