Learner
CHAPTER 7 SOFTWARE CONFIGURATION MANAGEMENT
John A. Scott and David Nisse Lawrence Livermore National Laboratory 7000 East Avenue P.O. Box 808, L-632 Livermore, CA 94550, USA (925) 423-7655 scott7@llnl.gov Table of Contents 1 2 3 4 5 6 Introduction................................................................. 1 Definition of the SCM Knowledge Area .................... 1 Breakdown of Topics for SCM................................... 2 Breakdown Rationale................................................ 10 Matrix of Topics vs. Reference Material .................. 10 Recommended References for SCM......................... 11 SCI SCR SCM SCSA SDD SQA SRS 2 Software Configuration Item Software Change Request Software Configuration Management Software Configuration Status Accounting Software Design Description Software Quality Assurance Software Requirements Specification DEFINITION OF THE SCM KNOWLEDGE AREA
SCMP Software Configuration Management Plan
Appendix A – List of Further Readings............................ 13 Appendix B – References Used to Write and Justify the Knowledge Area Description ................................... 14 Appendix C – Rationale Details ....................................... 16 1 INTRODUCTION A system can be defined as a collection of components organized to accomplish a specific function or set of functions [IEEE 610]. The configuration of a system is the function and/or physical characteristics of hardware, firmware, software or a combination thereof as set forth in technical documentation and achieved in a product [Buckley]. It can also be thought of as a collection of specific versions of hardware, firmware, or software items combined according to specific build procedures to accomplish a particular purpose. Configuration management (CM), then, is the discipline of identifying the configuration of a system at distinct points in time for the purpose of systematically controlling changes to the configuration and maintaining the
John A. Scott and David Nisse Lawrence Livermore National Laboratory 7000 East Avenue P.O. Box 808, L-632 Livermore, CA 94550, USA (925) 423-7655 scott7@llnl.gov Table of Contents 1 2 3 4 5 6 Introduction................................................................. 1 Definition of the SCM Knowledge Area .................... 1 Breakdown of Topics for SCM................................... 2 Breakdown Rationale................................................ 10 Matrix of Topics vs. Reference Material .................. 10 Recommended References for SCM......................... 11 SCI SCR SCM SCSA SDD SQA SRS 2 Software Configuration Item Software Change Request Software Configuration Management Software Configuration Status Accounting Software Design Description Software Quality Assurance Software Requirements Specification DEFINITION OF THE SCM KNOWLEDGE AREA
SCMP Software Configuration Management Plan
Appendix A – List of Further Readings............................ 13 Appendix B – References Used to Write and Justify the Knowledge Area Description ................................... 14 Appendix C – Rationale Details ....................................... 16 1 INTRODUCTION A system can be defined as a collection of components organized to accomplish a specific function or set of functions [IEEE 610]. The configuration of a system is the function and/or physical characteristics of hardware, firmware, software or a combination thereof as set forth in technical documentation and achieved in a product [Buckley]. It can also be thought of as a collection of specific versions of hardware, firmware, or software items combined according to specific build procedures to accomplish a particular purpose. Configuration management (CM), then, is the discipline of identifying the configuration of a system at distinct points in time for the purpose of systematically controlling changes to the configuration and maintaining the