BRD Document

The purpose of this document is to collect, analyze, and define high-level needs and features of the AP Exception Handling project. It focuses on the capabilities needed by the stakeholders and the target users, and why these needs exist. The details of how the AP Exception Handlingproject fulfills these needs are detailed in the use-case and software requirements specifications.

Detail about as-is process and current shortcoming or what is reason to have this project.

As-is process flow

To be process and complete UML diagram or process flow or process modeling diagram. This is very important

………………………………………..

Scope of Project

Ideally, this will be represented as a set of high-level bullet points that correspond to high level requirements.

Each bullet Requirement here will or should have a corresponding set of detailed Requirements elsewhere within or outside the document.

As the name implies, Out of Scope sub-section explains what NOT will be delivered by this project, and (usually) why. This is important to manage expectations of your stakeholders (assumptions about scope are, as you will be aware, a major source of heartburn during implementation sign-off).

On Agile projects, high level requirements usually correspond to Epics and the big User stories that make up these epics.

For most non-project stakeholders, the Overview and Scope sections provide sufficient information about the project, so it is important to be both concise and precise at the same time.

Document the requirements that your Business Sponsor or Product Owner need to be delivered by this project/initiative. Requirements can be classified under several headers – the internet provides a variety of responses for the search string ‘types of requirements. What we need is a standard format that you can use to document all requirements.

A cookie cutter format for documenting requirements would be:

· Index – can start from 1, 2, 3… for high level requirements and go on to 5.1, 5.2, 5.1.1, 5.1.2 and so on for lower level requirements. You can apply such numbering conventions to Agile user stories

· Title Description – brief description of the high-level requirement.

· Detailed Description – self-explanatory. User stories in the form of ‘As a customer, I can… so that…’ fit here.

· Owner – usually the Business Sponsor or the Product Owner. Can also be stakeholders like IT, Marketing, Legal, Compliance etc. depending on the requirement.

· Priority – High, Medium, Low (or a variation of this)or number 1 to 9. 1 means most imp