ADD, BRD, FRD, Test Plan & Test Strategy

What is BRD?

BRD (Business Requirement Document) is a document that describes the business needs, goals, and requirements of a project from the client's perspective.

 It explains what the business wants from the system.

BRD is a document that describes the business requirements and objectives of a project from the client’s perspective.

Definition:-

 Purpose of BRD

1️⃣ To define business objectives
2️⃣ To understand client requirements
3️⃣ To provide a clear project scope
4️⃣ To act as a reference for development and testing

Key Contents of BRD

  • Business objectives

  • Project scope

  • Stakeholders

  • High-level requirements

  • Business rules

Example

A bank wants a mobile banking application where customers can:

  • Check account balance

  • Transfer money

  • Pay bills

These business needs are documented in the BRD.

What is FRD?

FRD (Functional Requirement Document) describes how the system should work to meet the business requirements defined in the BRD.

 It focuses on system functionality.

FRD is a document that describes how the system will function to satisfy the business requirements.

Definition:-

Purpose of FRD

1️⃣ To explain system functionality
2️⃣ To convert business requirements into technical details
3️⃣ To guide developers and testers
4️⃣ To define system behavior

 Key Contents of FRD

  • Functional requirements

  • System workflows

  • Input and output details

  • Use cases

  • Business logic

Example

In a banking app:

  • User login functionality

  • Fund transfer process

  • Balance check feature

These detailed system functions are written in the FRD.

 What is Test Plan?

A Test Plan is a document that describes the testing approach, scope, resources, schedule, and activities for a testing project.

 It answers what to test, how to test, and when to test.

A Test Plan is a document that outlines the scope, strategy, resources, and schedule of testing activities.

Definition:-

Purpose of Test Plan

1️⃣ To define testing scope and objectives
2️⃣ To plan testing activities
3️⃣ To allocate resources and timelines
4️⃣ To manage testing risks

 Key Contents of Test Plan

  • Test scope

  • Test objectives

  • Test schedule

  • Test environment

  • Roles and responsibilities

  • Entry and exit criteria

Example

For an E-commerce website, the test plan defines:

  • Testing login and checkout modules

  • Testing timeline

  • Test environment setup

 What is Test Strategy?

A Test Strategy is a high-level document that defines the overall testing approach for a project or organization.

 It explains how testing will be performed across the project.

Test Strategy is a high-level document that defines the overall testing approach and standards for a project.

Definition:-

 Purpose of Test Strategy

1️⃣ To define the overall testing approach
2️⃣ To standardize testing processes
3️⃣ To ensure quality standards
4️⃣ To guide the testing team

Key Contents of Test Strategy

  • Testing approach

  • Testing levels

  • Testing tools

  • Risk management

  • Quality standards

Example

A company decides:

  • Use automation for regression testing

  • Use manual testing for UI testing

These decisions are documented in the Test Strategy.