Volere Requirements Specification Template

Motivation
To bring uncertainty out in the open and provide objective input to risk
analysis.
Examples
“Our investigation into whether or not the new version of the processor will
be suitable for our application is not yet complete.”
“The government are planning to change the rules about who is responsible
for gritting the motor ways, but we do not know what the changes might be.”
Considerations
Are there any issues that have come up from the requirements gathering that
have not yet been resolved? Have you heard of any changes that might occur
in the other organisations/systems on your context diagram? Are there any
legislative changes that might affect your system? Any rumours about your
hardware/software suppliers that might have an impact?
19 Off-the-Shelf Solutions
19a. Is there a ready-made system that could be bought?
Content
List of existing products that should be investigated as potential solutions.
Reference any surveys that have been done on these products.
Motivation
To give consideration to whether or not a solution can be bought.
Considerations
Is it possible to buy something that already exists or is about to become
available? It may not be possible at this stage to say with a lot of confidence,
but any likely products should be listed here.
Also consider whether there are products that must not be used.
19b. Can ready-made components be used for this product?
Content
Description of the candidate components, either bought-in or built by your
company, that could be used by this project. List libraries that could be a
source of components.
Motivation
Reuse rather than reinvention.
Volere Template V6.1 Copyright © Atlantic Systems Guild 43
This template may be copied for internal use provided copyright is acknowledged