we are using contour to do our formal verification process and we are using the Review Center Workflow to mark all requirements as "released" when the review is finalized.
A set of req need to be approved in the Review Center:
- Item 1 Version 1- Item 2 Version 1- Item 3 Version 1
All req are now approved in the review. They are all approved in Version 1. When the review is finalized all items are marked as "released" and the Version changes to 2. But the items in Version 2 are not approved.
When I create a Review Center Stats Report after the Review is finalized is shows that the "Reviewed Version" is different from the "Current Version". This happens just a few second after the Review was completed by the approvers.
Is there a way to either exclude the Status Change from the Version history or to print out a Report where "Reviewed Version" and "Current Version" are the same?
Is it possible to automatic generate a new Baseline after the Review was finalized?
We have the very same problem: As soon as a review has taken place successfully, the respective requirements are released by updating their status fields accordingly. This, however, is considered a change in the items and therefore generates new item versions, so the review becomes outdated immediately.
In my opinion, the correct solution to this problem would be to generally treat the status field differently than the other fields as it is more of a "meta-field": it does not belong to the content of the requirement as the other fields do but rather indicates the current state of the requirement in the respective development process.
To solve the underlying problem, however, it would be sufficient to allow admins to designate the status field as not changing versions, as proposed.
Are you currently working on this issue?
HEADQUARTERS|135 SW Taylor Suite 200, Portland, Oregon, 97204