Appendix B Configuration Management Tools

The configuration management tool industry is well established in that there are a number of configuration management tools that have gained acceptance in the marketplace (e.g., Pure Atria's ClearCase, Continuus' Continuus, True Software's ADC/Pro, and Intersolv's PVCS, Starbase's StarTeam, MKS's Source Integrity, and Perforce Software's Perforce). Most of these tools are available for Unix and Windows PC platforms. Table B1 shows examples of configuration management tools.

The classification categories for configuration management tools need to match the evolution of a company's development, production, and maintenance needs. For example, a Class 1 tool would typically suit a small company or a research and development group that has a small number of releases and possibly no variant releases. A Class 2 tool would typically suit a medium- or large-sized company that did not have a lot of formal processes defined and was not focused on standards certification. They may have many variant releases and so need strong support for parallel development and build management of products and, therefore, more reliability from the configuration management repository. A Class 3 tool would typically suit a large corporation that had formal processes that need to be automated and that focused on process improvement and had developer and management and change needs similar to companies that use Class 2 tools.

TABLE B1 Examples of Client-Server Configuration Management Tools

Version-Control Tools (Class 1)

Developer-Oriented Tools (Class 2)

Process-Oriented Tools (Class 3)

Intersolv's PVCS

Pure Atria's ClearCase

Continuus' Continuus

MKS's Source Integrity

True Software's ADC/Pro

Platinum's Harvest

Starbase's StarTeam

 

SQL Software's PCMS (Product Configuration Management Software)

Microsoft's SourceSafe

 

 

Revision Control System (RCS)

 

 

Source Code Control System (SCCS)

 

 

Perforce Software's Perforce

 

 

Tower Concept's Razor

 

 



The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement



Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 59
--> Appendix B Configuration Management Tools The configuration management tool industry is well established in that there are a number of configuration management tools that have gained acceptance in the marketplace (e.g., Pure Atria's ClearCase, Continuus' Continuus, True Software's ADC/Pro, and Intersolv's PVCS, Starbase's StarTeam, MKS's Source Integrity, and Perforce Software's Perforce). Most of these tools are available for Unix and Windows PC platforms. Table B1 shows examples of configuration management tools. The classification categories for configuration management tools need to match the evolution of a company's development, production, and maintenance needs. For example, a Class 1 tool would typically suit a small company or a research and development group that has a small number of releases and possibly no variant releases. A Class 2 tool would typically suit a medium- or large-sized company that did not have a lot of formal processes defined and was not focused on standards certification. They may have many variant releases and so need strong support for parallel development and build management of products and, therefore, more reliability from the configuration management repository. A Class 3 tool would typically suit a large corporation that had formal processes that need to be automated and that focused on process improvement and had developer and management and change needs similar to companies that use Class 2 tools. TABLE B1 Examples of Client-Server Configuration Management Tools Version-Control Tools (Class 1) Developer-Oriented Tools (Class 2) Process-Oriented Tools (Class 3) Intersolv's PVCS Pure Atria's ClearCase Continuus' Continuus MKS's Source Integrity True Software's ADC/Pro Platinum's Harvest Starbase's StarTeam   SQL Software's PCMS (Product Configuration Management Software) Microsoft's SourceSafe     Revision Control System (RCS)     Source Code Control System (SCCS)     Perforce Software's Perforce     Tower Concept's Razor