In the software world, it seems that SCM is an unfortunately overloaded acronym.
It can mean:-
Which one of these is the dominant term? Do they mean the same thing?
To me Source Code Management is essentially synonymous with Version Control. Whereas Software Configuration Management is a larger subject, which potentially includes Build and Release Management as well.
However looking on Wikipedia, it lists Subversion as a Software Configuration Management tool, which is at most only tangentially true.
Build and Software Management has come up before, but nothing definitive has been said on the matter, unfortunately.
Software configuration management. But for most of us that effectively means source code management.
The top three results on acronym finder are:
******SCM Supply Chain Management******SCM Software Configuration Management******SCM Source Code Management
Where the stars indicate the rank of the result.
So it looks like both are equally valid and equally used.
Software Configuration Management.
Generally, I use/hear Source Code Management when talking about, well, source code. On the other hand, if you're keeping config files (things in /etc, application-specific config files, etc.) in an SCM, then a lot of people expand the acronym to Software Configuration Management.
So its all about what you're managing ;)
来源：https://stackoverflow.com/questions/2575922/what-does-scm-stand-for