Requirement sets for different product versions and the ability to diff them?
We have a set of requirements in RRC for a product version. We need to start a new version, so we would like to have another set of requirements for the new version. What is the recommended way of working to version control (or tie to a specific version of a product) a set of requirements?
Also, we would like to be able to diff the entire requirement sets between two versions of the product, so we could see what has changed on requirement level. What is the recommended tool to do that?
The problem is very similar to git for example, where we have the source code version controlled and we can diff two versions, apply tags to certain versions and so on. How is it working on the requirement level in RRC? Any keywords would be much appreciated.
Also, we would like to be able to diff the entire requirement sets between two versions of the product, so we could see what has changed on requirement level. What is the recommended tool to do that?
The problem is very similar to git for example, where we have the source code version controlled and we can diff two versions, apply tags to certain versions and so on. How is it working on the requirement level in RRC? Any keywords would be much appreciated.
Accepted answer
At the moment there are 2 functionality which could help you to do part of the job.
- you can create baselines at the project level.
- you can create collections of artifacts and compare 2 collections specifying the baseline
You can also create baselines on modules, but from what I remember you can't compare 2 baselines for a module
You can define the scope of a product version with a collection and link this collection to a development plan within RTC. At the beginning of your iteration your scope is not stabilized, but when you get a clear understanding of your requirements, the priorities and the effort associated, you probably have a milestone in your project where you validate this collection of requirements with a more or less formal review. You create a baseline.
These functionality can probably help you for serial working, not really for parallel working on requirements.
- you can create baselines at the project level.
- you can create collections of artifacts and compare 2 collections specifying the baseline
You can also create baselines on modules, but from what I remember you can't compare 2 baselines for a module
You can define the scope of a product version with a collection and link this collection to a development plan within RTC. At the beginning of your iteration your scope is not stabilized, but when you get a clear understanding of your requirements, the priorities and the effort associated, you probably have a milestone in your project where you validate this collection of requirements with a more or less formal review. You create a baseline.
These functionality can probably help you for serial working, not really for parallel working on requirements.