8/12/2019 Requirement Quality Checklist

http://slidepdf.com/reader/full/requirement-quality-checklist 1/1

Requirements Excellence Framework

Requirement Quality Checkl

© Copyright 2012 Enfocus Solutions Inc. All Rights Reserved

R Q C

Use the following checklist to help ensure that requirements clearly describe what is to be implemented

and meet relevant quality standards before solution development begins.

Accurate

Does it correctly represent the business need? It must be apparent that the

requirement furthers the objective it supports, and must be necessary to meet

that objective.

□

AtomicIs it independent of any other requirement? A requirement should consist of

one complete idea that can stand alone. It must be indivisible and irreducible.  □

Complete

Does it contain or reference sufficient detail, examples, pictures, and other

explanatory material? Does it cover all attributes? Each requirement must fully

describe the functionality to be delivered.

□

Modifiable

When changes are necessary, will they be made easily, completely, and

consistently? A requirement specification is modifiable if its structure and style

are such that any necessary changes to the requirement can easily be made.

□

Practical

Is it feasible to perform with existing constraints, such as time, money, and

available resources? The requirement must prove to be realistically achievable

and cost-effective.

□

Prioritized

How important is this requirement to the future of the business? How essential

is a requirement to a particular service release? Although each requirement

should document something stakeholders really need or something that is

required to conform to an existing requirement, external interface, or standard,

in reality, some system capabilities are more essential than others.

□

TraceableDo you know the source of the requirement as well as the impact it has on other

requirements? If the origin cannot be identified, it is most likely unnecessary.  □

Unambiguous

Did you make sure to avoid uncertain terms, jargon, and wordiness so

that the requirement is clear and easily understood? If there are multiple

readers of a requirement (which there usually are), they should all arrive at

the same understanding.

□

ValuableDoes the source of the requirement have the authority to specifyrequirements? Every requirement has to describe something that the

customers truly need or express something required for compliance to an

external requirement, interface, or standard.

□

Verifiable

Is there a clear verification method? Can it be tested using quantifiable

measures and indicators of strength? Testers should be able to verify whether

the requirement is implemented correctly.

□