Volere Requirements Specification Template

Considerations
Ask questions from your marketing department to discover unstated
assumptions that have been made about the portability of the product.
15 Security Requirements
15a. Is the system confidential?
Content
Specification of who has authorized access to the system, and under what
circumstances that access is granted.
Motivation
To understand the expectations for confidentiality aspects of the system.
Examples
“Only direct managers can see the personnel records of their staff.”
“Only holders of current security clearance can enter the building.”
Fit Criterion
System function name or system data name
User role/s and/or names of people who have clearance
Considerations
Is there any data that is sensitive to the management? Is there any data that
low level users do not want management to have access to? Are there any
processes that might cause damage or might be used for personal gain? Are
there any people who should not have access to the system?
Avoid solving how you will design a solution to the security requirements.
For instance, don’t design a password system. Your aim here is to identify
what the security requirement is. The design will come from this description.
Consider asking for help. Computer security is a highly-specialised field, and
one where improperly-qualified people have no business being. If your
product has need of more than average security, we advise that you make
use of a security consultant. They are not cheap, but the results of
inadequate security can be even more expensive.
15b. File integrity requirements
Content
Specification of the required integrity of databases and other files.
Volere Template V6.1 Copyright © Atlantic Systems Guild 39
This template may be copied for internal use provided copyright is acknowledged