Features of Configuration Management

• File Locking

• Workspace

• Parallel Development

• Branching & Merging

• Conflicts

• Synchronization

• Audit Trails

• Integration with design, development, build, test and deployment tools

• Roll Back

• Supported Platforms
 File Locking

CM Tools Description
ClearCase ClearCase supports locking, but it is not required. A view is a
workspace, helps to modify the file/dir which is under source
control. All the elements in a view are virtual copies. Each
developer can create his own view and work on the elements
simultaneously
MKS Development teams can work flexibly and collaborate with a
streamlined locking model that supports optimistic locking; non-
exclusive locking and exclusive locking of files
Subversion Subversion supports locking files so that users can be warned
when multiple people try to edit the same file. A file can be marked
as requiring a lock before being edited, in which case Subversion
will present the file in read-only mode until a lock is acquired
PVCS PVCS works in a pragmatic locking mode
 Workspace

CM Tools Description
ClearCase A view provides a workspace where users access versions of file
and directory elements that are under source control
MKS Sandbox environments allow developers to create a private
workspace to explore changes, or update code without impacting
master project files
Subversion A Subversion working copy is an ordinary directory tree on your
local system, containing a
collection of files. Your working copy is your
own private work area
PVCS A PVCS workspace is a name for a location of the work files and
isn't as such the location itself. You define the location for a
workspace using the PVCS GUI clients. If this isn't specified the
default workspace for the current user is used
 Parallel development

CM Tools Description
ClearCase Allows teams to work on the same code or release at the same
time
MKS Sophisticated project sharing and refactoring support facilitates
parallel development, code sharing and reuse of software
components and requirements, lowering administration costs and
reducing the need for costly rewrites
Subversion Users can work in parallel by creating private branches on the
trunk, which is a main line of development
PVCS It enables multiple teams to safely engage in parallel development
without jeopardizing each other’s work. Promotion group
organization helps define and manage who can modify
code as it progresses from one stage of development to the next
 Branching & Merging

CM Tools Description
ClearCase Ability to easily resolve conflicts, reduce confusion, and get more
done in a short amount of time
MKS A graphical history view provides visibility into a project’s
development paths and branches. MKS Source Integrity
Enterprise's robust support for parallel branching and 3-way
merging
Subversion Automated assistance with managing the flow of changes between
lines of development, and with the merging of branches back into
their sources
PVCS Automated and consistent branching techniques can be defined
to support parallel development, promotion groups and labeling
strategies. These steps help foster reuse of code, which in turn
delivers cost-savings in future projects and reduces rework in
ongoing projects
 Conflicts

CM Tools Description
ClearCase ClearCase Merge manager will help the users to merge the code
from one branch to other. Merging can be done by using CLI or
GUI. The conflicts has to be resolved manually
MKS Streamline conflict resolution and improve application quality
through 3-way differencing and merging, automatic branching and
merging and graphical drag and drop merge
Subversion The Subversion command-line client (svn) offers various ways to
resolve conflicting changes, include interactive resolution
prompting. This mechanism is also made available via APIs, so
that other clients can offer interactive conflict resolution
appropriate to their interfaces
PVCS Visual differencing enables clear, side-by-side graphical
comparisons of revisions, including n-way comparison and merge.
Its automatic branch and merge capability speeds complex
development, while alerts of any conflicts requiring manual
resolution prevent program logic errors
 Synchronization

CM Tools Description
ClearCase ClearCase supplies a utility, syncreplica for synchronizing a
replicated VOB with a master VOB
Subversion Subversion supplies a utility, svnsync for synchronizing (via either
push or pull) a read-only slave repository with a master repository
PVCS PVCS supplies a utility, ‘sync' is always local, that is the site where
the perforce server is located
 Audit Trails

CM Tools Description
ClearCase Provides visibility of who is doing what and when – tracing the
origin and details of changes which helps meet compliance
mandates
MKS MKS Integrity’s repository maintains complete audit trails of test
plans, test cases and test results and their changes over time
Subversion A simple svn log command on the /branches URL will show the
entire history of your branch
PVCS Unique "foot printing" technology verifies inclusion of correct
source revisions . Stores a list of components or footprints and
reports at any time. Traces executables back to the specific
revisions of their source components. Ensures that an application
is calling a correctly built dynamic link library
 Integration with design, development, build, test and
deployment tools

CM Tools Description
ClearCase Integrations include IBM Rational ClearQuest (for change
management), IBM Rational Asset Manager (for asset reuse), IBM
Rational Build Forge (for software assembly and builds), and
more…
MKS Integrate process management and workflow, requirements
visibility, and metrics and measurement capabilities throughout
your daily development activities
Subversion Subversion is designed to be client/server from the beginning; thus
avoiding some of the maintenance problems which have plagued
CVS. The code is structured as a set of modules with well-defined
interfaces, designed to be called by other applications
PVCS Integration with PVCS Version Manager shortens build cycles with
repeatable, automated and accurate builds, while providing you
with a complete audit trail
 Rollback

CM Tools Description
ClearCase A config spec rule can “roll back” the critical file (in that user's
view) to a known “good” version. The merge utility can be used to
roll back a change permanently
MKS Recreate an exact replica of a past version through rollback
Subversion It is possible to roll back a change that has already been
committed
PVCS Can always revert to the latest good release. supports a well-
defined and tested rollback process.
 Supported Platforms

CM Tools Description
ClearCase Windows, HP-UX, AIX(R), SuSE, RHEL 3/4, Solaris 2.8/9/10,
OS/390, z/OS
MKS Windows Me, Windows NT 4.0, Windows 2000, Windows XP, and
Windows Server 2003
Subversion Windows Server 2003, XP, 2000, RHEL, Debian, Ubuntu, Solaris,
Mac OS X
PVCS Windows, Linux RH, SUSE, OpenVMS, Digital Unix, HP/UX,
Unixware, Dynix/ptx, Solaris 8 & 9