Software Configuration Management (SCM), also known as software form management, or software construction management, referred to as software form management.

Software configuration management

Software Configuration Management (SCM), also known as software form management , or software construction management , referred to as software form management . Define the component projects of the software, control the changes of each project ( version control ), and maintain the version association between different projects so that the content of the software at any time during the development process can be traced, including certain software with Several combinations of important meanings, such as software content delivered to customers at a certain time.

software development
core actions
process need design project structure test debug deploy maintain
paradigms and patterns
Prototyping clean room incremental modeling waterfall model Agile software development spiral model
Methodology and Framework
Rapid application development DevOps extreme programming Team software process personal software program Dynamic System Development Methods MSF Scrum signboard V model FDD MDD iterative development Lean development Unify process
supportive behavior
Configuration management document quality assurance project management user experience
practice
ATDD behavior driven development continuous integration continuous delivery domain driven design pair programming stand-up meeting test driven development
tool
translater debugger Performance analysis GUI designer Modeling Integrated Development Environment Build automation Release automation test
Standards and knowledge systems
Capability Maturity Model Integration IEEE standards ISO 9001 ISO/IEC standards SWEDISH BOOK Project management knowledge system BABOK

The abbreviation of SCM has been expanded to "source configuration management" and "software change and configuration management". However, the term "configuration" generally refers to changes that can only be made by system administrators .

Purpose

SCM的目標一般包括以下幾項：

• 配置識別：識別配置、配置項目和基準。
• 配置控管：導入變更控管流程。該流程通常由變更控制委員會來執行，其主要的職責是核准或拒絕有悖任何基準的所有變更請求。
• 配置狀態報告：記錄和呈報與開發過程狀態相關的所有必要資訊。
• 配置稽核：確保這些配置包含所有預期內容，且備有完整的規定文件（包括要求、結構規範和使用者手冊）。
• 建構管理：管理用於建構的流程和工具。
• 流程管理：確保遵循企業組織的開發流程。
• 環境管理：管理承載系統的軟硬體。
• 團隊合作：促進流程中團隊彼此間的互動。
• 缺陷追蹤：確保可溯及每個缺陷的源頭。

隨著雲端運算的引進，SCM工具的用途有時已互相整合。SCM工具本身轉變為虛擬設施，可以在虛擬機上執行並保存狀態和版本。這些工具能管理並為雲端虛擬資源（包括虛擬設備、儲存設備和軟體套件）建立模型。如今，因為現在已經可以動態的啟用虛擬伺服器和相關資源，SCM管理人員的角色和職責已經與開發人員合併。

歷史

軟體配置管理（SCM）在運算領域的應用可以追溯至1950年代。當時，原先用於硬體開發和生產控制的CM（配置管理）概念，轉而應用於軟體開發。早期的軟體都有實體，如打孔卡、打孔帶、磁帶和其他媒介。第一個軟體配置管理需經由人為操作。隨著程式語言及其複雜性不斷進展，涉及配置管理和其他方法的軟體工程由於時程、預算和品質等因素而成為主要隱憂。多年來的實踐經驗，為軟體開發流程和工具提供定義並奠定基礎。而這些工具最終成為管理軟體變更的系統。業界普遍的做法，即是採用開放或專有方式（如修訂控制系統）來作為解決方案。隨著電腦的使用越來越普及，可處理大型任務範疇的系統也因應而生，包括需求管理、設計替代方案、品質控管等。隨後，工具均遵循企業組織的守則，如軟體工程學院建立的能力成熟度模型（CMM）。

参见

• 版本控制
• 變更管理 (工程)
• 軟體生命週期管理
• 版本控制软件比较
• 連續配置自動化
• 版本控制軟體列表
• 基礎架構即代碼

參考文獻

1. ^  Gartner and Forrester Research
2. ^  Amies, A; Peddle S; Pan T M; Zou P X. . IBM DeveloperWorks (IBM). June 5, 2012.
3. ^  "1988 "A Guide to Understanding Configuration Management in Trusted Systems" National Computer Security System (via Google （页面存档备份，存于）)

延伸閱讀

• . 2012. ISBN 978-0-7381-7232-3. doi:10.1109/IEEESTD.2012.6170935.
• Aiello, R. (2010). Configuration Management Best Practices: Practical Methods that Work in the Real World (1st ed.). Addison-Wesley. ISBN 0-321-68586-5.
• Babich, W.A. (1986). Software Configuration Management, Coordination for Team Productivity. 1st edition. Boston: Addison-Wesley
• Berczuk, Appleton; (2003). Software Configuration Management Patterns: Effective TeamWork, Practical Integration (1st ed.). Addison-Wesley. ISBN 0-201-74117-2.
• Bersoff, E.H. (1997). Elements of Software Configuration Management. IEEE Computer Society Press, Los Alamitos, CA, 1-32
• Dennis, A., Wixom, B.H. & Tegarden, D. (2002). System Analysis & Design: An Object-Oriented Approach with UML. Hoboken, New York: John Wiley & Sons, Inc.
• Department of Defense, USA (2001). Military Handbook: Configuration management guidance (rev. A) (MIL-HDBK-61A). Retrieved January 5, 2010, from MIL-HDBK-61 CONFIGURATION MANAGEMENT GUIDANCE （页面存档备份，存于）
• Futrell, R.T. et al. (2002). Quality Software Project Management. 1st edition. Prentice-Hall.
• International Organization for Standardization (2003). ISO 10007: Quality management systems – Guidelines for configuration management.
• Saeki M. (2003). Embedding Metrics into Information Systems Development Methods: An Application of Method Engineering Technique. CAiSE 2003, 374–389.
• Scott, J.A. & Nisse, D. (2001). Software configuration management. In: Guide to Software Engineering Body of Knowledge. Retrieved January 5, 2010, from http://www.computer.org/portal/web/swebok/htmlformat （页面存档备份，存于）
• Paul M. Duvall, Steve Matyas, and Andrew Glover (2007). Continuous Integration: Improving Software Quality and Reducing Risk. (1st ed.). Addison-Wesley Professional. ISBN 0-321-33638-0.

外部連結

• SCM and ISO 9001 by Robert Bamford and William Deibler, SSQC （页面存档备份，存于）
• Use Cases and Implementing Application Lifecycle Management （页面存档备份，存于）
• Parallel Development Strategies for Software Configuration Management （页面存档备份，存于）

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.