CMGT/410 v19: Business Requirements Template

CMGT/410 v19

Page 13 of 14

C:UsersdjshireyOneDrive – University of PhoenixF_DriveStyle GuidesUPX LogosHorizontal formatUOPX_Sig_Hor_Black_Medium.pngBusiness Requirements Template
How to Use This Document
This document is a template for creating a Business Requirements Document (BRD); it includes instructions and examples for guidance. As you complete your BRD using the template, only include sections pertinent to your project.

Table of Contents
How to Use This Document 1

Table of Contents 1

1. Executive Summary 2

1.1 Project Overview 2

1.2 Purpose and Scope of this Specification 2

2. Product/Service Description 3

2.1 Product Context 3

2.2 User Characteristics 3

2.3 Assumptions 3

2.4 Constraints 3

2.5 Dependencies 3

3. Requirements 4

3.1 Functional Requirements 4

3.2 User Interface Requirements 5

3.3 Usability 5

3.4 Performance 6

3.4.1 Capacity 6

3.4.2 Availability 6

3.4.3 Latency 6

3.5 Manageability/Maintainability 6

3.5.1 Monitoring 6

3.5.2 Maintenance 6

3.5.3 Operations 7

3.6 System Interface/Integration 7

3.6.1 Network and Hardware Interfaces 7

3.6.2 Systems Interfaces 7

3.7 Security 8

3.7.1 Protection 8

3.7.2 Authorization and Authentication 8

3.8 Data Management 8

3.9 Standards Compliance 9

3.10 Portability 9

4. User Scenarios/Use Cases 9

5. Deleted or Deferred Requirements 9

6. Requirements Confirmation/Stakeholder Sign-Off 10

Appendices 11

Appendix A: Definitions, Acronyms, and Abbreviations 11

Appendix B: References 11

Appendix C: Requirements Traceability Matrix 12

Appendix D: Organizing the Requirements 13

1. Executive Summary
1.1 Project Overview
Describe this project or product and its intended audiences, or provide a link or reference to the project charter.

1.2 Purpose and Scope of this Specification
Describe the purpose of this specification and its intended audience. Include a description of what is within the scope what is outside of the scope of these specifications.Well-written project documentation clarifies intent, documents decisions and results, and allows project managers to assess project progress (and report it, as necessary, to project stakeholders) at every step of the project lifecycle.
For this assignment, you will create two examples of project documentation that align with the Project Plan Draft assignment you completed in Week 1. The documentation you will create for this assignment aligns with the initiation and planning phases of a project.

https://www.atlassian.com/agile/product-management/requirements