Info: Your browser does not accept cookies. If you want to put products into your cart and purchase them you need to enable cookies.

Unified Change Management For Subversion

View Full-Size Image

Unified Change Management For Subversion

Price: Call for Pricing

Lightweight, ALM (Application Lifecycle Management) for Subversion

Modelled on the principles of IBM Rational ClearCase Unified Change Management (UCM), UCM4SVN is a simplified version which takes these key concepts and applies them to Subversion.

UCM4SVN sits on top of Subversion and operates independently of any existing Subversion interface (including Subclipse, TortoiseSVN, RapidSVN, SmartSVN or plain command line). Operating in parallel, UCM4SVN allows the development team to manage activities and deliverables, increasing visibility and efficiency.

The primary purpose of UCM4SVN is to wrap a simple but effective structure around Subversion and raise the level at which developers are required to interact with Subversion thereby removing the need for the in-depth administration experience often associated with managing Subversion at this level.

The application of UCM4SVN to new or existing projects is simple:

File change requirements are grouped together as ‘activities’ according to the needs of the project. Activities can be a bug or enhancement, but can also be user-defined according to the specific needs of the project.
Each ‘activity’ has an easy to understand lifecycle. Traditionally, developers are ‘assigned’ activities and these are acknowledged as being ‘worked on’. Upon completion, these are marked as ‘closed’ and ready for integration.
Activities are delivered on a per-need basis to the main development branch quickly and easily through a ‘deliver’ option. When a developer has finished work on a particular change, the activity is quickly and easily checked in by an integration manager or project leader.
After an object has been changed, a new ‘baseline’ is created. By comparing between baselines, you can see the list of file changes and also the individual activities that contributed. This enables automation of release notes and greater visibility of the team and individual contribution.

UCM4SVN also allows for the establishment and enforcement of development policies, helping to minimise build problems by identifying conflicting changes and contributing activities earlier in the development process.

Contact us to find out more about the benefits of applying a UCM approach to your Subversion environment. Simplify your Subversion deployment, reduce training costs and increase project visibility in one easy to use interface with UCM4SVN.