What is SCM?????????

Current definition would say that SCM is the control of the
evolution of complex systems. More pragmatically, it is the
discipline that enable us to keep evolving software products
under control, and thus contributes to satisfying quality and
delay constraints.
SCM emerged as a discipline soon after the so called
« software crisis » was identified, i.e. when it was
understood that programming does not cover everything in
Software Engineering (SE), and that other issues were
hampering SE development, like architecture, building,
evolution and so on.
SCM emerged, during the late 70s and early 80s, as an
attempt to address some of these issues; this is why there is
no clear boundary to SCM topic coverage. In the early 80s
SCM focussed in programming in the large (versioning,
rebuilding, composition), in the 90s in programming in the
many (process support, concurrent engineering), late 90s in
programming in the wide (web remote engineering).
Currently, a typical SCM system tries to provide services in
the following areas:

• Managing a repository of components
• Help engineers in their usual activities
• Process control and support