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
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
Principles of Information Systems (MindTap Course List)
13th Edition
ISBN:9781305971776
Author:Ralph Stair, George Reynolds
Publisher:Ralph Stair, George Reynolds
Chapter12: System Acquisition And Development
Section: Chapter Questions
Problem 7SAT: The overall emphasis of the __________ phase is on gathering data on the existing system,...
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
Expert Solution
This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
Step by step
Solved in 2 steps
Recommended textbooks for you
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781305971776
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Fundamentals of Information Systems
Computer Science
ISBN:
9781337097536
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Information Technology Project Management
Computer Science
ISBN:
9781337101356
Author:
Kathy Schwalbe
Publisher:
Cengage Learning
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781305971776
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Fundamentals of Information Systems
Computer Science
ISBN:
9781337097536
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Information Technology Project Management
Computer Science
ISBN:
9781337101356
Author:
Kathy Schwalbe
Publisher:
Cengage Learning
Enhanced Discovering Computers 2017 (Shelly Cashm…
Computer Science
ISBN:
9781305657458
Author:
Misty E. Vermaat, Susan L. Sebok, Steven M. Freund, Mark Frydenberg, Jennifer T. Campbell
Publisher:
Cengage Learning
Management Of Information Security
Computer Science
ISBN:
9781337405713
Author:
WHITMAN, Michael.
Publisher:
Cengage Learning,