Volere Requirements Specification Template

The intention of this question is to determine if the product is really wanted.
Considerations
Is it realistic to build a product within this budget? If the answer to this
question is no, then either the client is not really committed to building the
product or does not place enough value on the product. In either case you
should consider whether it is worthwhile continuing.
5 Naming Conventions and Definitions
This section gives definitions of all terms, including acronyms, used in the
project.
Content
A dictionary containing the meaning of all the names used within the
requirements specification. Select names carefully to avoid giving a different,
unintended meaning.
This dictionary should build on the standard names that your organization, or
industry, uses. The names should also reflect the terminology in current use
within the work area.
The dictionary contains all important names that are used by the project. For
each name write a succinct definition. This definition must be agreed by the
appropriate stakeholders.
Motivation
Names are very important. They invoke meanings that, if carefully defined,
can save hours of explanations. Attention to names at this stage of the
project helps to highlight misunderstandings.
The dictionary produced during requirements is used and added to
throughout the project.
Examples
Gritter Truck -- a truck used for spreading de-icing substances on roads in
winter.
Considerations
Make use of existing references and data dictionaries. Obviously it is best to
avoid renaming existing items unless they are so ambiguous that they cause
confusion.
From the start of the project emphasise the need to avoid homonyms and
synonyms and explain how they increase the cost of the project.
Volere Template V6.1 Copyright © Atlantic Systems Guild 19
This template may be copied for internal use provided copyright is acknowledged