User:Vernon Miles Kerr/sandbox

Software Configuration Managment Overview "Software Configuration Management" (SCM) describes a subcategory of Software Development, or Computer Programming. More recent popular usage has subsumed SCM into a broader category, "Development Operations," (Dev Ops) which attempts to breakdown the historical "wall" between Software Development and Information Technology (IT)—between those creating and maintaining software and those creating and maintaining the hardware infrastructure upon which the software is being developed. ("IT" in this context ignores the broader familiar meaning of IT as the entire field of Information Technology) As of this writing, (mid 2017) It remains to be seen if "Dev Ops", will gain traction and fulfill its purported goal to unify both sides of the development equation or will go the way of other fads of terminology such as "Object-Oriented Programming" (OOP) "Rapid Development" (RD)  and RD's child method "Scrum."

SCM, however—even though having been involuntarily placed into Dev Ops is firmly established as its own discipline and as a necessary part of the software development process. A survey of large corporations, will show defined SCM or Software Configuration Management departments, usually headed by an engineer with the title of Software Configuration Manager.

Function SCM serves both as an auditing function (to ensure that a given development project is being conducted according to customer's requirements and specifications) and a literal control mechanism over the code being developed more...