In software engineering, the software configuration management ( SCM or S/W CM ) is the task of tracking and controlling changes in software, from a larger cross-disciplinary field of configuration management. SCM practices include revision control and baseline formation. If anything goes wrong, the SCM can determine what is changed and who changes it. If the configuration works properly, SCM can determine how to replicate it across multiple hosts.
The abbreviation "SCM" is also extended as a resource configuration management process and software changes and configuration management . However, "configuration" is generally understood to mask changes that system administrators typically make.
Video Software configuration management
Tujuan
Common SCM objectives are:
- Identify configuration - Identify configuration, configuration items and baseline.
- Configuration control - Implemented a controlled change process. This is usually accomplished by setting up a change control board whose primary function is to approve or reject all changes requests submitted against any baseline.
- Accounting configuration status - Recording and reporting all necessary information about the status of the development process.
- Configuration audit - Ensure that the configuration contains all of the intended sections and corresponds to the specifying document, including requirements, architectural specifications, and user manuals.
- Create management - Manage the processes and tools used to build.
- Process management - Ensure compliance with the organization's development process.
- Environmental management - Manage software and hardware that host the system.
- Team work - Facilitate team interactions associated with the process.
- Disability tracking - Ensure any defect has trace back to its source.
With the introduction of cloud computing the purpose of SCM tools has been joined in some cases. The SCM tool itself has become a virtual tool that can be used as a virtual machine and stored with status and status. Tools can model and manage cloud-based virtual resources, including virtual equipment, storage units, and software bundles. The roles and responsibilities of the actors have also joined the developers can now dynamically set an example of virtual servers and related resources.
Maps Software configuration management
History
The history of software configuration management (SCM) in computing can be traced back to the 1950s, when CM (for Configuration Management), initially for hardware development and production control, is being applied for software development. The initial software has physical footprints, such as cards, tapes, and other media. The first software configuration management is manual operation. With advances in language and complexity, software engineering, involving configuration management and other methods, is a major concern because of issues such as schedule, budget, and quality. Practical lessons, over the years, have led to definitions, and formations, procedures and tools. Finally, the tool becomes a system for managing software changes. Practice across industries is offered as a solution, either openly or ownership (such as Revision Control Systems). With the increasing use of computers, emerging systems dealing with a wider scope, including requirements management, design alternatives, quality control, and more; the tool then follows the organization's guidelines, such as the Capability Maturity Model from the Software Engineering Institute.
See also
- Application lifecycle management
- Comparison of open source configuration management software
- Comparison of revision control software
- Automate continuous configuration
- List of revision control software
- Pain matrix
- Infrastructure as Code
References
Further reading
- 828-2012 IEEE Standards for Configuration Management in System and Software Engineering . 2012. doi: 10.1109/IEEESTD.2012.6170935. ISBN: 978-0-7381-7232-3.
- Aiello, R. (2010). Best Practices Configuration Management: Practical Methods Working in the Real World (1st ed.). Addison-Wesley. ISBNÃ, 0-321-68586-5.
- Babich, W.A. (1986). Software Configuration Management, Coordinate for Team Productivity . First edition. Boston: Addison-Wesley
- Berczuk, Appleton; (2003). Software Management Configuration Pattern: Effective Team Work, Practical Integration (issue 1). 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. & amp; Tegarden, D. (2002). System Analysis & amp; Design: Object Oriented Approach with UML. Hoboken, New York: John Wiley & amp; Sons, Inc.
- Department of Defense, USA (2001). Military Handbook: Configuration management guide (rev A) (MIL-HDBK-61A) . Retrieved 5th January 2010, from http://www.everyspec.com/MIL-HDBK/MIL-HDBK-0001-0099/MIL-HDBK-61_11531/
- Futrell, R.T. et al. (2002). Qualified Software Project Management. Issue 1. Prentice-Hall.
- International Organization for Standardization (2003). ISO 10007: Quality management system - Guidelines for configuration management .
- Saeki M. (2003). Embedding Metrics into Information Systems Development Methods: An Application of Machine Method Techniques. CAiSE 2003, 374-389.
- Scott, J.A. & amp; Nisse, D. (2001). Software configuration management. In: Guides for Software Knowledge Techniques . Retrieved 5 January 2010, from http://www.computer.org/portal/web/swebok/htmlformat
- Paul M. Duvall, Steve Matyas, and Andrew Glover (2007). Sustainable Integration: Improve Software Quality and Reduce Risk . (1st ed.). Addison-Wesley Professional. ISBNÃ, 0-321-33638-0.
External links
- SCM and ISO 9001 by Robert Bamford and William Deibler, SSQC
- Using Cases and Applying Application Lifecycle Management
- Parallel Development Strategy for Software Configuration Management
- iNTCCM, International Certification for Professional Configuration Management
- SCM Certification, Software Configuration Management: Strategy, Technique & amp; Tools
Source of the article : Wikipedia
0 Comments