As a Business Analyst, you would have to create different types of documents based on the task assigned to you.
While some of these documents would be created numerous times such as a functional requirements document, other requirements documents would only have to be created occasionally.
Business analysts use requirements documents to describe the project goals so that all the stakeholders have a shared understanding of what they want to accomplish.
What are the different types of requirements document that a Business Analyst can create ?
There are different types of requirements documents that a Business Analyst might need to create and they include the following:
- Business Requirements Document (BRD): the business requirement document is used to describe the business need and how the organization plans to fulfill that need. The document might include the following information: the project objective, the business need, the budget, the cost-benefit analysis and the solution features.
- Functional Requirements Document (FRD): the functional requirements document is used to describe how the project team plans to fulfil the business need. It explains the business need, functional requirements, current state and future state.
- Product Requirements Document (PRD): the product requirements document is used to describe what would be included in the product. It is very similar to a functional requirements document but it also includes the non functional requirements such as the products reliability, security and scalability.
- Technical Requirements Document (TRD): the technical requirements document is used to describe the software, hardware and environment requirements of the product. This would include details such as the application’s programming language and the operating system would also be included in the document.
- Market Requirements Document (MRD): the marketing requirements document is used to explain the needs of a targeted market segment. It also explains the customers needs, what the product is, what the product requirements are, who the target customers are and what the competitors products are.
- Software Requirements Specification Document (SRSD): the software requirements specification document is used to describe the product’s functional and non-functional requirements.
- Quality Requirements Document (QRD): The quality requirements document describes the functionalities that the customers needs the product to have.
- User Interface Requirements Document (UIRD): A user interface requirements document is used to describes the look and feel of the systems User Interface (UI). It includes information such as the user navigation, user screens and application buttons.