Functional Requirements Template
Document and organize functional requirements derived from stakeholder interviews and research.
Project Information
- Project Name: _________________________
- Version: _________________________
- Date Created: _________________________
- Last Updated: _________________________
- Prepared By: _________________________
- Approved By: _________________________
Executive Summary
Project Description: (One paragraph overview of what this project is about)
Business/User Need: (Why is this project important?)
Stakeholders:
- Primary user: _____________________________________________________
- Secondary users: __________________________________________________
- Decision makers: __________________________________________________
Functional Requirements
Organization Strategy
Requirements organized by:
- User role/perspective
- Feature/component
- Priority level
- Other: _______________
Primary Functional Requirements
Core features that define the product
FR1: [Feature Name]
Priority: [ ] Critical [ ] High [ ] Medium [ ] Low
Description: What the product must do:
User Stories:
-
“As a [user type], I want to [action] so that [benefit]”
-
-
“As a [user type], I want to [action] so that [benefit]”
-
Acceptance Criteria:
- _________________________________________________________________
- _________________________________________________________________
- _________________________________________________________________
Related Requirements: ____________________________________
FR2: [Feature Name]
Priority: [ ] Critical [ ] High [ ] Medium [ ] Low
Description:
User Stories:
Acceptance Criteria:
- _________________________________________________________________
- _________________________________________________________________
Related Requirements: ____________________________________
FR3: [Feature Name]
(Continue with additional primary requirements)
Secondary Functional Requirements
Important supporting features
FR-S1: [Feature Name]
Priority: [ ] High [ ] Medium [ ] Low
Description:
Acceptance Criteria:
- _________________________________________________________________
- _________________________________________________________________
FR-S2: [Feature Name]
(Continue with secondary requirements)
Non-Functional Requirements
Performance, reliability, and design properties
Performance Requirements
- Response time: ___________________________________________________
- Throughput: _______________________________________________________
- Resource usage: ___________________________________________________
Reliability Requirements
- Failure rate acceptable: _____________________________________________
- Recovery capability: _________________________________________________
- Data persistence: ___________________________________________________
Physical Requirements (for 3D printed objects)
- Dimensions: ________________________________________________________
- Weight capacity: ____________________________________________________
- Material properties: __________________________________________________
- Temperature range: __________________________________________________
- Durability: ________________________________________________________
Accessibility Requirements
-
Usable by people with visual impairment
- How: __________________________________________________________
-
Usable by people with motor impairment
- How: __________________________________________________________
-
Usable by people with hearing impairment
- How: __________________________________________________________
-
Usable by people with cognitive differences
- How: __________________________________________________________
Constraint Requirements
Limitations on design and implementation
Technical Constraints
- Must work with: ____________________________________________________
- Must not require: __________________________________________________
- Must be compatible with: ____________________________________________
Physical Constraints
- Cannot exceed (size/weight/cost): _____________________________________
- Must fit in/with: ___________________________________________________
- Must be available by (date): _________________________________________
Regulatory/Safety Constraints
- Must comply with: __________________________________________________
- Must not: __________________________________________________________
- Safety considerations: _______________________________________________
Cost Constraints
- Maximum budget: ____________________________________________________
- Target unit cost: ___________________________________________________
Environmental Context
Use Environment
- Location(s): _______________________________________________________
- Climate conditions: _________________________________________________
- Physical surroundings: _______________________________________________
- Typical usage pattern: _______________________________________________
Maintenance & Lifecycle
- Expected lifespan: __________________________________________________
- Maintenance needed: ________________________________________________
- End-of-life handling: ________________________________________________
Dependency Mapping
Requirements that depend on other requirements:
| Requirement | Depends On | Notes |
|---|---|---|
| FR1 | ||
| FR2 | FR1 | Cannot implement without FR1 |
| FR3 |
External dependencies:
- Third-party components needed: ________________________________________
- Integration points: __________________________________________________
Scope Definition
What IS In Scope
What IS NOT In Scope
Future Considerations (Out of Scope but noted)
Change Control
Requirements Changes:
| Change Request | Date | Reason | Status |
|---|---|---|---|
Verification Plan
How will we verify each requirement is met?
| Requirement | Verification Method | Test Case | Status |
|---|---|---|---|
| FR1 | [Inspection/Test/Demo] | ||
| FR2 | [Inspection/Test/Demo] |
Sign-Off
Stakeholder Approval:
| Stakeholder | Title | Signature | Date |
|---|---|---|---|
Requirements Baseline Approved: Date: ____________ Status: Approved / Pending / Rejected
Reference Documents
- Interview notes: ____________________________________________________
- Design sketches: ____________________________________________________
- Related specifications: _______________________________________________
- Standards/guidelines: ________________________________________________
Document Version History:
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | Initial draft | ||