Taming the legacy systems


I'm interested! Votes: 9

A little bit about our experience organizing maintenance and support of legacy source code systems operated by the customer. Problems, tasks, approaches and solutions. Is it real to give a source code of your maintained system to be supported by the external company and not to get lots of new problems?

Legacy systems specifications

  • Technology, specialists, environments.
  • Knowledge and skills in the system. Operation and development
  • Constraints and opportunities for maintenance and support

The main task of dealing with legacy systems

  • Support
  • Development
  • Integration
  • Migration

Approaches to solving problems

  • Organizational
    • Competence Center
      • Organization
      • Team profile
      • Where can I get the experts?
      • Motivation issues
    • External Resources.
    • Interaction with the customer team.
  • Stages of building a competence center.
    • Education (what, how and why).
    • Formation (environments deployment, the main tasks, how to determine that everything is ready)
    • Use competence center
  • Technical
    • Development and test environments.
    • Source code managing.
    • «Knowledge management.”

Technical means of a “Knowledge management”

  • Approaches to the problem of knowledge management.
  • DCA architecture.
  • Implemented features and examples of their use.
  • DCA potential.

Conclusions.




Leave a comment

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

© CEE-SECR 2012 • Email:
Powered by WordPress. • Hosted by Hosting Community • Developed by i-Help