You are on page 1of 17

BUSINESS REQUIREMENTS DEFINITION

WORKING DOCUMENT

ProjectName
DepartmentName

CompanyName

0 Page 2 of 17 . completeness or suitability of the content of this template and your use of it. Revision History: Date Version Name Description of Changes Mar. While we have used reasonable care and skill in the creation of this template. 1.0 IAG Consulting Initial Creation CompanyName version 1.Business Requirements Document ProjectName This template was created by IAG Consulting for use as is. 2009 1. tort or otherwise) for the accuracy. we do not warrant and we exclude all liability (whether arising in contract.

.......................................................................10 PROCESS DEFINITION.......................................................................................................... 9 Non-Functional Requirements List..................................................... 4 Purpose of this Document........ Risks.............................................................................................................................3 INTRODUCTION......................... 4 Project Objectives............................................................................................................................................. 12 DATA DEFINITION....... 8 REQUIREMENTS.............................................................................................................................................................................................................................................................................................................16 CompanyName version 1.Business Requirements Document ProjectName TABLE OF CONTENTS BUSINESS REQUIREMENTS DEFINITION..... 9 Functional Requirements List....................................... 15 APPENDIX.................................................................................................................................................... 6 Use Case Diagram..................... 4 Summary of Scope.................................................................................................................................................... 14 Entity / Use Case Table........................................ 16 Appendix 1 – Glossary of Terms and Acronyms.......................................... 4 Constraints....................................................................................................................................................................................................................................................................................................................................................................11 1 Use-Case-Name.............................................................................................................................................................0 Page 3 of 17 .................................................................. 14 Entity Relationship Diagram........................................................................................................................................................................................................................................9 Information Requirements List................................................................................................................................................................................................................................................................................................................... Dependencies...............................................................................5 Project Team................. 4 Executive Summary................................................................................................................................................................... 9 Business Rules List................................ 14 Entity-Name....................................................................................................................................................................................................................................................................................................................................................1 TABLE OF CONTENTS....................................... 5 Context Diagram...... 7 Process Swim Lane Diagram................................................................................ 4 Business Objectives...................................................................................................................................................... 4 Issues................................. Assumptions.....................................

Purpose of this Document Describes the purpose of the document. scope and description of the requirements. which are: Specific Measurable Attainable Results-Oriented Time-Bounded  Objective#1 Project Objectives Describe the product(s) or service(s) being proposed by this project to positively impact the business.0 Page 4 of 17 . and the intended audience. and a summary of the objectives. the intended audience for the document.Business Requirements Document ProjectName INTRODUCTION Executive Summary This section should describe the purpose of the BRD. The standard for any objective is that it meets the “SMART” properties.  Objective#1 Summary of Scope Please refer to the complete document as a definition of scope. Business Objectives Describe objectives that will be used to measure the success of the project. The following is a summary of the in scope and out of scope activities and scenarios: In Scope Activities:  In Scope Scenarios:  Out of Scope:  Issues Issue Description CompanyName Resolution version 1.

interfaces. which must be confirmed Risks – quantifiable losses to the business as a result of not proceeding or as a result of failure of the project Dependencies – an external need which the project’s completion is contingent upon  Project Team The following team members were integral in the development and contributions to this specification: Name CompanyName Role version 1.0 Page 5 of 17 .Business Requirements Document ProjectName Constraints. functionality. Dependencies Describe factors which limit the project including: Constraints – factors which inhibit the project’s ability to deliver Assumptions – decisions made about scope. Assumptions. Risks. etc.

Business Requirements Document ProjectName Context Diagram Context Diagram CompanyName version 1.0 Page 6 of 17 .

Business Requirements Document ProjectName Use Case Diagram Use Case Diagram CompanyName version 1.0 Page 7 of 17 .

0 Page 8 of 17 .Business Requirements Document ProjectName Process Swim Lane Diagram Swim Lane Diagram CompanyName version 1.

2. the mean time to failure for the entire system must be at least six months. Detailed functionality. Requirement ID # Use Case Steps 1.0 Page 9 of 17 . Ninety percent of all users must be able to use all of the functions of the system after one day’s training. RELIABILITY Describe any requirements as it relates to the times-to-failure of the entire system based on the life distributions of the components from which it is composed. business rules. Business Rules List The following list represents the business rules related to the ProjectName System. or more satisfying to use. USABILITY Describe any requirements as it relates to making the system more efficient to use. Rule ID # Business Rule Functional Requirements Entity Name Non-Functional Requirements List The following list represents the non-functional requirements for any solution that also meets the functional requirements.1. Req. e.1 1. Each requirement relates to a Step of a Use Case described and modeled in the specification. easier to learn. Each Business Rules relates to one or more Functional Requirements and/or Data Entities described in the specification as noted in the “Functional Requirements” and “Entity Name” columns.. e.Business Requirements Document ProjectName REQUIREMENTS Functional Requirements List The following list represents the functional business requirements for the ProjectName System. Use Case steps for which this is a requirement should be listed in the “Use Case Steps” column..g.1 The system must have the ability to do something with some information under certain circumstances according to business rules. CompanyName version 1. constraints and conditions for each of these requirements can be found in the detailed description of the component associated with the requirement. The ID # should be uniquely created to tie back to the Use Case Step for which it is first a requirement.g.

installability.. serviceability. OTHER Many organizations may have additional Non-Functional Requirements to be formally considered. Privacy. 90% of the time. e. SUPPORTABILITY Describe any requirements as it relates to: testability. extensibility. Information Requirements List The following list represents the business data requirements for the ProjectName. Entity Name CompanyName version 1. Note: Each requirement relates to an Entity described and modeled in the Data Definition section of the specification. ID # Requirement Entity Name EN. configurability. Response time must be within 2 seconds for 90% of all transactions SECURITY & ACCESS CONTROLS Describe any requirements as it relates to access.g. $Documentation & Training. compatibility.0 Page 10 of 17 . Req.. localizability (internationalization) e. System upgrades must be performed with no impact on availability.. e. Disaster Recovery and Business Continuity.g. Entity Name EN. User authentication shall be via the corporate Single Sign-on system. They may include but are not limited to: Audit. Infrastructure. adaptability. Volume & Scalability. Data Retention.2 The system must have the ability to do something with some information under certain circumstances according to business rules.Business Requirements Document ProjectName PERFORMANCE Describe any requirements as it relates to system availability and response time. maintainability. Sarbanes-Oxley impacts. Application Controls.g. Detailed definitions and Business Rules for each of these requirements can be found in the detailed description of the Entity associated with the requirement. user roles and security.1 The system must have the ability to add/modify/delete Entity data according to business rules.

CompanyName version 1.0 Page 11 of 17 .Business Requirements Document ProjectName PROCESS DEFINITION Copy and paste blank Use Case template below and modify to include detail for Use Cases in scope for your project.

0 Page 12 of 17 .Business Requirements Document ProjectName 1. Use-Case-Name Data Flow Diagram BPMN Diagram CompanyName version 1.1.

1.1. non-functional requirements.1.1.1.2 Step-2  Sub-step detail ALTERNATE SCENARIO DETAIL: VARIATION-1 1. CompanyName version 1. TRIGGERING EVENT(S) AND PRE-CONDITIONS  OUTCOME(S) AND/OR POST-CONDITIONS  LIST OF USE CASE SCENARIOS Primary Scenario  High-level steps Variation-1  High-level steps PRIMARY SCENARIO DETAIL 1.4 Step-2  Sub-step detail SPECIAL CONSIDERATIONS Include design considerations. legal.1 Step-1  Sub-step detail 1.0 Page 13 of 17 . etc.Business Requirements Document ProjectName SUMMARY SUMMARY USE CASE NARRATIVE Brief description of the Use Case. regulatory.3 Step-1  Sub-step detail 1.1.1.1.

Business Requirements Document ProjectName DATA DEFINITION Entity Relationship Diagram Entity Relationship Diagram Use Case 2 Entity 10 Entity 9 Entity 8 Entity 7 Entity 6 Entity 5 C* Entity 4 Use Case 1 Entity 3 Activity Entity 1 Entity Entity 2 Entity / Use Case Table R* D* Use Case 3 Use Case 4 Use Case 5 U* Use Case 6 Use Case 7 Use Case 8 * C – Create. U – Update. D – Display CompanyName version 1. R – Remove.0 Page 14 of 17 .

M = Mandatory. CompanyName version 1.0 Page 15 of 17 . N = Multi-Valued. DATA The system shall provide for the following data elements and business rules: 1 Data Element Description -id Unique identifier O/M1 1/N Rules Note: O = Optional.Business Requirements Document ProjectName ENTITY-NAME DEFINITION Describe the information that will be saved in this entity and how it will be used. 1 = Single Value.

Business Requirements Document ProjectName APPENDIX Appendix 1 – Glossary of Terms and Acronyms Term CompanyName Definition version 1.0 Page 16 of 17 .

Hint: To begin entering specifications for a new Use Case or Entity copy and paste the blank Use Case or Entity template and then update with your detail.0 Page 17 of 17 . For detailed instructions on the use of this template. please review the participant guide for the “Documenting Requirements” course. Last Page CompanyName version 1.Business Requirements Document ProjectName Note to Author (delete from final deliverable) Throughout this document there is instruction text which should be removed prior to publishing.