Professional Documents
Culture Documents
Business Requirement Document
Business Requirement Document
<Project ID>
<Project Name>
Business Requirement Document
QMS V4.0.0
Page 2 of 9
Business Requirement Document
QMS V4.0.0
Table of Content
1 INTRODUCTION............................................................................................................... 5
1.1 SCOPE...................................................................................................................................5
1.2 REFERENCES........................................................................................................................5
1.3 DEFINITIONS, ACRONYMS AND TERMINOLOGY.................................................................5
2 CURRENT SYSTEM.......................................................................................................... 5
3 PROPOSED SYSTEM........................................................................................................ 5
9 INTERFACE REQUIREMENTS...................................................................................... 7
10 ANALYSIS OF REQUIREMENTS................................................................................... 7
11 SYSTEM REQUIREMENTS............................................................................................. 7
12 ACCEPTANCE CRITERIA............................................................................................... 8
Page 3 of 9
Business Requirement Document
QMS V4.0.0
Page 4 of 9
Business Requirement Document
QMS V4.0.0
1 Introduction
1.1 Scope
[The purpose of this document is to collect, analyze, and define high-level user
needs and product features. Focus on capabilities needed by the target users
and why these needs exist. The specific requirements of how the application
fulfills these needs should be provided elsewhere in the software
requirements specifications and the use case specification.]
1.2 References
[Provide a list of all documents that require]
2 Current System
[Describe the current system if exists that is being used. Depict the current system
using flow charts/ data flow diagrams if possible.]
3 Proposed System
[If there is any proposed system by the stakeholders then provide the description of
that system]
S
Name Designation Email Contact
L
1
2
3
4
Page 5 of 9
Business Requirement Document
QMS V4.0.0
5
6
Description/Business Logic
Prototype/Mock Screen
Application/Process Impacted
Page 6 of 9
Business Requirement Document
QMS V4.0.0
Description/Business Logic
Prototype/Mock Screen
Application/Process Impacted
Priority Status
(Essential (In-Process
(E), (I), Agreed
Req. ID Reason of Priority & Status
Conditional To (A),
(C), Rejected
Optional (O)) (R))
(Optional, The description or any kind of
[FR-
[E] [I] recommendations for particular
001]
requirements)
SL Description
No Requirements
.
(Optional, The description of any kind
(Optional, The name of any kind of
1 of constrains for particular
constrains for particular requirements)
requirements)
7 Interface Requirements
Page 7 of 9
Business Requirement Document
QMS V4.0.0
SL
Requirements Description
No.
1 (Optional, The description of any kind of constrains for particular requirements)
8 Analysis of requirements
[Provide business flow if required]
9 System Requirements
[Provide description of system requirement which includes hardware/software specification (if required]
SL
Requirements Description (Hardware/Software)
No.
10 Acceptance Criteria
Page 8 of 9
Business Requirement Document
QMS V4.0.0
Signature Signature
Page 9 of 9