Requirements document is an important document in system – hardware/software – development. There exist a well known methodology called Volere, they have a very good template, but it too big for our small project, I developed a small template that is just sufficient to us.
In all cases you have to read basic info about Volere from http://www.systemsguild.com/GuildSite/Robs/Template.html
The template is just a structured way to remind us to the basic sections of requirements, of course in any project some of the titles will be not applicable.
The document will be filled with Product Managers, Hardware Team and Software Team collaboratively. Look at CMMI 1.2 Requirements Management key process area.
Project Requirements Specifications
Revision History:
|
Revision |
When |
Who |
What, Where, Why |
|
1 |
ahm507 |
18-1-2007 |
Created; This template is based on Volere, look at http://systemsguild.com/GuildSite/Robs/Template.html |
PROJECT DRIVERS
1. The Purpose of the Product
2. Client, Customer, Stakeholders
|
ID |
Name/Title |
Company |
Phone |
|
Notes |
|
|
|
|
|
|
|
4. Users of the Product
PROJECT CONSTRAINTS
4. Mandated Constraints
5. Naming Conventions and Definitions
6. Relevant Facts and Assumptions
FUNCTIONAL REQUIREMENTS
7. The Scope of the Work
8. The Scope of the Product
9. Functional and Data Requirements
9.1 Group 1:
|
ID |
Description |
Originator |
Priority |
Notes |
|
9.1.1 |
|
|
|
|
|
9.1.2 |
|
|
|
|
9.2 Groups 2:
|
ID |
Description |
Originator |
Priority |
Notes |
|
9.2.1 |
|
|
|
|
|
9.2.2 |
|
|
|
|
9.3 Groups 3:
|
ID |
Description |
Originator |
Priority |
Notes |
|
9.3.1 |
|
|
|
|
|
9.3.2 |
|
|
|
|
NON-FUNCTIONAL REQUIREMENTS
10. Look and Feel
11. Usability and Humanity
12. Performance
13. Operational
14. Maintainability and Support
15. Security
16. Cultural and Political
17. Legal
PROJECT ISSUES
18. Open Issues
19. Off-the-shelf Solutions
20. New Problems:
21. Tasks
22. Migration to the New Product
23. Risks
24. Costs
25. User Documentation
26. Waiting Room
27. Ideas for Solutions