Business Requirements Documentation

Business Requirements Documentation

<Name of the Project>

<Month YYYY>
<Version X.XX>

<Name of the Company>

<Address of the Company>

1.0 Document Revisions

Date Version Number Document Changes

ex. 2/15/17 0.1 Initial Draft

<Name of the System> Page 1

Business Requirements Documentation

2.0 Approvals

Roles Name Signature Date

Project Manager

Document Analyst

System Analyst

Business Analyst

Project Adviser

3.0 Introduction

Software Design Document is the design work product that formally documents the design of the software
components. Software Design Document gives us the detailed description about the flow of the project.

3.1 Project Summary

3.1.1 Objectives

The main objective of this document is to illustrate the requirements of the project Library Management
system. The document gives the detailed description of the both functional and non functional
requirements proposed by the client. The document is developed after a number of consultations with the
client and considering the complete requirement specifications of the given Project. The final product of
the team will be meeting the requirements of this document.

3.1.2 Background

<Name of the System> Page 2

Business Requirements Documentation

3.1.2.1 Business Drivers

3.2 Project Scope

Project Title : Library Management System Date : Prepared By : Project Justification: This project
is basically updating the manual library system into an internet based application so that the users can
know the details of their account ,availability of books etc., Product Characteristics and Requirements : 1.
Secured database.

2. User tracking

3. Search feature

4.Calculating fines

5. Checking the availability of books.

6.Students will get an E-mail before the due date in order to avoid fines

Project Management Deliverables:

Project plan, Research finding report, Work breakdown structure, Scope statement,

Project charter, Training manuals, lessons learned report etc.,

Product-related deliverables :

Research reports ,design documents, software code, hardware ,test plan,

project benefit measurement plan etc.,

Project Success Criteria: Our main goal is to complete this project within allotted dead

line and also within the budget allotted. It is necessary to develop a method for capturing

the benefits while the Library management system is being developed, tested, and after it

is rolled out. If the project takes a little longer to complete or costs a little more than

planned, the firm will still view it as a success if it has a good payback and helps promote

the firm’s image as an excellent management organization

3.2.1 In Scope Functionality

3.2.2 Out of Scope Functionality

3.3 System Perspective

3.3.1 Assumptions

<Name of the System> Page 3

Business Requirements Documentation

3.3.2 Constraints

3.3.3 Risks

3.3.4 Issues

4.0 Business Process Overview

4.1 Current Business Process (As- Is)

4.2 Proposed Business Process (To-Be)

5.0 Business Requirements

The requirements in this document are prioritized as follows:

Value Rating Description

1 Critical This requirement is critical to the success of the project. The project will not
be possible without this requirement.
2 High This requirement is high priority, but the project can be implemented at a
bare minimum without this requirement.
3 Medium This requirement is somewhat important, as it provides some value but the
project can proceed without it.
4 Low This is a low priority requirement, or a “nice to have” feature, if time and cost
allow it.
5 Future This requirement is out of scope for this project, and has been included here
for a possible future release.

5.1 Functional Requirements

Req # Priority Description Rationale Impacted

stakeholders

General Functionality

FR-G-001 1 A new Master Single repository Development

Widget repository simplifies teams
shall be created to management of
house the name widget Infrastructure
records and links development engineers
to the widget across 30+ global
objects. development
teams

Security Requirements

<Name of the System> Page 4

Business Requirements Documentation

FR-S-001

Reporting Requirements

FR-R-001

Usability Requirements

FR-U-001

Audit Requirements

FR-A-001

5.2 Non-Functional Requirements

ID Requirement

NFR-001 The WINS repository shall accommodate up to 100 users concurrently.

NFR-002 The WINS repository shall be designated at Level 2 for availability and SLA purposes.

NFR-003

NFR-004

NFR-005

6.0 Appendices

6.1 List of Acronyms

6.2 Glossary of Terms

6.3 Related Documents

<Name of the System> Page 5

 Business Requirements Documentation

BRD Content Descriptions are as follows:

Objectives

- Describe the overall goal in developing the product, high level descriptions of what the product
will do, how they are aligned to business objectives, and the requirements for interaction with
other systems.

Background

- Provide a brief history of how the project came to be proposed and initiated, including the
business issues/problems identified, and expected benefit of implementing the project/developing
the product.

Business Drivers

- List that make development of this product important. These can be financial, operational, market
or environmental.

Project Scope

- Describe what work is in scope for the project, and specifically what work is out of scope beyond
the current budget, resources and timeline as approved by the project stakeholders.

System Perspective

- Provide a complete description of the factors that could prevent successful implementation or
accelerate the projects, particularly factors related to legal and regulatory compliance, existing
technical or operational limitations in the environment, and budget/resource constraints.

Business Process Overview

- Describe how the current process(es) work, including the interactions between systems and
various business units. Include visual process flow diagrams to further illustrate the processes the
new product will replace or enhance.
Business Requirements
- Elicited from stakeholders should be listed, categorized by both priority and area of functionality
to smooth the process of reading and tracking them

<Name of the System> Page 6

Business Requirements Documentation

Non-Functional Requirements

 Operating System: Windows 9x/xp ,Windows ME

 Processor: Pentium 3.0 GHz or higher

 RAM: 256 Mb or more

 Hard Drive: 10 GB or more

Client side:

 Operating System: Windows 9x or above, MAC or UNIX.

 Processor: Pentium III or 2.0 GHz or higher.

 RAM: 256 Mb or more

<Name of the System> Page 7