Abstract
An organization that is evolving its software engineering environment needs an SCM tool that can evolve with the environment. SCM tools are available that can meet the long term needs of such organizations, but those tools are generally packaged in a way that, because of financial and managerial risks, makes them unacceptable for department level computing. SCM vendors are consequently excluded from a significant part of the SCM market, and users are forced to build custom SCM systems. The build-versus-buy dilemma could be resolved by a vendor-supplied SCM tool that is designed for incremental sale, delivery, and operation, where later increments are differentiated by functionality beyond that of earlier increments. Such a tool might be composed of separate, interoperable tool-sets.
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 1995 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Adams, C. (1995). Why can't i buy an SCM tool?. In: Estublier, J. (eds) Software Configuration Management. SCM SCM 1993 1995. Lecture Notes in Computer Science, vol 1005. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-60578-9_24
Download citation
DOI: https://doi.org/10.1007/3-540-60578-9_24
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-60578-2
Online ISBN: 978-3-540-47768-6
eBook Packages: Springer Book Archive