Google
 
   
Login
Username:

Password:


Lost Password?

Register now!
Search

Advanced Search
Main Menu
top books
Polls
What do you think about php-deluxe.net?
Excellent!
Cool
Hmm..not bad
What the hell is this?
encyclopedia
ODT (computing)
CamelCase
Revolution...
Silent Spring
KFAB
Global field
Manchester University...
recommendation
compare webbrowser
Freenet DSL
Who's Online
7 user(s) are online (6 user(s) are browsing encyclopedia)

Members: 0
Guests: 7

more...
browser tip
Unix Befehle
manual of unix befehle
recommendation!
Sponsored
partner

History of software configuration management

In Computing, software configuration management (SCM) can be approached from a historical perspective, in which CM (for configuration management) was used earlier, originally for hardware development and production control. History records tend to be based on tools and companies, and let concepts to a secondary plane.

  • Early 1960s or even late 1950s: IBM UPDATE.
  • Late 1960s, early .
  • Early 1970s: Unix Make.
  • By 1970 CDC update was an advanced product.
  • Circa 1972: Bell Labs paper describing the original Diff algorithm.
  • 1972, with an for UNIX (used diff for comparing files).
  • 197x: Pansophic s PANVALET was an early source code control system for the mainframe market. They were based in Lisle, Illinois.
  • 1975: Pr Pressor s work eventually grew into a commercially available product called Change and Configuration Control (CCC) which was sold by the SoftTool corporation.
  • Revision Control System (Revision Control System, Walter Tichy).
  • Early 1980s: Patch (Unix) (around 1988, Larry Wall).
  • 1984: Aide-de-Camp (ADC, later TrueChange around 1990, Richard Harter).
  • Concurrent Version System (Concurrent Versions System).
  • Early arch become viable.

    • Until the 1980s, as can be seen from a source such as Software Configuration Management by J.K. Buckle (1982), SCM could only be understood as CM applied to software development. Some basic concepts such as identification and baseline (well-defined point in the evolution of a project) were already clear, but what was at stake was a set of techniques oriented towards the control of the activity, and using formal processes, documents, request forms, control boards etc.

    It is only after this date that the use of software tools applying directly to software artefacts representing the actual resources, has allowed SCM to grow as an autonomous entity (from traditional CM).

    The use of different tools has actually led to very distinct emphases. Maybe one can pick up three:

  • traditional CM for Software, typically around )
  • line oriented management, based on patches or )
  • focused on /clearmake)

    • =See also=

    Revision control