BRD- Business Requirement Document or BRS Document- Business

Requirement Specification Document both are same. The

Business/Client/other Stakeholders provide a requirement. One
requirement can be small or big. But, has to be break wherever it
requires and taken as multiple requirements.

FRD- Functional Requirement Document or FRS Document-

Functional Requirement Specification Document both are same. The
Process to reach the expectancy of the BRD is an FRD. How we develop
the expected requirement? What are the features? Functionalities? Tools
or Systems used and interdependencies? How they react when start
working together when this Functionality takes place? Assumptions?
Limitation? any other supporting Process Flows/Maps/Wiring Diagrams
etc..

Best Example:

BRD- Need a Motorcycle which should make work me and i should

make it work to reach my destination.

FRD-

How does Motorcycle looks?

What parts are included to assemble it?

Step by Step process as how it can be assemble it?

How it can be used?

Its Performance- Speed, Accuracy?

Used Case, Process Flows etc for each activity interlinking

dependencies. Ex: When U drive the Motorcycle, How the Engine
Works, Handle Turns, Braking, Seating, Chain System, Light etc..

Assumptions & Limitations?

Now, the above BRD can be considered as Single Requirement or

broken into multiple requirements? I believe yes- it has to be broke
into multiple requirements.If yes, then=>

BRD=> Need a Frame which can fit the Handle, Seat, Carriage, Pedal,
Chain System, Stand=> Center/Side Stand etc..

FRD=> About the Frame=> How the Frame to be?Features=>

Functionalities=> Performance=>Assumptions=>Limitations.

Hope this will make u understand as a lay man. U can corelate to any
Software or Hardware Process.....

BRD- Business Requirement Document or BRS Document- Business Requirement

Specification Document both are same. ... FRD- Functional Requirement Document or FRS
Document- Functional Requirement Specification Document both are same. The Process to
reach the expectancy of the BRD is anFRD

Business requirements are often listed in a Business Requirements Document or

BRD. The emphasis in a BRD is on what is required, rather than on how to achieve it;
this is usually delegated to a Systems RequirementsSpecification or Document (SRS
or SRD), or other variation such as a Functional Specification Document.