1.

0 Document Revisions
2.0 Approval
3.0 Introduction
The Business Requirements Document (BRD) and the purpose of capturing
and describing the business needs of the customer/business owner identified
within the RUSI Motorcycle Company provides organizational context for this
RMC BRD to a Framework, which depicts the overall capabilities desired for
the future state and glossary that applies to both of the business requirements
documentation
3.1 Project Summary
3.1.1 Objectives
3.1.2 Background
3.1.2.1 Business Drivers
3.2 Project Scope
3.2.1 In Scope Functionality
3.2.2 Out of Scope Functionality
3.3 System Perspective
3.3.1 Assumption
3.3.2 Constraints
3.3.3 Risks
3.3.4 Issues
4.0 Business Process Overview
4.1 Current Business Process (As-Is)
4.2 Propose Business Process (To-Be)
5.0 Business Requirements
5.1 Functional Requirements
Functional requirements describe all of the things that a system must be
able to performthat is, the system behavior. All other requirements are
non-functional. The non-functional requirements will be addressed in the
technical requirements, which will be attached to the Performance Work
Statement
5.2 Non- Functional Requirements
6.0 Appendices
6.1 List of Acronyms
6.2 Glossary of Terms
6.3 Related Documents