A requirements gathering template is a document used to track and record software requirements from stakeholders. It provides a structured way to capture, analyze, and communicate these requirements.
Here is a simple example of a requirements gathering template that you can adjust to fit your needs:
| Requirement ID | Requirement Description | Requirement Type | Source | Priority | Comments |
|---|---|---|---|---|---|
| REQ-001 | The system shall allow users to log in using an email and password | Functional | Stakeholder Meeting | High | |
| REQ-002 | The system shall provide an option to reset a forgotten password | Functional | User Interview | High | |
| REQ-003 | The system shall encrypt all user passwords | Non-Functional | Security Policy | High | |
| REQ-004 | The system shall load the user dashboard in less than 2 seconds | Non-Functional | Performance Standard | Medium |
Here is what each column represents:
- Requirement ID: A unique identifier for each requirement. This helps in tracking and referencing individual requirements.
- Requirement Description: A clear, concise description of the requirement.
- Requirement Type: The type of requirement. This could be functional (describing what the system should do) or non-functional (describing how the system should be or how it should perform).
- Source: Where or who the requirement came from. This could be a person (like a user or stakeholder), a document (like a policy or standard), or an event (like a meeting or workshop).
- Priority: How important the requirement is. This helps in planning and scheduling the work. Typical priority levels are High, Medium, and Low.
- Comments: Any additional notes or comments about the requirement. This could include information about dependencies, assumptions, constraints, or anything else that’s relevant.
Using a template like this can help ensure that all important information about each requirement is captured and can be easily understood, tracked, and communicated.
