Requirement Validation-

Reviews
 VALIDATION

VALIDATION is the process of ensuring that the

specified requirement meets the user need and
that it fulfills its intended purpose.

VALIDITY CONSISTENC REALISM VERIFIABILI

Y TY
 REVIEWS
Requirements review is a review by a group
of people to find errors and point out other
matters of concern in the requirement
specification of system.
TYPES OF REVIEWS
Reviews can be classified as follows (based on their formality levels):
 walk-through,
 peer-review
 formal review/ inspection.
REQUIREMENT VALIDATION

Validation is the process of confirming

the completeness and correctness of
requirements.
Why Validation

Requirement validation eliminates following

things from requirement document
Requirements conflicts.


Technical errors.


Ambiguous requirements

Validation ensures
Requirement validation ensures that requirements are

 Clear.

 Feasible.

 Traceable.

 Verifiable.

 Prioritizable.
Validation As Process
 How TO Validate
There are some techniques to validate requirements:

 Reviews.

 Prototype.

 User manual.

 Model Validation.

 Requirement Testing.
Requirement Reviews
What are Requirement Reviews?
Requirement Reviews are the most
common methods of validation.
Requirements review is a review by a
group of people to find errors and point
out other matters of concern in the
requirement specification of system.
 Who are the Reviewers?
1. Requirement Analyst
2. Clients
3. End Users
4.Domain Expert
5.Person from a Design Team
6.Person responsible for maintaining Requirement
Document.
7.Tester
 Plan Review
 Distribute Document
Review Activities

 Prepare for Review

meetings
 Requirement Review
Meeting
. Comments and
problems are discussed
. Set Action to
address the problem

 Follow up Action
 Revise Document
Reviews Checklist

1.Are all hardware resource defined?

2.Have all the functions required by the client been
specified.
3.Is each requirement testable?
4.Is each requirement is Traceable?
5.Is the initial state of the system defined?
6.Are possible future modifications specified?
READING TECHNIQUES TO INCREASE
EFFECTIVNESS OF A REVIEW
Especially during the peer-reviews and inspection, it is
additionally possible to improve effectiveness of a review by
using different reading techniques. Here is quite a complete list
of these supportive techniques:
 Checklist-based
 Perspective-based reading
 Ad-hoc
 Pattern-based
 Scenario-based:
 Defect-based reading
CHECKLIST-BASED READING
TECHNIQUE
 In checklist-based reading, the reviewer is given a
checklist with questions that are to be answered during the
review. The questions shall draw the attention of the reviewer
to some aspects of the inspected document that are often
found defective. Checklists give support to the reviewer, so
that the result of the review is not dependent on the skills of
the individual.
PERSPECTIVE-BASED READING
TECHNIQUE
 When using the perspective-based reading technique reviewers use
different roles or points of view when reviewing. For example, reviewing as
a tester, reviewing as a designer, reviewing as a developer etc. Each role
has scenarios that include questions and activities that tell the reader how
to review.
AD-HOC READING TECHNIQUE

 The ad-hoc reading technique does not give any guidance for
reviewers. The reviewers simply attempts to find as many
defects as possible by examining the document using the
skills and knowledge they have. The ad-hoc technique is very
dependent on the individuals performing the inspection.
SCENARIO-BASED READING TECHNIQUE
 A scenario-based reading technique offers a set of formal
procedures how to review a document. A quite popular version
of scenario-based reading is defect-based reading technique.
DEFECT-BASED READING
 To use the defect-based reading technique we need to create
a model of possible defects in requirements documents. For
each defect class from the model (e.g. the class of data type
inconsistencies, incorrect functions, and/or missing or
ambiguous functions), we develop a set of questions that
would characterize the defect class. While reading the
document, the reviewer tries to answer the questions and find
defects in the document. Each reviewer applies only a single
scenario/looks for one fault class only. All reviewers together
achieve then sufficient coverage of the document.
Pattern Based Technique
Pattern-based reading - a set of patterns is provided to
reviewers that they can use when validating requirements
against scenarios. – A set of requirements patterns is to be
defined.
Each requirements pattern can be represented by a formal
validation frame that describes what a part of a scenario should
look like to make the pattern applicable, and what should then
be searched for in the requirements document.
Why Reviews are Important?

 Less Client Involvement

 Safe Delivery Time
 Large Team size
 Clarity