[The specific business requirements elicited from stakeholders should be listed, categorized by both priority and area of functionality to smooth the process of reading and tracking them. Include links to use case documentation, and other key reference material as needed to make the requirements as complete and understandable as possible. You may wish to incorporate the functional and non-functional requirements into a traceability matrix that can be followed throughout the project.]
The requirements in this document are prioritized as follows:
Value
Rating
Description
Critical
This requirement is critical to the success of the project. The project will not be possible without this requirement.
High
This requirement is high priority, but the project can be implemented at a bare minimum without this requirement.
Medium
This requirement is somewhat important, as it provides some value but the project can proceed without it.
Low
This is a low priority requirement, or a “nice to have” feature, if time and cost allow it.
Future
This requirement is out of scope for this project, and has been included here for a possible future release.
Functional Requirements
Req#
Priority
Description
Rationale
Use Case Reference
Impacted Stakeholders
General / Base Functionality
FR-G-001
A new Master Widget repository shall be created to house the name records and links to the widget objects.
Single repository simplifies management of widget development across 30+ global development teams
Development teams
Infrastructure engineers
FR-G-002
A widget shall be defined in the repository via a unique identifier and name combination.
ID+Name eliminates duplicate widget name records
FR-G-003
FR-G-004
FR-G-005
Security Requirements
FR-S-001
Widget creation in the repository shall be limited to users with Team Lead or System Administrator,
Reporting Requirements
FR-R-001
The system shall generate a weekly Report of Widget Name Status Changes
Usability Requirements
FR-U-001
User interface for the WINS repository shall be responsive, allowing for proper display on tablet, laptop, and desktop devices.
Audit Requirements
FR-A-001
Any change to a widget name record shall be appended with user ID and date/time stamp.
Non-Functional Requirements
[Include technical and operational requirements that are not specific to a function. This typically includes requirements such as processing time, concurrent users, availability, etc.]
ID
Requirement
NFR-001
The WINS repository shall accommodate up to 100 users concurrently.
NFR-002
The WINS repository shall be designated at Level 2 for availability and SLA purposes.
NFR-003
NFR-004
NFR-005
Appendices
List of Acronyms
[If needed, create a list of acronyms used throughout the BRD document to aid in comprehension.]
Glossary of Terms
[If needed, identify and define any terms that may be unfamiliar to readers, including terms that are unique to the organization, the technology to be employed, or the standards in use.]
Related Documents
[Provide a list of documents or web pages, including links, which are referenced in the BRD.]
