Software transition: A case study

Thomas M. Pigoski, Joanne Sexton

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

3 Citations (Scopus)

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
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

Computer software maintenance
Hardware
Life cycle
Acoustic waves
Planning

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.

Software transition : A case study. / Pigoski, Thomas M.; Sexton, Joanne.

Conference on Software Maintenance. Publ by IEEE, 1990. p. 200-204 (Conference on Software Maintenance).

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

Pigoski, TM & Sexton, J 1990, Software transition: A case study. in Conference on Software Maintenance. Conference on Software Maintenance, Publ by IEEE, pp. 200-204, Proceedings of the 1990 Conference on Software Maintenance, San Diego, CA, USA, 11/26/90.
Pigoski TM, Sexton J. Software transition: A case study. In Conference on Software Maintenance. Publ by IEEE. 1990. p. 200-204. (Conference on Software Maintenance).
Pigoski, Thomas M. ; Sexton, Joanne. / Software transition : A case study. Conference on Software Maintenance. Publ by IEEE, 1990. pp. 200-204 (Conference on Software Maintenance).
@inproceedings{b98f79a59172455ba3707821cbc52731,
title = "Software transition: A case study",
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?",
author = "Pigoski, {Thomas M.} and Joanne Sexton",
year = "1990",
month = "11",
day = "1",
language = "English (US)",
isbn = "0818620919",
series = "Conference on Software Maintenance",
publisher = "Publ by IEEE",
pages = "200--204",
booktitle = "Conference on Software Maintenance",

}

TY - GEN

T1 - Software transition

T2 - A case study

AU - Pigoski, Thomas M.

AU - Sexton, Joanne

PY - 1990/11/1

Y1 - 1990/11/1

N2 - 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?

AB - 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?

UR - http://www.scopus.com/inward/record.url?scp=0025509890&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0025509890&partnerID=8YFLogxK

M3 - Conference contribution

AN - SCOPUS:0025509890

SN - 0818620919

T3 - Conference on Software Maintenance

SP - 200

EP - 204

BT - Conference on Software Maintenance

PB - Publ by IEEE

ER -