Volere Requirements Specification Template

Requirement Shell
Use this requirement shell as a guide for writing each requirement.
The type from
the template
List of events /
use cases that
need this
requirement
Requirement #: Unique id Requirement Type: Event/use case #:
Description:
A one sentence statement of the intention of the requirement
Rationale:
A justification of the requirement
Source: Who raised this requirement?
Fit Criterion: A measurement of the requirement such that it is possible to
test if the solution matches the original requirement
Other requirements
that cannot be
Customer Satisfaction:
Customer Dissatisfaction:
implemented if this
Dependencies: A list of other requirements that have Conflicts: one is
some dependency on this one
Supporting Materials: Pointer to documents that
History: Creation, changes, illustrate and explain this Volere
deletions, etc. requirement
Copyright © Atlantic Systems Guild
Degree of stakeholder happiness if this requirement
is successfully implemented.
Scale from 1 = uninterested to 5 = extremely pleased.
Measure of stakeholder unhappiness if this
requirement is not part of the final product.
Scale from 1 = hardly matters to 5 = extremely displeased.
Requirement Numbering
Give each requirement a unique identifier to make it traceable throughout
the development process. The numbering scheme suggested in the
requirement shell is:
Requirement # is the next unique requirement number
Requirement Type is the section number from the template for this
type of requirement
The inclusion of the section number is not absolutely necessary
because we do have a unique requirement id. However it serves as a
Volere Template V6.1 Copyright © Atlantic Systems Guild 5
This template may be copied for internal use provided copyright is acknowledged