Reviewing requirements

Essentials of IBM® Rational® DOORS Next Generation V4.01
Reviewing requirements 1© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
© Copyright IBM Corporation 2013
Reviewing requirements
Contents
Module overview -2
Preparing a review -3
Reviews -4
Why use reviews? -5
Reviews and approvals -6
Types of reviews -7
Reviewer roles -8
Review lifecycle states -9
Creating a review from a collection -10
Creating a review of individual artifacts -12
Completing a review -13
Open reviews -14
Completing a review -15
Monitoring a review -19
Finalizing a review -20
Review of a module -21
Lab : Conducting a review -22
Review -23
Module summary -24

2 © Copyright IBM Corporation 2013
Module overview
After you complete this module, you should be able to
do these tasks :
 Prepare a requirements review.
 Complete a requirements review.

Topics
> = Current topic
> Preparing a review
 Completing a review

Reviews
When you are ready for team members to review
requirement artifacts, you can create a review.
In reviews, team members review requirement artifacts,
record comments about them, and approve or
disapprove them within the context of the project.
A review can contain individual artifacts or can be
based on a collection.
You can add team members to reviews, assign them
specific roles, and set up automatic email notifications.

Why use reviews?
0
20
40
60
80
100
120
R
equirem
entsD
esign
C
ode
Test
O
perations
 Rework can consume
30-50% of development
costs. Requirement
errors account for 70-
85% of rework costs.
 Preventing requirement
errors and catching
them early can greatly
reduce rework.
Wiegers, 2003.
Relative Cost to Correct a Defect
 See also: Lindner, Richard J. & Tudahl, D. "Software
Development at a Baldrige Winner,“ Proceedings of ELECTRO
`94, Boston, Massachusetts, May 12, 1994, pp. 167-180.

Reviews and approvals
Generally, a review and approval process includes
these steps:
 Presenting and making the information available
 Defining the review criteria
 Reviewing or inspecting the requirement artifacts
 Collecting comments and feedback for improvement
 Gaining acceptance of the requirements
 Getting formal sign-off for the requirements, if required
Generate review documents only in these
circumstances:
• When there is value to both the
stakeholders and development team
• When your organizational process
requires them; for example, for archival
purposes or for using your organization’s
content-management system and
approval process
• When other parties who do not have
access to the project area need
information
• For contractual purposes
With the Requirements Management (RM)
application, teams can reduce their
dependence on large specification
documents.

Types of reviews
Type Description When to use
Formal Reviewers see versions
of artifacts that were
current when the review
was created
 Artifacts are in flux and
you want controlled
reviews on static versions
 You need specific versions
of artifacts to be approved
Informal Reviewers see the latest
version of the artifacts
when they start the
review
 Artifacts are not changing
 You do not need specific
versions to be approved
Use informal reviews to provide feedback
when team members are jointly authoring
requirements.
In a formal review, the version of embedded
artifacts is "frozen" in the artifacts that are in
the review.

Reviewer roles
The review creator adds team members to the review and
assigns a role to each reviewer.
Role Required action
Approver Must approve, disapprove, or abstain from
reviewing each artifact in the review for the
review to move forward.
Reviewer Must review or abstain from reviewing each
artifact in the review for the review to move
forward.
Optional reviewer Optionally review or abstain from reviewing
the artifacts. The review moves forward
even if optional reviewers do not respond.

Review lifecycle states
State Description
Draft The initial state of the review as it is being
created.
In progress The state of the review after the creator
starts the review. Participants are notified.
Paused The review creator can pause the review
to add participants or roles, or to change
artifacts.
Reviewed Reviewers have marked the review as
complete.
Finalized All required reviewers have marked the
review complete, and the review creator
has clicked Finalize Review.
The review can move through these states.

Creating a review from a collection
From the edit menu of a collection ,
select Create Review from
Collection.
Name the review, select the
review type, and click OK.

Creating a review from a collection (continued)
Indicate a due date and include
instructions to reviewers.
Add participants and assign roles.
Optional: Send email notifications
to participants.
Add or remove artifacts.
When you are finished creating the
review , save it. Click Start Review to
begin the review.
Optional: To send a review request, select
one or more participants, and click Send
Email. The email addresses of the selected
users are added to the recipients list of the
new email message. Add text as required in
your email program, and then send the
message.
When you are finished setting up the review ,
save it. The review is in draft state until you
click Start Review.

Creating a review of individual artifacts
Create a review of individual artifacts
from the Artifacts page, from the
Artifact editor, or from the right
sidebar.
You can create reviews on individual
artifacts or include several individual artifacts
in a review. You can create a review in these
ways:
•On the Artifacts page, select the artifact or
artifacts to include in the review, and then
select Create Review Containing Artifact
from the edit menu.
•From an artifact that is open in the Artifact
editor, click the Create Review icon.
•From the Reviews sidebar in an open
artifact.

Topics
> = Current topic
 Preparing a review
>Completing a review

Open reviews
You can see active reviews in the Reviews
widget on the project dashboard or in the
Reviews section of the right sidebar.
Click the review to open it.
If you have the Reviews widget on your
dashboard, you can see your active reviews
in that widget.
You can also see your active reviews listed in
the Reviews section of the right sidebar.
Click the Show my active reviews icon.
To open a review and begin the review
process, click the title of the review from
either the dashboard or the sidebar.

Completing a review
Participants in the reviewer role have the option to
click Reviewed or Abstain for each artifact .

Completing a review (continued)
Participants in the approver role have the option to
Approve, Disapprove, or Abstain each artifact.
You can click Approve, Disapprove, or Abstain
for an artifact from this screen or click the artifact
to open it and review its contents.
Review each artifact in the review. From this
page, you can click Approve, Disapprove,
or Abstain for each artifact
To open an artifact, click its name.
If you select the check box at the beginning
of the table to select all artifacts, only the
artifacts that are listed on the page are
selected. If additional artifacts are on
subsequent pages, you must repeat this step
on each page.

When the artifact is open, you can
add comments.
Navigate back to the review.

When you are finished with
the review, click Done.
After you click Done, you
cannot make further
changes.
You must mark the review as done when you
are finished. After you mark the review as
done, you cannot make additional changes.
The status bar at the bottom of the page
indicates the overall status of the review.

Monitoring a review
Team members can monitor the progress of
the review.
The review creator and other team members
can monitor the progress of a review.

Finalizing a review
After all of the participants have
clicked Done, click Finalize
Review.
The review creator finalizes the review after
all of the participants are done.
When the review is
finalized, it cannot be
modified.
If a reviewer does not finish a review, the
review creator might need to select all of the
artifacts that are not marked as done and
change their status to done before finalizing
the review.

Reviewing a module
Placing a module under review places only one artifact in review: the module.
•A formal review baselines all of the artifacts within it.
•An informal review allows the artifacts to be edited .

Lab: Conducting a review
After you finish this lab, you
should be able to do these
tasks:
 Create a formal review from a
collection
 Log in as review approver, and
complete a review
 Log in as review creator, and
finalize a review

Review
 What are the two types of
reviews that you can create?
When would you use one type
versus the other?
 What participant roles are
available for reviews and what
are their required actions?

Module summary
In this module, you learned how to do these tasks :
 Prepare a requirements review
 Complete a requirements review

Reviewing requirements

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (20)

Ähnlich wie Reviewing requirements

Ähnlich wie Reviewing requirements (20)

Mehr von IBM Rational software

Mehr von IBM Rational software (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Reviewing requirements