{"id":201,"date":"2007-01-18T11:27:00","date_gmt":"2007-01-18T11:27:00","guid":{"rendered":"https:\/\/ahm.basfinans.com\/index.php\/2007\/01\/18\/requirements-document-template-for-small-projects\/"},"modified":"2007-01-18T11:27:00","modified_gmt":"2007-01-18T11:27:00","slug":"requirements-document-template-for-small-projects","status":"publish","type":"post","link":"https:\/\/ahm.basfinans.com\/index.php\/2007\/01\/18\/requirements-document-template-for-small-projects\/","title":{"rendered":"Requirements Document Template for Small Projects"},"content":{"rendered":"

\"\"<\/a>Requirements document is an important document in system – hardware\/software – development. There exist <\/span>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.<\/span>
<\/span><\/p>\n

\n

<\/p>\n

<\/p>\n

In all cases you have to read basic info about Volere from http:\/\/www.systemsguild.com\/GuildSite\/Robs\/Template.html<\/a><\/p>\n

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.<\/p>\n

The document will be filled with Product Managers, Hardware Team and Software Team collaboratively. Look at CMMI 1.2 Requirements Management key process area.
<\/span>
<\/span><\/p>\n


<\/span><\/p>\n

Project Requirements Specifications<\/b><\/span><\/p>\n


Revision History:<\/b><\/span><\/p>\n\n\n\n\n\n\n\n\n
\n

Revision<\/b><\/span><\/p>\n<\/td>\n

\n

When<\/b><\/span><\/p>\n<\/td>\n

\n

Who<\/b><\/span><\/p>\n<\/td>\n

\n

What, Where, Why<\/b><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

1<\/span><\/p>\n<\/td>\n

\n

ahm507
<\/span><\/p>\n<\/td>\n

\n

18-1-2007
<\/span><\/p>\n<\/td>\n

\n

Created; This template is based on Volere, look at <\/span><\/span>http:\/\/systemsguild.com\/GuildSite\/Robs\/Template.html<\/span><\/span><\/a><\/u><\/span><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n


<\/span><\/p>\n


<\/span><\/p>\n

PROJECT DRIVERS<\/span><\/p>\n


<\/span><\/p>\n

1. The Purpose of the Product
<\/span>
<\/span><\/p>\n

2. Client, Customer, Stakeholders<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n
\n

ID<\/span><\/p>\n<\/td>\n

\n

Name\/Title<\/span><\/p>\n<\/td>\n

\n

Company<\/span><\/p>\n<\/td>\n

\n

Phone<\/span><\/p>\n<\/td>\n

\n

email<\/span><\/p>\n<\/td>\n

\n

Notes<\/span><\/p>\n<\/td>\n<\/tr>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n


4. Users of the Product<\/span><\/p>\n


<\/span><\/p>\n


<\/span><\/p>\n

PROJECT CONSTRAINTS<\/span><\/p>\n


<\/span><\/p>\n

4. Mandated Constraints<\/p>\n

5. Naming Conventions and Definitions<\/span>
<\/span><\/p>\n

6. Relevant Facts and Assumptions<\/span><\/p>\n


<\/span><\/p>\n

FUNCTIONAL REQUIREMENTS<\/span><\/p>\n


7. The Scope of the Work<\/span>
<\/span><\/p>\n

8. The Scope of the Product<\/p>\n

9. Functional and Data Requirements<\/span><\/p>\n


9.1 Group 1:<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n
\n

ID<\/span><\/p>\n<\/td>\n

\n

Description<\/span><\/p>\n<\/td>\n

\n

Originator<\/span><\/p>\n<\/td>\n

\n

Priority<\/span><\/p>\n<\/td>\n

\n

Notes<\/span><\/p>\n<\/td>\n<\/tr>\n

\n

9.1.1<\/span><\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n<\/tr>\n

\n

9.1.2<\/span><\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n


9.2 Groups 2:<\/span><\/p>\n


<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n
\n

ID<\/span><\/p>\n<\/td>\n

\n

Description<\/span><\/p>\n<\/td>\n

\n

Originator<\/span><\/p>\n<\/td>\n

\n

Priority<\/span><\/p>\n<\/td>\n

\n

Notes<\/span><\/p>\n<\/td>\n<\/tr>\n

\n

9.2.1<\/span><\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n<\/tr>\n

\n

9.2.2<\/span><\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n


9.3 Groups 3:
<\/span>
<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n
\n

ID<\/span><\/p>\n<\/td>\n

\n

Description<\/span><\/p>\n<\/td>\n

\n

Originator<\/span><\/p>\n<\/td>\n

\n

Priority<\/span><\/p>\n<\/td>\n

\n

Notes<\/span><\/p>\n<\/td>\n<\/tr>\n

\n

9.3.1<\/span><\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n<\/tr>\n

\n

9.3.2<\/span><\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n

\n


<\/span> <\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n


<\/span><\/p>\n

NON-FUNCTIONAL REQUIREMENTS<\/span><\/p>\n


10. Look and Feel<\/span><\/span><\/span>
<\/span><\/p>\n

11. Usability and Humanity<\/span>
<\/span><\/p>\n

12. Performance<\/span>
<\/span><\/p>\n

13. Operational<\/span>
<\/span><\/p>\n

14. Maintainability and Support<\/span>
<\/span><\/p>\n

15. Security<\/span>
<\/span><\/p>\n

16. Cultural and Political<\/span>
<\/span><\/p>\n

17. Legal<\/span><\/p>\n

<\/span> <\/p>\n

PROJECT ISSUES
<\/span><\/span><\/b>
<\/span><\/p>\n

18. Open Issues<\/span>
<\/span><\/p>\n

19. Off-the-shelf Solutions<\/span>
<\/span><\/p>\n

20. New Problems:<\/p>\n

21. Tasks<\/span>
<\/span><\/p>\n

22. Migration to the New Product<\/span>
<\/span><\/p>\n

23. Risks<\/span>
<\/span><\/p>\n

24. Costs<\/span>
<\/span><\/p>\n

25. User Documentation<\/span>
<\/span><\/p>\n

26. Waiting Room<\/span>
<\/span><\/p>\n

27. Ideas for Solutions<\/span><\/p>\n


<\/span><\/p>\n


<\/span><\/div>\n

From ahm507.blogspot.com<\/div>\n","protected":false},"excerpt":{"rendered":"

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 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"_links":{"self":[{"href":"https:\/\/ahm.basfinans.com\/index.php\/wp-json\/wp\/v2\/posts\/201"}],"collection":[{"href":"https:\/\/ahm.basfinans.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ahm.basfinans.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ahm.basfinans.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ahm.basfinans.com\/index.php\/wp-json\/wp\/v2\/comments?post=201"}],"version-history":[{"count":0,"href":"https:\/\/ahm.basfinans.com\/index.php\/wp-json\/wp\/v2\/posts\/201\/revisions"}],"wp:attachment":[{"href":"https:\/\/ahm.basfinans.com\/index.php\/wp-json\/wp\/v2\/media?parent=201"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ahm.basfinans.com\/index.php\/wp-json\/wp\/v2\/categories?post=201"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ahm.basfinans.com\/index.php\/wp-json\/wp\/v2\/tags?post=201"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}