Instruction
This document provides more detail regarding the business requirements associated with the project. This document is to be used in conjunction with the Project Charter and is not intended to duplicate information that exists in the project charter.
If business requirements change during the project (based on new information received, change in funding, or other reason), this document should be updated accordingly.
Note: Technical solutions are not addressed in this document. A separate Design document will be created to detail how NUIT will technically address the business requirements outlined below.
1. Business Process Flow / Overview
This section shows the current and proposed business process diagrams. The current business process flow diagram describes the current process accurately, including any flaws that exist in today's process that will be repaired by the proposed process. The proposed business flow diagram describes the proposed process accurately.
1.1 Current Business Flow Diagram
m here]
ere]
1.2 Proposed Business Flow Diagram
m here]
ere]
2. Dependencies
This section defines the specific dependencies that may affect the project team's ability to implement the project. Given their potential impact on the project, these dependencies should be addressed as quickly as possible.
3. Security Requirements
This section defines the user’s specific security needs and the security measures that must be present in the final product.
4. Performance Requirements
This section defines the user’s required level of performance and the performance measures that must be present in the final product.
5. Availability Requirements
This section defines the timeframes during which the solution must be available to meet the needs of the business. This section also details how the user wants to learn about system disruptions (timing, mode of communication, who to contact, etc.).
6. User Requirements
This section outlines the users specific expectations of the look, feel, and functionality of the finished product. For example, this might include reporting formats, interactions with other systems, data management, remote access, batching needs, process flows, etc.
7. Business Policies and Procedures
This section lists of all business policies and procedures that . . .
a) are affected by this project
b) have an effect on this project
c) have an effect on the design of the solution
d) have to be modified because of this project.
8. Business Operational Requirements
This section defines the operational requirements (activities) of the supporting personnel and the basic level of service that should be provided to support this project/solution.
9. Business Test Scenarios/Acceptance Criteria
This section defines the specific tests the user will conduct to determine the success of the project. This section should include the conditions that need to be met in order for the solution to be accepted by the client. Note: Indicate which requirement(s) goes with each test scenario. For larger projects, it may be useful to create a separate detailed test case (use case) document.
10. Other Considerations
This section includes any other user needs that haven’t been captured above (e.g., inputs, outputs, interactions, etc.). It may also be used to capture initial technical issues and considerations that should be taken into account during the Design of the solution.
11. Business SME Contact List
This section lists the Subject Matter Experts (SME’s) who are involved with the project and/or impacted by the solution.
SME Name / SME Business Area / SME Contact Numberand Email
Approval and Revision History
This section records the history of changes and approvals to this document.
Ex: Tom Jones / 1/1/11 / Enhanced security requirement by minimizing #people who have access to system.
Reason: grant requirement. / v.1
Ex: Tom Jones / 1/3/11 / Approval / v.2
Date Printed: 6/15/2011 Page 2 of 3
File Name: Business Requirements Analysis_v1 (with headers and footers).docx NUIT Confidential