If I am not mistaken, I believe you are talking about baselining requireents, not backing them up.

In Quality Center, a project administrator can create baselines that provide ''snapshots'' of a project at different stages of development. In the Management module-Libraries tab, the administrator first creates a library, which specifies the root folders from which to import the data. The administrator then creates the actual baseline, which comprises the latest checked in versions of every asset included in the library. The administrator can also import and share entire baselines from other Quality Center projects. When a project reaches an important stage in the project lifecycle, the administrator can create a new baseline of the files in the library at that point. In Quality Center, these baselines can be viewed and compared in their entirety. Note that baselines are supported in Quality Center 10.00 Enterprise and Premier editions only. They are not supported in Quality Center Starter edition.

Quality Center 10 indeed can baseline requirements. But an organization still needs to determine and follow a baseline strategy based on their software development and maintenance approach(s). Once that strategy is in place QC 10 can be the tool to implement the strategy.

Im not aware of a add-in for QC10 that does this. But you can use QC features to achieve what you have described when used in conjuntion with the Management module. There are three parts to this solution: Use the Management module to assign requirments and tests so that you can quickly see progress for a specific release Use the priority field and a custom sequence field to give a specific sequence then add a favourite that with a Filter to sort by Priority sequence. Use the Requirements coverage analysis to view progress of previous/current release/sprints as well as plan future sprints. Detailed explanation: Load all requirements into a single folder Assign a priority and sequence to each requirement Set a filter in the requirements tab to sort the display by priority then sequence, save this filter as a favourite so that you can re-call it quickly. -Assign requiremnets to a Cycle/Release. In the Coverage analysis view, set the Coverage analysis setting to display coverage for a specific Cycle/Releasee. This will allow you to track Progress of previous releases, reassign from one release to the next, change priority or sequence of all unassigned backlog items.

Thank You Captain Mercury, Steven Davis & Daniel for your response. yes this helps. Thanks, RS