Project Name: Requirements Document (version 1.0)
To use this template:
1. Replace any red italicized text with your own text. You may remove or add sections as
needed for your particular projects.
2. Enter the project name in the title and footer (and change the document version number,
if necessary).
3. If your document is very long, break each numbered chapter into its own document
section, beginning it on a new page. This will make it easier to replace/updagte
4. Delete these instructions and any other italicized instructions.
Project:
Date(s):
Prepared by:
Document status: __ Draft __ Proposed __ Validated __ Approved
1. Introduction
This document contains the system requirements for project name. These requirements have
been derived from several sources, including brief listing of most important sources.
1.1 Purpose of This Document
This document is intended to guide development of project name. It will go through several
stages during the course of the project:
1. Draft: The first version, or draft version, is compiled after requirements have been
discovered, recorded, classified, and prioritized.
2. Proposed: The draft document is then proposed as a potential requirements
specification for the project. The proposed document should be reviewed by several
parties, who may comment on any requirements and any priorities, either to agree, to
disagree, or to identify missing requirements. Readers include end-users, developers,
project managers, and any other stakeholders. The document may be amended and
reproposed several times before moving to the next stage.
3. Validated: Once the various stakeholders have agreed to the requirements in the
document, it is considered validated.
4. Approved: The validated document is accepted by representatives of each party of
stakeholders as an appropriate statement of requirements for the project. The developers
then use the requirements document as a guide to implementation and to check the
progress of the project as it develops.
1.2 How to Use This Document
We expect that this document will be used by people with different skill sets. This section explains
which parts of this document should be reviewed by various types of readers.
Types of Reader
In this section, list the different types of reader this document is aimed at. For example, Flash
programmers, graphic designers, end-users, project managers, etc. For each type of reader,
clearly state which sections are most pertinent to them, and which may be safely skipped.
Technical Background Required
Describe here the technical background needed to understand the document in general, and any
particular expertise or understanding that is needed for specific sections.
Overview Sections
List here the sections that should be read by someone who only wishes to gain an overall
understanding of the project, or which should be read first before technical requirements are
reviewed.
Project Name: Requirements Document (version 1.0) 1
