Software Configuration Management

Software Configuration Management is a software development support and control function.

Specializing in software building, installation packaging, change management and configuration management.

SCM ensures the integrity, reliability and reproducibility of software from conception to release to retirement.

• Software Builds
• Source Code Administration
• Install Packaging
• Change Management
• Configuration Management

SCM and the functions it normally encapsulates has been called by different names.

I have seen it called Integration, Build Masters Team, Software Engineering and Tooling.

Microsoft called their team, Logistics.

Which can easily been confused with the more traditional uses of the term in trucking and freight.

I have seen one place name their group Software Management and Delivery.

Which really seems to fit all aspects of SCM and it has a nice acronym, SMD.

However, SCM gets confused with other tools and processes that share the same acronym, SCM

• Supply Chain Management
• Service Center Management
• ITIL's Configuration Management
• Student Christian Movement

Software Configuration Management seems to be by far the most popularly used named for this function.

Almost all the source control tool vendors now call their tool a SCM Tool.

• IBM's Rataional ClearCase
• Serena's Dimensions
• MKS's Integrity
• Perforce
• Microsoft's Team Foundation Server

SCM Tools

• SCM Tools
• SCM Tools List
• Software Build Tools
• Installation Tools

In the end, it does not really matter what SCM is called.

Day in and day out, some team is going to be responsible for administering the source code, performing the software builds, installation packaging and managing software configurations.

We my as well call it wisely, SCM.

• SCMWise.com
• Software Build Best Practices
• What is SCM
• Why Use Source Control
• Why Use SCM