Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Software configuration management
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Goals== The goals of SCM include:{{Citation needed|date=March 2008}} * Configuration identification - Identifying configurations, [[configuration item]]s and [[baseline (configuration management)|baselines]]. * Configuration control - Implementing a [[change control|controlled change]] process. This is usually achieved by setting up a [[change control board]] whose primary function is to approve or reject all change requests that are sent against any baseline. * Configuration status accounting - Recording and reporting all the necessary information on the status of the development process. * Configuration auditing - Ensuring that configurations contain all their intended parts and are sound with respect to their specifying documents, including requirements, architectural specifications and user manuals. * [[Build management]] - Managing the process and tools used for builds. * [[Process management (computing)|Process management]] - Ensuring adherence to the organization's development process. * Environment management - Managing the software and hardware that host the system. * [[Teamwork]] - Facilitate team interactions related to the process. * Defect tracking - Making sure every defect has traceability back to the source. With the introduction of [[cloud computing]] and [[DevOps]] 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.<ref>{{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}}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)