| 词条 | Software configuration management |
| 释义 |
In software engineering, software configuration management (SCM or S/W CM)[1] is the task of tracking and controlling changes in the software, part of the larger cross-disciplinary field of configuration management.[2] SCM practices include revision control and the establishment of baselines. If something goes wrong, SCM can determine what was changed and who changed it. If a configuration is working well, SCM can determine how to replicate it across many hosts. The acronym "SCM" is also expanded as source configuration management process and software change and configuration management.[3] However, "configuration" is generally understood to cover changes typically made by a system administrator. Purposes{{Prose|section|date=June 2014}}The goals of SCM are generally:{{Citation needed|date=March 2008}}
With the introduction of cloud computing the purposes of SCM tools have become merged in some cases. The SCM tools themselves have become virtual appliances that can be instantiated as virtual machines and saved with state and version. The tools can model and manage cloud-based virtual resources, including virtual appliances, storage units, and software bundles. The roles and responsibilities of the actors have become merged as well with developers now being able to dynamically instantiate virtual servers and related resources.[4] HistoryThe history of software configuration management (SCM) in computing can be traced back as early as the 1950s, when CM (for Configuration Management), originally for hardware development and production control, was being applied to software development. Early software had a physical footprint, such as cards, tapes, and other media. The first software configuration management was a manual operation. With the advances in language and complexity, software engineering, involving configuration management and other methods, became a major concern due to issues like schedule, budget, and quality. Practical lessons, over the years, had led to the definition, and establishment, of procedures and tools. Eventually, the tools became systems to manage software changes.[5] Industry-wide practices were offered as solutions, either in an open or proprietary manner (such as Revision Control System). With the growing use of computers, systems emerged that handled a broader scope, including requirements management, design alternatives, quality control, and more; later tools followed the guidelines of organizations, such as the Capability Maturity Model of the Software Engineering Institute. See also
References1. ^Atria (later Rational Software, now a part of IBM) 2. ^{{cite book | title = Software Engineering: A Practitioner's Approach | edition = 7th International | author = Roger S. Pressman | year = 2009 | publisher = McGraw-Hill | location = New York}} 3. ^Gartner and Forrester Research 4. ^{{cite journal | last=Amies | first=A |author2=Peddle S |author3=Pan T M |author4=Zou P X | title = Develop cloud applications with Rational tools | journal = IBM developerWorks | publisher = IBM | date = June 5, 2012 | url = https://www.ibm.com/developerworks/community/blogs/iaas_cloud/entry/develop_cloud_applications_with_rational_tools3}} 5. ^"1988 "A Guide to Understanding Configuration Management in Trusted Systems" National Computer Security System (via [https://books.google.com/books?id=CScMNjwwK8UC&printsec=frontcover&dq=configuration+management+systems&hl=en&sa=X&ei=bADiUcmJFs3FqQGG4oCYDg&ved=0CDkQ6AEwAA Google]) Further reading
External links
4 : Configuration management|Software engineering|IEEE standards|Types of tools used in software development |
| 随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识，基本涵盖了大多数领域的百科知识，是一部内容自由、开放的电子版国际百科全书。