Subversion – IBM DOORS Integration Overview
In an Application Lifecycle Management (ALM) ecosystem, the choice of systems, and the collaboration between the cross-functional teams play a great role. While the choice of systems impacts the productivity of a team, cross-functional collaboration brings in collective wisdom to make better decisions, faster. Best-of-breed systems such as Subversion Integration with IBM DOORS (Both DOORS and IBM DOORS Next Generation) bring rich functionalities to the ecosystem and make the work of the product and development team easier.
With IBM DOORS (Both DOORS and IBM DOORS Next Generation) and Subversion integrated within the ecosystem, the product development has real-time visibility into the commits made by the development team. It is also easier for them to enforce authentic commits against each work item and access the changes/edits made to the commits from IBM DOORS itself.
How Subversion – IBM DOORS integration is beneficial for an enterprise
- Track commit volume, track commit trends and edits/changes to commit files in real time
- Enforce authentic commits to make sure each commit is happening against a scheduled and open work
With Subversion + IBM DOORS integration, enterprises can:
How OpsHub Integration Manager integrates Subversion and IBM DOORS
OpsHub Integration Manager integrates IBM DOORS (Both DOORS and IBM DOORS Next Generation) and Subversion bi-directionally. It ensures that all historical and current data is available to each user, in that user’s preferred system, with full context, in real-time. All the details related to a commit made against a work item in IBM DOORS can be tracked from IBM DOORS itself. For example, for each commit that development team makes in Subversion, Subversion synchronizes a ‘commit entity’ linked to the specific requirement id back to IBM DOORS. Each ‘commit entity’ includes information such as ‘who did the commit?’, ‘when was the commit done?’, and ‘which part of the code was committed?’.
Popularly synchronized entities
Use Case: Subversion integration with IBM DOORS
Problem statement: Lack of commit traceability in the Application Lifecycle Management (ALM) ecosystem can lead to compliance as well as other issues.
Solution:If IBM DOORS (Both DOORS and IBM DOORS Next Generation) and Subversion are integrated using OpsHub Integration Manager, there will be complete traceability for each requirement in the ecosystem.
- The Product Manager creates a ‘business requirement’ in IBM DOORS.
- The development team works on the requirement, tests it, and then commits it in Subversion against the ‘requirement id’ specified in IBM DOORS.
- For each commit that happens from the development team, OpsHub Integration Manager creates a ‘commit entity’ linked to the specific requirement id back to IBM DOORS. Each ‘commit entity’ includes information such as ‘who did the commit?’, ‘when was the commit done?’, and ‘which part of the code was committed?’.
- From Doors, user can create reports to see commit trend, modules touched in a given release, number of people working on a given feature or project and so on.
Benefits of integration for Subversion and IBM DOORS users
- Each commit can be traced back to its respective workitem at any given point in time from Subversion itself
- Enforced checkpoints ensure that no mandatory steps/checks are missed while making a commit – this leads to high success rate for commits
IBM DOORS Users
- Complete traceability from IBM DOORS to source code in Subversion
- Visibility into the progress of development work, the volume and quality of commits made with full context, in real-time
- Reduced dependency on manual communication to track the completion of a task