Explain Comparison Between BRD vs SRS vs FRD 

	BRD	FRD / FRS	SRS
Scope	Project Objective, Project Scope, Stakeholders, Success Criteria It depends on WHAT & WHY Project	All Detailed Granular Functional Requirement as form UML & Data Flow Diagram	Project’s All Functional & Non Functional Requirement Security, Performance, Reliability, Scalability Availability
Created By	Business Analyst	Functional Analyst	Business Analyst
Focus	What & Why Project is going to be created	Defines How the system will work to meet those business needs.	detailed document (functional and non-functional )requirements & providing a final or comprehensive blueprint of the system
Audience	Business Analyst, Stakeholders, Project /Product Managers	Development Team , QA Team,	Development Team , QA Team,
Prepared In	Initial Phase	Planning Phase	Planning Phase
Example	Need to improve customer experience through a new system	Users can register, search for products, and purchase online	The system must handle 1,000 users with no more than 2-second response time

The Flow of BRD (Business Requirements Document) & FRD (Functional Requirements Document) or FRS (Functional Requirements Specification) & SRS (Software Requirements Specification)

First Created- BRD (Business Requirements Document)

Second Created – FRD (Functional Requirements Document) or FRS (Functional Requirements Specification)

Third Created – SRS (Software Requirements Specification)