Professional Documents
Culture Documents
PM Lite
Requirements Document
Template
Template Description
1 Purpose
The Business Requirements document details specific project and product requirements that must be met to satisfy
the business objectives.
2 How to Use
This template provides a mechanism to track product/project deliverables against requirements to ensure
business and product requirements are met.
3 Best Practice
Requirements may start out at a high level and become progressively more detailed as more information is
known. Requirements must be unambiguous (measurable and testable), traceable, complete, consistent, and
acceptable to key stakeholders. A requirements management plan should be defined to document how
requirements will be captured, measured, analyzed, and managed.
Note: The PM Lite Requirements Document Template is customizable as you see fit, on a per project basis,
meeting specific needs of the project and/or your organization’s policies. The below sections are suggestions but
can be tailored as applicable.
**NOTE: Please remove this page when creating your Requirements Document**
PM Lite 2.0 Requirements Document Template Texas Department of Information Resources
This section is to designate The ID-Prefix refers The ID-Number Explain what the Located within the Business Case, Referring to the Project Charter, Define priority of The status column is referring A test case is a set of Any additional notes for
which category of to a designated uniquely identifies specific requirement is the business objectives are usually identify the project/product requirement based on to the current standing of conditions or variables this requirement. (E.g. a
requirement it falls under. letter meant to individual and what it embodies related to the supporting the requirement this specific/ detailed your specific business that particular requirement. under which a tester will dependency that exists or a
distinguish the requirements in terms of what is agency's and/or division's requirement will support. need. Prioritization of These are meant to help determine if the specific timeframe that
requirement as within a specific needed from the business needs. Refer to the requirements can help track the progress of meeting requirements are met. needs to occur.)
being of that requirement type. project. Ensure each Business Case Reference ID of the manage limited resources that requirement. This column is used to
requirement type. specific requirement is goal/objective this requirement and prioritize specific risks track the test case by its
unique, concise, and will support. and/or business needs. given number. Test cases
testable. should be defined and
tracked in a separate test
plan.
Feature-Function F 0001
Requirements F 0002
F 0003
(Things that the
system/application F 0004
system/application F 0005
must be able to do F 0006
in order for the user to F 0007
achieve his/her goals) F 0008
Reporting R 0001
Requirements R 0002
Reporting R 0003
Requirements R 0004
R 0005
R 0006
R 0007
R 0008
User Access/Security U 0001
Requirements U 0002
User Access U 0003
U 0004
U 0005
U 0006
U 0007
U 0008
Interfaces I 0001
I 0002
Interfaces I 0003
I 0004
I 0005
I 0006
I 0007
I 0008
Service Level/ S 0001
Performance/ S 0002
Scalability/ S 0003
Information S 0004
Security Requirements S 0005
Requirements S 0006
S 0007
S 0008
M 0001
M 0002
Support and M 0003
Maintenance M 0004
Requirements M 0005
M 0006
M 0007
M 0008
OR 0001
OR 0002
Other OR 0003
OR 0004
OR 0005
OR 0006
Status Tested
New Pass
Need
Additional
Information Fail
Approved
Duplicate
Validated
Implement
ed