Project Name Requirements Document
This document defines the requirements of the project. It will be used as the basis for the following
activities:



Creating a Design/Implementation
Developing test plans
Determining project completion and assessment of project success
Document Resources
This item is optional. Identifying all resources and stakeholders involved in gathering requirements. e.g. interviews
with other institutions; documents reviewed for a similar project; focus groups, etc.
...
Glossary of Terms
This item is optional. If your project has any unique terms or acronyms, it is useful to clearly identify and define
them.
 i.e. ISP Internet Service Provider - one who supplies internet services to a party
 ...
Project Overview
A brief and high-level description of what this project is about. If your project is small it may be sufficient to simply
describe your requirements in this section.
...
Assumptions and Constraints
List any assumptions or constraints on which the requirements are based. Budget, scheduling and scope constraints
should be included here. e.g. window of opportunity for service or product; grant funding availability.
...
Use Cases
This item is optional. Use Cases are helpful in describing the required system behavior from an end user perspective.
Usually a Use Case describes the flow of events between people using the system and the system itself. A system
could have many use cases depending on the feature set. e.g. faculty posting assignments; students viewing
assignment and submitting their solution.
...
Specific Requirements (Scope)
Not all projects will use all the various requirements sub-groups. The sub-groups are:
 User requirements
 Reporting requirements
 Access/Security requirements
 Interface requirements (user and/or system, usability,etc.)
 Support/Maintenance requirements
 Scalability requirements
 Integration requirements
 Quality and Performance requirements
...
Revised May 1, 2012