You are here: Validating requirements > Reviewing > About Reviews

About Reviews

Overview

A review artifact allows you to request artifact feedback and/or approval from stakeholders. Review artifacts can be set to one of two types: informal review (live artifacts), or formal review (baseline artifacts). You can only request approval or electronic signatures on artifacts if they are included in a formal review. If you create an informal review, review participants can add comments to artifacts, but the artifacts cannot be approved.

Note: A baseline must be sealed and published before you can include it in the review contents. This ensures that the artifacts do not change while the review is underway.

When the review is active, you can view the review status information to determine which individuals have started reviewing the artifacts and whether or not any of the artifacts have been approved.

Finding your review artifacts

Review artifacts are special artifacts that are treated somewhat differently than other artifacts in Blueprint. Review artifacts are stored in a separate location in Blueprint. You can find your project's baseline and review artifacts by clicking the Baselines and Reviews folder located below your project in the explorer panel of Blueprint:

After you click the Baselines and Reviews folder for your project, your baseline and review artifacts are displayed in the main content area.

Key Concepts

Reviewer and Approver Roles in Formal and Informal Reviews

A review artifact can be set to either a formal review or an informal review. Formal reviews contain sealed baseline artifacts, while informal reviews contain live artifacts.

Review Status

The review can have one of the following statuses:

Modifying an Active Review

When any review is active, you can still modify the list of review participants. Your ability to change other review parameters differs depending on whether you are modifying an Informal Review (live artifacts) or a Formal Review (baseline artifacts). The differences are:

Typical Usage of Reviews

Review artifacts can be beneficial at any phase in the project when you want to elicit feedback from others. Here's an example:

Example

Lewis, a business analyst, is working on a set of requirements. He is close to completion and would like to obtain feedback from a few individuals.

In this scenario, Lewis would create an Informal Review, which is a review containing live artifacts. Lewis can continue to change the artifacts, and reviewers will always see the most recent published artifact when they open the artifacts from the review.

Review artifacts are also useful when requirements are complete and final approval is required. Here's an example:

Example

Susan, a business analyst, is finished incorporating feedback from prior reviews that she has conducted. She is now confident that her artifacts are ready for approval.

In this scenario, Susan creates a baseline artifact. Next, she creates a review artifact and sets the type to Formal Review. Susan can then select the stakeholders that she wants to approve the requirements.

Review Artifact Properties

By default, a review artifact contains the following system properties:

Your instance administrator can configure standard properties for each standard artifact type.

Tasks

Adding a review

Configuring a review

Viewing review status information

Closing a review

Creating a follow up review

Deleting a review

Learn More

Baselines and reviews

About the Reviewers Experience

About the utility panel reviews tab