Requirements
BRD vs FRD vs SRS: what is the difference and which do you need?
Part of our guide to business analyst roles and responsibilities.
The three documents side by side
People confuse these three documents because they overlap, and different companies use the names loosely. The cleanest way to understand them is as three levels of detail answering three different questions: why, what the system does and exactly how it must behave.
| BRD | FRD | SRS | |
|---|---|---|---|
| Full name | Business Requirements Document | Functional Requirements Document | Software Requirements Specification |
| Main question | Why are we doing this and what must the business achieve? | What functions must the system provide? | What exactly must the software do and satisfy? |
| Main readers | Sponsors, business managers, steering group | Developers, testers, business analysts | Developers, testers, architects, auditors |
| Level of detail | High | Medium to detailed | Detailed and formal |
| Typical content | Objectives, scope, stakeholders, business requirements, assumptions, risks, benefits | Features, business rules, screens, inputs and outputs, error handling | Functions plus non-functional requirements, interfaces, data, constraints |
| Typical use | Approving the project | Guiding build and test | Contracts, regulated and high-risk systems |
The names are not universal. Some organisations write a single "requirements document" that mixes all three, and others use different labels such as "functional specification" for the FRD. What matters is knowing which question each section answers and who needs the answer. If your organisation has templates, learn them; this article helps you understand why they have the sections they do.
Diagram in words
- BRD: why: Business need, objectives, scope, success measures. Sponsors and business managers
- FRD: what the system does: Functions, rules, inputs, outputs, errors. Developers, testers, analysts
- SRS: exactly what it must satisfy: Functions plus non-functional, interfaces, data. Developers, architects, auditors
The BRD: the business case in requirements form
The Business Requirements Document is written first and aims at people who decide whether the project goes ahead and what it must achieve. It describes needs in business terms, without specifying how a system will meet them.
What a BRD usually contains
- Purpose and background: why the project exists, summarised from the business case.
- Objectives and success measures: ideally SMART.
- Scope: what is in and what is out.
- Stakeholders: who is affected and who decides.
- Current and desired process: an overview of the AS-IS and TO-BE.
- Business requirements: numbered statements of what the business needs.
- Assumptions, constraints and dependencies.
- Risks and benefits.
- Approval: names, roles and dates of sign-off.
A good BRD is short enough that a sponsor reads it. Its main value is to create a single agreement about what the project must deliver, which later documents and tests can refer back to. For a worked outline, see our free BRD example and outline.
The FRD: what the system must do
The Functional Requirements Document translates each business requirement into specific system behaviour. It is the main working document for developers and testers on many projects.
What an FRD usually contains
- A list of functional requirements, each with a unique ID, traceable to a business requirement.
- Business rules and calculations.
- User roles and permissions.
- Screen descriptions or wireframe references.
- Inputs, outputs, validation and messages.
- Error and exception handling.
- Reports, notifications and integration points.
Precision is the point. "The system shall remind customers about renewals" is a business requirement. The FRD says when the reminder is sent, to whom, in what channel, with which content and what happens if sending fails. Each statement should be something a tester can check. If you are writing at this level in an agile team, the equivalent is usually a set of user stories with acceptance criteria.
The SRS: the complete formal specification
The Software Requirements Specification describes the whole software product: its functions plus the qualities and constraints around them. It follows from traditions in software and systems engineering, where a precise, reviewable specification matters for contracts, safety, regulation and audit.
What an SRS usually contains
- Purpose, scope, definitions and references.
- Overall description: users, environment, assumptions.
- Specific functional requirements.
- Non-functional requirements: performance, security, availability, usability, auditability, data retention.
- External interfaces: user interface, other systems and APIs.
- Data requirements.
- Constraints, standards and compliance needs.
Many organisations treat the SRS as the FRD plus everything else the software must satisfy. In practice, the boundary between FRD and SRS is blurry, and some companies use only one. The important idea is that for complex or regulated systems, the specification is a controlled document under change control, so everyone can see what was agreed and what changed.
One requirement at three levels: a fictional insurer
Harbor Mutual is a fictional insurance company that loses some customers because policies lapse without a reminder. Here is one need written at each level so you can see the difference.
In the BRD (business requirement)
BR-04: Customers must be reminded before their policy renews, so that fewer policies lapse unintentionally. Success is measured by the share of policies that lapse within 30 days of renewal, compared with the previous year.
Notice it states the need and the measure but not the channel, the timing or the design.
In the FRD (functional requirements)
- FR-04.1: The system shall send a renewal reminder to the policyholder's registered email address 30 days before the renewal date.
- FR-04.2: The system shall send a second reminder 7 days before the renewal date if the policy has not been renewed.
- FR-04.3: The reminder shall contain the policy number, renewal date, renewal premium and a link to the renewal page.
- FR-04.4: The system shall not send a reminder for a policy that has been cancelled or already renewed.
- FR-04.5: If sending fails, the system shall record the failure and retry up to three times at one-hour intervals.
Each is specific enough to test, and each traces back to BR-04.
In the SRS (adding the wider specification)
- NFR-04.1: All reminders scheduled for a day shall be sent within two hours of the start of the batch window.
- NFR-04.2: Reminder content shall not include medical or payment-card information.
- NFR-04.3: Each send attempt shall be written to the audit log with timestamp and outcome and retained for the period required by the company's records policy.
- INT-04.1: The reminder service shall call the email provider's API using the agreed contract and shall treat any response other than success as a failure.
The SRS now covers performance, privacy, audit and the interface to another system, in addition to the functions. Reading across the three levels, the sponsor sees why, the developer sees what, and the auditor sees the controls.
Diagram in words
- BRD: BR-04, remind customers before their policy renews, measured by lapses within 30 days of renewal.
- FRD: FR-04.1 first reminder 30 days before; FR-04.2 second reminder 7 days before; FR-04.3 content; FR-04.4 no reminder for cancelled or renewed policies; FR-04.5 retry up to three times.
- SRS adds: NFR-04.1 sent within two hours of the batch window; NFR-04.2 no medical or payment-card information; NFR-04.3 audit log; INT-04.1 email provider API contract.
What changes in agile teams
Many agile teams do not write a full BRD, FRD and SRS. That does not mean they skip the thinking. The same information is spread across lighter artefacts:
- The BRD's purpose, objectives and scope become a short product vision, a goal for each release and a one-page scope statement.
- The FRD's functions become the backlog of user stories with acceptance criteria.
- Non-functional requirements become constraints and criteria on stories, or part of the definition of done.
- Process models and decisions live in a team wiki. See documentation for business analysts.
However, regulated industries, fixed-price contracts and large integrations often still need formal documents, even when teams build iteratively. In those cases, analysts typically keep the document as a living artefact and update it with each change. The principle is to document what the reader needs to make a decision or take an action, and no more. See also the agile BA and product owner guide.
How to choose and how to avoid common mistakes
Ask four questions before opening a template.
- Who will read it and what will they decide? Sponsors approving funding need a BRD-level view. Developers building need FRD-level detail.
- How regulated or contractual is the work? Audit or contract requirements push towards an SRS and formal control.
- How stable are the requirements? Stable and well understood suits upfront documents; uncertain and evolving suits stories and iteration.
- What does the organisation already use? Follow existing templates unless there is a strong reason not to.
Mistakes to avoid
- Mixing levels. Putting screen details in the BRD or business goals in the FRD confuses both readers.
- Writing solutions as needs. "The system shall use a dropdown" is a design choice, not a business requirement.
- Skipping IDs and traceability. Without IDs you cannot show that each need is built and tested. See the traceability matrix guide.
- Writing and never updating. An outdated document is worse than none.
- Writing it alone. Review with a stakeholder, a developer and a tester.
To practise, use our BRD example and then convert two of its requirements into FRD-style statements. The BA Lab includes requirements tasks that check for vague wording and missing traceability. The distinction between the documents is a small piece of a bigger skill, which you can see in the overview of business analyst skills.
Frequently asked questions
Is a BRD the same as an SRS?
No. A BRD states business needs and objectives for decision makers. An SRS specifies in detail what the software must do and satisfy, for developers, testers and auditors. The SRS follows from the BRD.
Do I need all three documents on every project?
No. The right set depends on the readers, regulation and stability of requirements. Small or agile projects often use a short vision, a backlog of stories and a wiki instead.
Who writes the BRD?
Usually the business analyst, with input from sponsors and business stakeholders, and approval by the sponsor.
What is the difference between FRD and SRS?
An FRD focuses on functions the system provides. An SRS covers those functions and also non-functional requirements, interfaces, data and constraints. Some organisations use the terms almost interchangeably.
Where can I see an example?
Our free BRD example and outline shows a fictional document, and this article shows one requirement written at all three levels.
This article is educational. All companies, people and numbers in the examples are fictional. BA Mentorship does not issue professional certifications and cannot guarantee any job or interview outcome.
Key terms in this article
- BRD (Business Requirements Document)
- FRD (Functional Requirements Document)
- SRS (Software Requirements Specification)
- Business Analyst
- Stakeholder
- Business Requirement
- Business Rule
- Business Case
- SMART Objectives
- Sign-Off
- Functional Requirement
- Wireframe
- Agile
- Non-Functional Requirement
- API (Application Programming Interface)
- Product Vision
- Backlog
- User Story
- Acceptance Criteria
- Definition of Done
- Process Model