Abstract
Software industry is slowly starting to adopt the discipline of Software Configuration Management (SCM) to be a part of the daily routines of software development and production. Hardly anybody denies that plenty of advantages can be gained by using SCM capabilities in a company. However, in some occasions a company with a technically capable SCM-process has failed to reach an efficient level of software change process management. The problem with these companies has been a poorly organised collection and analysis of change needs information. The problems of this kind can be avoided by adopting a product and customer oriented view to the definition of the SCM-process.
This is a preview of subscription content, log in via an institution to check access.
Preview
Unable to display preview. Download preview PDF.
References
Ben-Menachem, M. 1994. Software Configuration Management Guidebook. McGraw-Hill Book Company. London.
Bersoff, E. H. & Davis, A. M. 1991. Impacts of Life Cycle Models on software Configuration Management. Communications of ACM. August Vol 34 No 8.
Buckley, F. J. 1993. Implementing Configuration Management Hardware, Software and Firmware. The Institute of Electrical and Electronics Engineers, Inc, New York.
Compton, S. B.& Conner G. R. 1994. Configuration Management for Software. Van Nostrand Reinhold, New York.
Dart, S. 1991. Concepts in Configuration Management Systems. Proceedings of the 3rd International Workshop on Software Configuration Management, June 1991, pp. 1–18.
IEEE ANSI standard. 1987. IEEE Guide to Software Configuration Management. IEEE/ANSI Standard 1042–1987.
Kilpi, T. 1996. Evaluating the Maturity of Software Product Management: A Case Study in Three Companies. Proceedings of the Ninth Australian Software Engineering Conference ASWEC '96 July 14 to July 18, 1996. IREE Society.
Kilpi, T. 1997. Choosing a VC/CM-tool: a Framework and Evaluation. Will be published in the 8th Conference on Software Engineering Environments SEE '97 8–9 April, 1997.
Kotler, P. 1997. Marketing Management: Analysis, Planning, Implementation, and Control. Prentice Hall, Upper Saddle River, New Jersey 07458. pp 1–107.
Kuczmarski, T. D. 1992. Managing New Products The Power of Innovation. Prentice Hall, Englewood Cliffs, New Jersey 07632.
Nugent, N. & O'Donnell, R. 1994. The European Business Environment. The MacMillan Press Ltd, Houndmills, Bansingstoke, Hampshire RG21 2XS. pp 183–198
Pine, J. B. 1993. Mass Customization The New Frontier in Business Competition. Harvard Business School Press, Boston, Massachusetts.
Primer. 1996. http://www.ele.vtt.fi/projects/primer/primer.htm. VTT Electronics/Technical Research Centre of Finland.
Reichenberger, C. 1994. Concepts and Techniques for Software Version Control. Software-Concepts and Tools. 15: pp 97–104.
Trillium. 1994. Trillium: Model for Telecom Product Development & Support Process Capability. Bell/Canada. Release 3.0, December. 118p.
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 1997 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Kilpi, T. (1997). Product management requirements for SCM discipline. In: Conradi, R. (eds) Software Configuration Management. SCM 1997. Lecture Notes in Computer Science, vol 1235. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-63014-7_14
Download citation
DOI: https://doi.org/10.1007/3-540-63014-7_14
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-63014-2
Online ISBN: 978-3-540-69063-4
eBook Packages: Springer Book Archive