BR.

150 – Instructions
Objective

The purpose of this document is to capture the business and information system requirements necessary to
meet a set of defined business objectives. The BR.150 (Functional Business Requirements / GAP
Analysis) document should help the project team in:

 Defining the detailed function, data, and operational requirements that the new ERP application system
must support
 Map business requirements to application capabilities and propose solutions to gaps
 Demonstrate that the proposed business process design is feasible

The BR.150 document should include the following:

 Detailed Business Requirements Scenarios that depict sequenced elementary business functions for
mapping process steps to the new system
 Definition of Reporting and user interface requirements for each business function
 Mapping of high-level and detailed business requirements to application functionality to prove the
viability and feasibility of proposed business processes and its integration

Conventions/Best Practices for BR. 150 (Functional Business Requirements /GAP Analysis)

The BR.150 template outlines the format requirements for the document. The document must include the
following sections:
 Document Control
 Definitions
 Business requirement identification and Gap analysis section
 Open and closed issues for Issue tracking and follow-up.

Document Control: Changes and updates to the document should be clearly indicated in this section by
providing details of date of updates, Person who updated the document, change references indicating at a
high level what was updated or reasons for update and versioning the document with an incremental
version number.

Definitions: This section should list the meaning of abbreviations used through out the document and
terms or phrases that may have special connotation in the context of the document. For the purpose of
clarity and reference simplicity certain definitions have already been embedded in the BR.150 document
template

Business requirement identification and Gap analysis section

This is the most important section of the document and should follow the following conventions:

 The business requirements documents should be prepared for each business function like Order
Management, Inventory, and Finance
 The business requirements should be further grouped in to business processes related to the functions.
e.g. Order Management requirements should be further grouped in to ‘”Quote Process”, “Order Entry “,
Fulfillment of Order”, ‘”Shipment” and “Invoicing”. A unique identifier should identify each of these
requirements. This would help tracking of requirements to the Solution Document (BP.080) and test cases
- scenarios
 The requirement document should include the expected functional capabilities, interfacing and user
interface requirements, security requirements, expected performance levels and should list constraints and
limitations if any
 All requirements for a particular business process should be grouped or listed in the sequence of its
logically flow.

Review Matrix

The following is the Review rating criteria that should be followed by the reviewer of this
document.

Review comment classification Review

Ratings
Standard Template not adopted High
Customization is a solution for a requirement that can be easily High
implemented via a standard product feature
Document versions not maintained and document control section not Medium
updated
Requirements not organized as per conventions Medium
Other comments Low