In software engineering, Software Configuration Management (SCM) is the task of tracking and controlling changes in the software. Configuration management practises include revision control and the establishment of baselines.
SCM concerns itself with answering the question: somebody did something, how can one reproduce it? Often the problem involves not reproducing “it” identically, but with controlled, incremental changes. Answering the question will thus become a matter of comparing different results and of analysing their differences. Traditional CM typically focused on controlled creation of relatively simple products. Nowadays, implementers of SCM face the challenge of dealing with relatively minor increments under their own control, in the context of the complex system being developed.
SCM tools
Name | Vendor |
AccuRev | AccuRev |
AllFusion CA-Pan/LCM Configuration Manager | Computer Associates |
BitKeeper | BitMover |
Bugzilla | Mozilla Corporation |
Changelogic | Webmedia |
ClearCase | IBM Rational Software |
codebeamer | Intland |
Fossil | D. Richard Hipp |
Mercurial | Matt Mackall |
MKS Source | MKS |
PVCS Professional | Serena Software |
Perforce | Perforce Software |
PureCM | PureCM.com |
Visible System’s Razor | Visible Software |
Sablime | Lucent Technologies |
SharpForge | XP Software Services |
StarTeam | Borland |
Surround SCM | Seapine |
Synergy/CM | Telelogic |
Trac | Edgewall Software |
Vault | Sourcegear |
Visual Enabler | Soft Lab |
Visual Source Safe | Microsoft |
Visual Studio Team System | Microsoft |
Subversion (software) | Free Open Source Software (main sponsor is Collabnet) |
No comments:
Post a Comment