Software transition: experience and lessons learned

While operating a software maintenance organization, the authors were faced with the challenge of accepting maintenance responsibility from a software developer for several systems. Transition of the first two systems was painful. Based on the experience gained, the authors developed procedures for transition. They believe that those procedures improve the ability of the maintenance organization to provide quality support. They discuss their experience in having large software systems transitioned to them for maintenance and lessons learned.<
>