BRD VS FRS

BRD VS FRS
BRD ( BUSINESS REQUIREMENT DOCUMENT):-
BRD is the reference document for identification and documentation of business requirements ,on short form business opurtunities which the project will bring business requirement document document will also define what are the availibilble oppurtunities or the benefits of the project ,what is the current stage of the project or if there is no an d then what is the target stage of the project and what is achieved by the business requirements once completed .
They describe the reasons why a project has been intiated ,the objectives that the project will achieve , and the metrics that will be used to measure its success .BRD also acts as an agreement document between business and delivery team assigned of BRD will mean that business approves the requirements captured in the document
BRD is needed for assigning of BRD will act as a reference document for the business requirements so if multiple people want to refer regarding the business requirements of a project they can refer to one single signed of brd to communicate between different stakeholders regarding the project a BRD is very helpful as a BRD of the document can be shared with multiple stakeholders for their review and comments. A BRD usually captures high level requirements of a project but it is important to be clear on what other in scope requirements but are out of scope requirements for the project which BRD can help with .
Requirements documented in a BRD will helps remove ambiguity over the requirements as it will be clearly defined in the document what is supposed to be done and what is supposed to be achieved .
BRD also helps the project or delivery team to get sign off from the business as a BRD will act as a reference document to which business has agreed that these are the reuirements which will be delivered those we are already captured in the document and signed off by the business . It is important to follow standard structure for BRD although different organizations may use different structure but the points we have mentioned below will usually is needed to be covered in each and every business requirement document however the order vcan vary from the organization to organization they are :-
1.Document revisions
2.Approvals
3.RACI chart for this document
3.1 Codes used in RACI chart
3.2 RACI chart
4.Introduction
4.1 business goals
4.2 business objectives
4.3 business rules
4.4 background
4.5 project objective
4.6 project scope
4.6.1 Inscope functionality
4.6.2 Outscope functionality
5.Assumptions
6.constaraints
7. Risks
• TECHNOLOGICAL RISKS
• SKILLS RISKS
• POLITICAL RISKS
• BUSINESS RISKS
• REQUIREMENT RISKS
• OTHER RISKS
8. Business process overview
8.1 legasy system
8.2 proposed recommendations
9.Business requirements
10.Appendices
10.1 list of acronyms
10.2 Glossary terms
10.3 Related documents
BUSINESS REQUIREMENTS CHECKLIST :-
• Specific and unique requirement
• Measurable and achievable requirement
• Realistic and time boundad requirement
• Unambiguous and complete requirement
• Prioritizing requirements
• Requirement dependencies

FRS ( FUNCTIONAL REQUIREMENT SPECIFICATION ):-
Functional requirement specifications document or the FRS is describes how exactly the system is expected to function in order to satisfy all the requirements listed in the BRD and SRS ( software requirement specification).
FRS document is created from the prespective of a user and describes how the software will behave when an external user interacts with it the FRS is usually prepared by the business system analyst on the project and post completion this document is reviewd by the project manager
In FRS there are two types of requirements they are :-
1.Functional requirements:- It describe the behavior and information that the solution will manage .they describe capabilities the system will be able to perform in terms of behaviors or operations that means specific information technology application actions or responces .
2.Non functional requirements :- It captures conditions that do not directly relate to the behavior or functionality of the solution ,but rather describe environmental conditions under which the solution must remain effective or qualities that the systm must have.they are also known as quality or supplementary requirements ,mostly thes requirements are related to capacity ,speed security ,availability and the information architecture and presentation of the user interface .
FRS also have a different structure are as follows they are :_
1.Document version control list
2.Distribution
3.Business rules
4.System rules
5.Control flow
6.Purpose
7.Project background
8.Project objective
9.Business requirements
9.1.Stakeholder requirements
10Assumptions and constraints
11.Usecase diagrams (uml)
11.1Actor specific use case diagrams
11.2Usecase specifications
12.Activity diagrams
12.1Process specific activity diagrams
12.2Activity specifications
12.3Basic flow
12.4.Alternate flow
12.5.Exception flow
13.Functional requirements
14.Non functional requirements
15.Proto typing
16.Master tables
17.Notes
These are the diference between BRD VS FRS .