SCM Comparison Matrix

AccuRev offers discounts on licensing for users trading-in existing SCM tools like ClearCase and Perforce.

	Subversionmore details »	Perforcemore details »	ClearCasemore details »	AccuRevmore details »
	Comparison Watch Videos	Comparison Watch Videos	Comparison Watch Videos	Data Sheet Watch Demo
Support for Complex Parallel and Distributed Development
Process Visibility	Branches displayed as folders—no global view of the software development process; branches are easy to create but graphical merge capabilities are limited	Branches displayed as folders—no global view of the software development process; branches are easy to create but graphical merge capabilities are limited	Base ClearCase requires expertise in creating branches and views and merging changes between them. UCM simplifies the complexity but constrains development processes	Graphical StreamBrowser provides complete visibility of the software development process and simple graphical branch and merge operations
Dynamic Restructuring	No dynamic restructuring capabilities	No dynamic restructuring capabilities	No dynamic restructuring capabilities	Drag-and-drop dynamic restructuring
Private Branching	Private branches must be created and maintained manually	Private branches must be created and maintained manually	Private branches must be created and maintained manually	Built-in private branching supports SCM best practices
Namespace Support	Namespace changes are not handled appropriately during a merge	Namespace changes are not handled appropriately during a merge	Full namespace support	Full namespace support to track and merge changes involving file and directory moves & renames
Integrated Change and Configuration Management
Integrated Issue Tracking	Revision numbers are used as change sets to provide basic change tracking	Changelists integrated with Perforce jobs provide basic change tracking	Base ClearCase requires triggers to integrate with issue tracking; UCM has built-in integration	Robust integration between SCM and issue tracking with built-in change packages
Change-based Workflow	Change sets do not allow developers to easily work per change instead of per-file	Job functionality has limited workflow capabilities	UCM provides a standard usage model that is not suitable for all software development methodologies	Complete change-based workflow fully supports Agile and other task-based methodologies
Built-in Merge by Change Set	Scripts needed in order to merge by change set	Scripts needed in order to work effectively by change set	Base ClearCase requires scripting to merge by change set; UCM provides change set merging capabilities, but confines users to the UCM usage model	Merge by change package functionality without the need for scripting
Change Set Visibility	Change set merges must be tracked manually by revision log comments or file attributes	Only partial visibility into which jobs have been merged into each branch	Limited visibility and traceability of changes, especially when multiple change sets are merged simultaneously	Complete visibility of which change packages have been merged into each software configuration