Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirements Validation Techniques (Perspective-based reading (May be…
Requirements Validation Techniques
Commenting
The goal is to receive the co-worker’s
expert opinion with regard to the quality of a requirement
The co-worker reviews the requirement with the goal to identify issues that impair requirement quality
Inspections
Phases
Planning
the goal of the inspection
the work results that
are to be inspected,
roles and participants
Overview
the author explains the requirements to be
inspected to all team members
Error detection
the inspectors search through the
requirement for errors
individually
each inspector can concentrate on the requirements
collaboratively
communication between the inspectors creates synergy effects during error detection
Error collection and
consolidation
all identified errors are collected, consolidated,
and documented
Roles
Organizer
plans and supervises the inspection process
Moderator:
leads the session and ensures that the predetermined
inspection process is followed. (Neutral Stakeholder)
Author:
explains the requirements that he created to the
inspectors in the overview phase
is responsible for correcting
the errors identified.
Reader:
introduces the requirements to be inspected successively
and guides the inspectors through them.
Often, the moderator is also the reader
Inspectors:
are responsible for finding errors and communicating
their findings
Minute-taker:
Walk-throughs
is a lightweight version of an inspection
Goal
identify quality flaws within requirements by means of a shared process and to gain a shared understanding of the requirements
Roles
reviewer (comparable to the inspector)
author
introduces the requirement to all other participants
minute-taker
potentially the moderator
discuss the requirements to be validated step-by-step, with participants
Perspective-based reading
requirements are checked by adopting different perspectives
May be
User/customer perspective
Software architect perspective
Tester perspective:
to establish whether they contain the information necessary to derive test cases from the requirements.
Content perspective:
Documentation perspective:
Agreement perspective:
the results of the perspective-based reading contain answers to the predefined questions, and on the other hand, open issues that the auditors noticed while reading may be present
prototypes
throw-away prototypes
are not maintained once they have
been used.
evolutionary prototypes
are developed with the goal to be developed further and improved in later steps
checklists
a set of questions and/or statements about a certain
circumstance.
must be strictly adhered to. These questions must be answered by the auditor to validate the requirements