COEPD – Center of Excellence for Professional Development Happy Learning
BRD – Business Requirement Document
Business requirements are gathered by business analyst. Business analysts also study AS-IS process to convert into TO-BE process.
BRD also acts as an agreement document between business and delivery team assigned. BRD can be used as a reference document for the business requirements, if anyone wants to refer the business requirements of a project they can refer to one single document of BRD to communicate between different stakeholders regarding the project. BRD includes, Business context, scope and background. Success factors for a future state, Logical data model and data flow diagrams to illustrate how data flows through the information system.
In BRD, we follow different processes such as:
RACI Chart
In BRD, we describe the risks. A risk is something which can affect the success or failure of the project. We have to analyse risks regularly as progress in the project. While we cannot be able to avoid every risk, but we can limit each risk’s impact by being well prepared to face it beforehand only. For each risk, we have to check the probability of its occurrence, project cost and the strategy to handle risk. Strategies include the following:
Avoid: We have to eliminate the risk.
Mitigate: If risk materializes we have to reduce the damage.
Transfer: We have to pass the risk to another entity.
Accept: We have to accept the consequences and do nothing about the risk.
“Risk Analysis” describes new technological issues that could hamper the project.
“Risk Analysis” describes the risk of staff who did not get required expertise for the project.
“Risk Analysis” not getting political forces that could concern or influence the project.
“Risk Analysis” describes the implications of business if the project is called off.
“Risk Analysis” describes the risk that requirement are not specified according to the project. Requirements are not calculated in a proper manner for the project.
In this “Risk Analysis” the risks other than the above mentioned will arise (external risks).
FRD – Functional Requirement Document
FRD is also known as FRS and FS
FRS – Functional Requirement Specification
FS – Functional Specification
FRD document is created from the perspective of end user and describes how the user interface through which an end user can interact with the software. FRD is usually prepared by the business system analyst and this document is verified by the project manager.
In FRS there are two types of requirements they are:-
1.Functional requirements:-
It’s the behaviour and information that the solution will manage, describe capabilities of the system that can be performed in terms of operations this means specific information technology application action or response.
Non-functional requirements:-
The conditions that do not directly link to the behaviour or functionality of the solution, but rather describe environmental conditions under which the solution must remain effective or qualities that the system must have. Mostly these requirements combine the capacity, speed security, availability and the information of architecture and presentation of the user interface
Functional requirement document defines how the system will accomplish the requirements by outlining the functionality and features that will be supported by the system. This gives the testers and developers more understanding in making development and design decisions about the physical design of the system.
We usually describe the FRD through the wireframe diagrams that is through the Use case diagram, sequence diagram and the Activity Diagram.
