Advertisement

Untangling configuration management

Mechanism and methodology in SCM systems
  • Martin Cagan
SCM-4 Best Papers
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1005)

Abstract

There is considerable diversity in the SCM methodological needs of today's software teams. The SCM methods a team requires are a function of technical, social and corporate constraints that define how the project team must design, construct, test and deliver software.

Most commercial and academic SCM systems created to date support particular SCM methodologies. Some created specific mechanisms to support their methodology, while others simply support the methods that work given the constraints and limitations of their mechanisms.

If modern SCM systems are to be applicable to the broad spectrum of software development teams, the methodologies must be separated from the mechanisms, the mechanisms must be distilled into a flexible set of widely applicable capabilities, and the definition of methodologies using these mechanisms must be facilitated.

The purpose of this paper is to explore the mechanisms needed to support advanced SCM methodologies, and process-based software configuration management in general.

Keywords

Project Team Parallel Development Parallel Version Source Object Configuration Object 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Cagan M (1995). White Paper, Continuus Software Corporation.Google Scholar
  2. 2.
    Cagan M (1990). An Architecture for a New Generation of Software Tools, Hewlett-Packard Journal.Google Scholar
  3. 3.
    Courington W (1989). The Network Software Environment, Technical Report, Sun Microsystems.Google Scholar
  4. 4.
    Feiler P (1990). Tool Version Management Technology: A Case Study, SEI Technical Report SEI-90-TR-25.Google Scholar
  5. 5.
    Feiler P (1991). Configuration Management Models in Commercial Environments, SEI Technical Report SEI-91-TR-7.Google Scholar
  6. 6.
    Humphreys W (1989) Managing the Software Process, Addison-Wesley.Google Scholar
  7. 7.
    Jones C (1994). Assessment and Control of Software Risks, Prentice-Hall.Google Scholar
  8. 8.
    Leblang D (1985). The DOMAIN Software Engineering Environment for Large Scale Software Development Efforts, Proceedings of the IEEE Conference on Workstations.Google Scholar
  9. 9.
    Wiebe D (1990). Generic Software Configuration Management: Theory and Design, University of Washington, Department of Computer Science Technical Report 90-07-03.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1995

Authors and Affiliations

  • Martin Cagan
    • 1
  1. 1.Continuus Software CorporationIrvineUSA

Personalised recommendations