Software transition: A case study

Thomas M. Pigoski, Joanne Sexton

Research output: Chapter in Book/Report/Conference proceedingConference contribution

3 Scopus citations

Abstract

One of the major topics during discussions regarding life cycle software support is the transition of the support responsibility from a software developer organization to a software maintenance organization. In many cases these are entirely different and distinct organizations, and the difference creates some problems and necessitates sound planning. The authors describe a case study of the successful transitioning of two systems from the developer to a new software maintenance organization. The following issues were addressed: When is the hardware required for the SSA (software support activity)? What is the hardware suite that will be provided to the SSA? What level of manning is required? What is the phasing plan for the agreed upon manning level? When is the manning agreed upon? Does the SSA get involved during development of the system? Does the SSA play an active role in preliminary design reviews and Critical Design Reviews?

Original languageEnglish (US)
Title of host publicationConference on Software Maintenance
PublisherPubl by IEEE
Pages200-204
Number of pages5
ISBN (Print)0818620919
StatePublished - Nov 1 1990
Externally publishedYes
EventProceedings of the 1990 Conference on Software Maintenance - San Diego, CA, USA
Duration: Nov 26 1990Nov 29 1990

Publication series

NameConference on Software Maintenance

Other

OtherProceedings of the 1990 Conference on Software Maintenance
CitySan Diego, CA, USA
Period11/26/9011/29/90

    Fingerprint

ASJC Scopus subject areas

  • Software

Cite this

Pigoski, T. M., & Sexton, J. (1990). Software transition: A case study. In Conference on Software Maintenance (pp. 200-204). (Conference on Software Maintenance). Publ by IEEE.