Product management requirements for SCM discipline

  • Tapani Kilpi
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1235)


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.


Product Management Customer Order Software Industry Software Production Change Request 
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.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. Ben-Menachem, M. 1994. Software Configuration Management Guidebook. McGraw-Hill Book Company. London.Google Scholar
  2. Bersoff, E. H. & Davis, A. M. 1991. Impacts of Life Cycle Models on software Configuration Management. Communications of ACM. August Vol 34 No 8.Google Scholar
  3. Buckley, F. J. 1993. Implementing Configuration Management Hardware, Software and Firmware. The Institute of Electrical and Electronics Engineers, Inc, New York.Google Scholar
  4. Compton, S. B.& Conner G. R. 1994. Configuration Management for Software. Van Nostrand Reinhold, New York.Google Scholar
  5. Dart, S. 1991. Concepts in Configuration Management Systems. Proceedings of the 3rd International Workshop on Software Configuration Management, June 1991, pp. 1–18.Google Scholar
  6. IEEE ANSI standard. 1987. IEEE Guide to Software Configuration Management. IEEE/ANSI Standard 1042–1987.Google Scholar
  7. 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.Google Scholar
  8. 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.Google Scholar
  9. Kotler, P. 1997. Marketing Management: Analysis, Planning, Implementation, and Control. Prentice Hall, Upper Saddle River, New Jersey 07458. pp 1–107.Google Scholar
  10. Kuczmarski, T. D. 1992. Managing New Products The Power of Innovation. Prentice Hall, Englewood Cliffs, New Jersey 07632.Google Scholar
  11. Nugent, N. & O'Donnell, R. 1994. The European Business Environment. The MacMillan Press Ltd, Houndmills, Bansingstoke, Hampshire RG21 2XS. pp 183–198Google Scholar
  12. Pine, J. B. 1993. Mass Customization The New Frontier in Business Competition. Harvard Business School Press, Boston, Massachusetts.Google Scholar
  13. Primer. 1996. VTT Electronics/Technical Research Centre of Finland.Google Scholar
  14. Reichenberger, C. 1994. Concepts and Techniques for Software Version Control. Software-Concepts and Tools. 15: pp 97–104.Google Scholar
  15. Trillium. 1994. Trillium: Model for Telecom Product Development & Support Process Capability. Bell/Canada. Release 3.0, December. 118p.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1997

Authors and Affiliations

  • Tapani Kilpi
    • 1
  1. 1.Department of Information Processing ScienceThe University of OuluOuluFinland

Personalised recommendations