How to use reviews for releases/sign-off
How do you leverage the review capability in RRC to provide only the approved versions of artifacts to RQM instead of the most up-to-date versions.
Also, has anyone used the review functionality to provide sign-off on a project for a release of approved versions of artifacts?
Any help would be appreciated,
Brian R.
Accenture
Business Analyst
Also, has anyone used the review functionality to provide sign-off on a project for a release of approved versions of artifacts?
Any help would be appreciated,
Brian R.
Accenture
Business Analyst
2 answers
How do you leverage the review capability in RRC to provide only the approved versions of artifacts to RQM instead of the most up-to-date versions.
Also, has anyone used the review functionality to provide sign-off on a project for a release of approved versions of artifacts?
Any help would be appreciated,
Brian R.
Accenture
Business Analyst
In regards to sign-off of requirements, once the formal review is complete, a report can be run to publish the results and used for sign-off.
An alternative is create a collection from the finalised review and embed that collection in a rich text document and print that.
Now if you want to reference specific versions of an artifact if you open the history for that artifact, you can copy the artifact URL from the address bar - you will notice a revision extension at the end - and paste that in a rich text document.
Clicking this link will open that specific version, not the latest.
How do you leverage the review capability in RRC to provide only the approved versions of artifacts to RQM instead of the most up-to-date versions.
Also, has anyone used the review functionality to provide sign-off on a project for a release of approved versions of artifacts?
Any help would be appreciated,
Brian R.
Accenture
Business Analyst
In regards to sign-off of requirements, once the formal review is complete, a report can be run to publish the results and used for sign-off.
An alternative is create a collection from the finalised review and embed that collection in a rich text document and print that.
Now if you want to reference specific versions of an artifact if you open the history for that artifact, you can copy the artifact URL from the address bar - you will notice a revision extension at the end - and paste that in a rich text document.
Clicking this link will open that specific version, not the latest.
Additionally you could set up a sign-off attributes that you can associate with a specific user in the project. You could have the community sign off the requirements and then as rbater recommends you can create a collection or take a snapshot.
-------------------------------------
Jared Pulham
RRC Product Manager