Requirements Document Insert Project Name

Requirements Document – [Insert Project Name]

Requirements Document
[Insert Project Name] /
[Type the author name]
Last Updated: October 16, 2012

Introduction

Provide a paragraph or two describing the project and a bit of background information, if relevant. Refer to where the reader can find the Charter, Project Management Plan, etc for further information.

[Insert Introduction]

Scope

Provide a description of the project’s scope. Refer to the scope statement in the Project Charter or the more detailed one within the Project Management Plan (if applicable). This will define boundaries and set expectations for the requirements listed in this document.

[Insert Scope]

Product Perspective and Functions

This section provides the product perspective on the requirements. What need will this product serve? Who are the primary stakeholders, who is developing the project and who will benefit from the finished product? This should provide a high level list of what activities/business processes will be in the product.

[Insert Product Perspective and Functions]

User Characteristics

Who will use the finished product? What are their technical background and training, and their motivation to use? What obstacles might they encounter and what specialized skills will they need? This information is all relevant towards the requirements of the product.

[Insert User Characteristics]

Constraints, Assumptions and Dependencies

Describe any constraints, assumptions and dependencies (other than what is in the charter and/or Project Management Plan which you can refer to) that should be noted while gathering and documenting requirements.

[Insert Constraints, Assumptions and Dependencies]

Requirements

This section of the document divides the requirements into the following sections:

1. Business Requirements: high level, measurable statements of goals, objectives or needs of the University
2. Functional Requirements: describe the behaviour (processes) and information (data) that the solution will manage. These requirements will be categorized by stakeholder (where applicable), by business process (where applicable) and will include requirements for reporting, data entry, inquiry, and interfaces.
3. Non-Functional Requirements: describe the environmental conditions under which the solution must remain effective or qualities that the system must have (security, performance, capacity, availability, user interface, etc)
4. Transition Requirements: describe capabilities necessary to facilitate transition from the current state to the desired future state (data conversion, skill gaps, etc)

Business Requirements

These requirements are high level and measurable and relate to the department or University strategies.

[Insert Business Requirements]

Functional Requirements

This section could be very large so breaking it down into various applicable categories is recommended (stakeholders, business processes, etc). It may also refer to other supporting documents or appendices with further supporting documentation.

[Insert Functional Requirements]

Non-Functional Requirements

[Insert Non-Functional Requirements]

Transition Requirements

[Insert Transition Requirements]

Revision History

Provide a chart where document revisions are recorded. This chart should include who made the revision, the date made, what was revised, who it was reviewed & approved by, and the date it was reviewed & approved.

[Insert Revision History chart]

Page | 1[Insert full path and file name]