BibTeX
@MISC{Schgfer_sophisticatedsoftware,
author = {Wilhelm Schgfer},
title = {Sophisticated Software Configuration Management},
year = {}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
Software Process technology as well as Software Confi-guration Management (SCM) has focussed very much on supporting the Idevelopment and evolution of a single soft-ware product rather than software product-lines. In the case of SCM this is particular harmful, because current SCM technology only provides very limited support to adjust a tool supporting SCM to the particular needs and require-ments of a company producing product-line software. Usually such a tool has a built-in process and to the most provides a shell-script like language to define certain responsibilities or development status attributes for the arti-facts produced during development and maintenance. There is virtual.ly no support to adjust a tool to e.g. the defi-nition of special workflows for change management and notification (cf. [l] for an overview). 2. Practical Experience This observation is underlined by our most recent expe-rience steming from a cooperative project with a large Ger-man software vendor. The department with whom we are collaborating, maintains a single software product of about 1 Mill LOC. Let‘s call this product X from now on. This software X in turn provides the functionality to maintain all information about product-line software in terms of cur-rent, previous, and planned releases, installation/de-instal-lation information about all sites where the software is used, distribution of the software components, on-line elec-tronic delivery and installation of new releases (in particu-lar component by component), incoming and handled error reports etc. Product-line software whose maintenance is supported by X includes e.g. banking applications managing a net-
Keyphrases
product-line software sophisticated software configuration management limited support large ger-man software vendor shell-script like language mill loc software process technology new release software product-lines development status attribute change management banking application error report etc built-in process single software product special workflow software confi-guration management on-line elec-tronic delivery installation de-instal-lation information cooperative project particular need single soft-ware product current scm technology particular harmful software component certain responsibility practical experience particu-lar component recent expe-rience steming
