5. Business Requirement Document A Business Requirement Document is created to describe the business requirements of a product/process and the intended end result expected from the product/process. It is one of the most widely accepted project requirement documents and is referred to throughout the development life cycle for any project. A BRD mainly focuses on answering 'what is the business solution' as opposed to 'how to achieve the business solution,' and thus, it's primarily centered around the business requirements. A BRD is created with the help of the project team (BA, client, subject matter experts, and business partners). It is also a communication tool for other stakeholders/external service providers. The Business Requirement Document contains the following sections: - Project Background - Business goals and objectives - Stakeholders - Requirement scope - Functional requirements - Data requirements - Non-functional requirements - Interface requirements - Business glossary/Definitions -Dependencies of existing systems - Assumptions 7. Functional requirement specification (FRS)/ Functional Specification Document (FSD) A Functional requirement specification or Functional Specification Document describes the intended behavior of a system, including data, operations, input, output, and the prop- erties of the system. In a BRD, the requirements are high-level, but in an FRS/FSD, they are written in much more detail to capture each and every aspect of a requirement. Thus a functional specifi- cation document becomes a more technical, accurate, and descriptive requirement document. Owing to their technical nature, FRS/FSD are equally used by developers, testers, and the business stakeholders of a project. The Functional requirement specification (FRS)/Functional Specification Document (FSD) contains the following: - Product Context - Assumptions - Constraints - Dependencies - Functional Requirements - User Interface Requirements - Usability - Performance - Manageability/Maintainability - System Interface/Integration - Security - Requirements Confirmation/sign-off

Database System Concepts
7th Edition
ISBN:9780078022159
Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Chapter1: Introduction
Section: Chapter Questions
Problem 1PE
icon
Related questions
Question
 
 
 
  • What are the main differences between a BRD and FSD? What elements make them different from each other?
  • Do you think BRD and FSD differs for an agile development methods 
 
 
 
 
 
5. Business Requirement Document
A Business Requirement Document is created to describe the business requirements of a
product/process and the intended end result expected from the product/process. It is one
of the most widely accepted project requirement documents and is referred to throughout
the development life cycle for any project.
A BRD mainly focuses on answering 'what is the business solution' as opposed to 'how to
achieve the business solution,' and thus, it's primarily centered around the business
requirements.
A BRD is created with the help of the project team (BA, client, subject matter experts, and
business partners). It is also a communication tool for other stakeholders/external service
providers.
The Business Requirement Document contains the following sections:
- Project Background
- Business goals and objectives
- Stakeholders
- Requirement scope
- Functional requirements
- Data requirements
- Non-functional requirements
- Interface requirements
- Business glossary/Definitions
-Dependencies of existing systems
- Assumptions
Transcribed Image Text:5. Business Requirement Document A Business Requirement Document is created to describe the business requirements of a product/process and the intended end result expected from the product/process. It is one of the most widely accepted project requirement documents and is referred to throughout the development life cycle for any project. A BRD mainly focuses on answering 'what is the business solution' as opposed to 'how to achieve the business solution,' and thus, it's primarily centered around the business requirements. A BRD is created with the help of the project team (BA, client, subject matter experts, and business partners). It is also a communication tool for other stakeholders/external service providers. The Business Requirement Document contains the following sections: - Project Background - Business goals and objectives - Stakeholders - Requirement scope - Functional requirements - Data requirements - Non-functional requirements - Interface requirements - Business glossary/Definitions -Dependencies of existing systems - Assumptions
7. Functional requirement specification (FRS)/ Functional Specification
Document (FSD)
A Functional requirement specification or Functional Specification Document describes
the intended behavior of a system, including data, operations, input, output, and the prop-
erties of the system.
In a BRD, the requirements are high-level, but in an FRS/FSD, they are written in much
more detail to capture each and every aspect of a requirement. Thus a functional specifi-
cation document becomes a more technical, accurate, and descriptive requirement
document.
Owing to their technical nature, FRS/FSD are equally used by developers, testers, and
the business stakeholders of a project.
The Functional requirement specification (FRS)/Functional Specification Document (FSD)
contains the following:
- Product Context
- Assumptions
- Constraints
- Dependencies
- Functional Requirements
- User Interface Requirements
- Usability
- Performance
- Manageability/Maintainability
- System Interface/Integration
- Security
-
Requirements Confirmation/sign-off
Transcribed Image Text:7. Functional requirement specification (FRS)/ Functional Specification Document (FSD) A Functional requirement specification or Functional Specification Document describes the intended behavior of a system, including data, operations, input, output, and the prop- erties of the system. In a BRD, the requirements are high-level, but in an FRS/FSD, they are written in much more detail to capture each and every aspect of a requirement. Thus a functional specifi- cation document becomes a more technical, accurate, and descriptive requirement document. Owing to their technical nature, FRS/FSD are equally used by developers, testers, and the business stakeholders of a project. The Functional requirement specification (FRS)/Functional Specification Document (FSD) contains the following: - Product Context - Assumptions - Constraints - Dependencies - Functional Requirements - User Interface Requirements - Usability - Performance - Manageability/Maintainability - System Interface/Integration - Security - Requirements Confirmation/sign-off
Expert Solution
steps

Step by step

Solved in 2 steps

Blurred answer
Similar questions
Recommended textbooks for you
Database System Concepts
Database System Concepts
Computer Science
ISBN:
9780078022159
Author:
Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:
McGraw-Hill Education
Starting Out with Python (4th Edition)
Starting Out with Python (4th Edition)
Computer Science
ISBN:
9780134444321
Author:
Tony Gaddis
Publisher:
PEARSON
Digital Fundamentals (11th Edition)
Digital Fundamentals (11th Edition)
Computer Science
ISBN:
9780132737968
Author:
Thomas L. Floyd
Publisher:
PEARSON
C How to Program (8th Edition)
C How to Program (8th Edition)
Computer Science
ISBN:
9780133976892
Author:
Paul J. Deitel, Harvey Deitel
Publisher:
PEARSON
Database Systems: Design, Implementation, & Manag…
Database Systems: Design, Implementation, & Manag…
Computer Science
ISBN:
9781337627900
Author:
Carlos Coronel, Steven Morris
Publisher:
Cengage Learning
Programmable Logic Controllers
Programmable Logic Controllers
Computer Science
ISBN:
9780073373843
Author:
Frank D. Petruzella
Publisher:
McGraw-Hill Education