Information & Technology Management Standards

Business Requirements Document

The purpose of the Business Requirements Document is to describe business requirements of an application completely, accurately and unambiguously in a technology-independent manner. Requirements should be described using business terminology and business language so far as possible. Very minimal and commonly understood technical terminology may be used. Use case or Designer approach may be used in modeling the business requirements in this document. (Delete the approach that is not applicable).

The business owners of the proposed system are the main intended audience for this document. This document should be readable by business owners of the proposed system. They must be able to verify that their business requirements have been documented here completely, accurately and unambiguously.

Data Architects, Application Architects and Technical Architects would also find the information in this document useful when they need to design a solution that will address these business requirements.

Since the requirements are documented here in a technology-independent manner, the end-users of the system should be able to comprehend the requirements fairly easily from this document.

Template

Contact
Download Template Business Requirements Document Application Architect

Deliverable Reviewers

IMG Reviewers

Other Typical Reviewers
Application Architect Business Lead
Data Architect ITMB Business Analyst
Database Administrator Business Sponsor
Technical Architect    

Related Deliverables

Companion Deliverables

Successor Deliverables

Download Template Actor Profile Specification   System Function Model
Download Template Essential Use Case Specification Download Template Application Architecture Document
    Download Template Technical Architecture Document

Related Standards

Standard The Business Requirements Document should conform to the ministry's template. All sections of the document are mandatory.
Download Standard If the Designer approach is used to develop the Business Requirements Document, requirements models should conform to Requirements Modeling and Specification Guidelines and Standards .
Standard If use case approach is used to develop the Business Requirements Document, the Actor Profile Specification template should be used to document the actor profiles. Alternately, if the number of actors is small, then the actor profile information may be provided in a table in the Business Requirements Document itself.
Standard If use case approach is used to develop the Business Requirements Document, attach the Essential Use Case Specifications Document to the Business Requirements Document using the Essential Use Case Specifications Document template . Alternately, if there are fewer than 15 use cases, then use the tabular format in the Business Requirements Document itself to describe the essential use case specifications.
Download Standard Under section 69 of Freedom of Information and Protection of Privacy Act, ministries are required to conduct a Privacy Impact Assessment (PIA) to determine if a new enactment, system, project or program meets the Privacy Protection requirements in the Freedom of Information and Protection of Privacy Act. The PIA is designed to be used for all programs, legislation, systems or initiatives. See Privacy Impact Assessments in the Core Policy Manual.
Download Standard Requirements Modeling and Specification Guidelines and Standards .
Download Standard Activity Diagram Standards & Guidelines
Download Standard Domain Class Diagram Modeling Standards & Guidelines
Download Standard Essential Use Case Modeling Standards & Guidelines

 

NOTE: Acrobat Reader needed to view or print PDF versions.