Volere Requirements Specification Template
Volere Requirements Specification Template
Volere Requirements Specification Template
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Motivation<br />
<strong>Requirements</strong> for interfacing to other applications often remain undiscovered<br />
until implementation time. Avoid a high degree of rework by discovering<br />
these requirements early.<br />
Examples<br />
“We must be able to interface with any html browser.”<br />
“The new version of the spreadsheet must be able to access data from the<br />
previous 2 versions”<br />
“Our product must interface with the applications that run on the remote<br />
weather stations”<br />
Fit Criterion<br />
For each inter-application interface specify:<br />
- The data content<br />
- The physical material content<br />
- The medium that carries the interface<br />
- The frequency<br />
- The volume<br />
14 Maintainability and Portability <strong>Requirements</strong><br />
14a. How easy must it be to maintain this product?<br />
Content<br />
A quantification of the time necessary to make specified changes to the<br />
product.<br />
Motivation<br />
To make everyone aware of the maintenance needs of the product.<br />
Examples<br />
“New MIS reports must be available within one working week of the date the<br />
requirements are agreed”<br />
“A new weather station must be able to be added to the system overnight”<br />
Considerations<br />
There may be special requirements for maintainability, such as this product<br />
must be able to be maintained by its end-users, or developers who are not<br />
the original developers. This has an effect on the way that the product is<br />
<strong>Volere</strong> <strong>Template</strong> V6.1 Copyright © Atlantic Systems Guild 37<br />
This template may be copied for internal use provided copyright is acknowledged
Change language