Requirements Document
A requirements document is a detcailed document specifying the features and other requirements of a proposed piece of software. Your requirements document will include the following sections:
- Project Overview
- Users
- Features
- Rules/Constraints
- Non-Functional Requirements
- Success Criteria
We'll look at each of these sections alongside an example.
Project Overview
A sentence or two describing what your app is.
Example: "A homework tracker app for students."
Users
What are the types of users that will make use of your app? How so?
Example:
- Teachers - Assign homework and mark it
- Students - Submit homework
Features
What must the app do? This can be formatted as a list. You may want to categorize the list if you have lots of features.
Example: (this is just a start - you should have many more)
- add homework
- mark homework complete
- sort by due date
Rules/Constraints
Important limitations.
Example:
- must work on phones
- users need passwords
- due dates cannot be in the past
Non-Functional Requirements
Requirements that deal with the quality of the software as opposed to how it functions.
Example:
- loads quickly
- secure passwords
- easy to use
Success Criteria
How do we know it works?
Example: "A student can add and complete homework tasks successfully."