10 Important Documents Prepared By Business Analyst

Got the opportunity to work on the first project as a business analyst? Are you wondering about the document prepared by a business analyst? Don’t worry, you are not alone, almost every business analyst goes through this phase. Therefore, I have listed the most common yet important documents that a business analyst has to prepare for a project.

Documents Prepared By Business Analyst

Project documentation is one of the key responsibilities of the business analysts. A business analyst will prepare and manage many documents throughout the project life cycle i.e. starting from the project initiation until the project goes live. You must know the key documents that a business analyst prepares if you want to jump into the business analyst profession.

Top 10 Important Documents Prepared By Business Analyst

This article will list down the 10 important documents prepared by BA however, there could be many more documents that a BA would be preparing and managing. Let’s get started with my list of business analyst documents;

1. Business Case and Project Charter

A business case is a high-level document that is created before initiating the project. It summarizes the project’s objective, vision, benefits, viable options, the risk involved, etc. In a nutshell, you can get the project background by referring to a business case.

Project Charter is also a high-level document that is prepared before the project initiation. It is a very short document and consists of high-level project information, stakeholders, risks involved, and a high-level view of – how the project will be carried out.

These documents are usually prepared by the project managers, however business analysts assist. These two documents act as a formal agreement with the client or business stakeholders.

2. Business Analysis Plan

It is a formal document that describes the key activities to be carried out by the business analyst during the project life-cycle. It is part of a project management plan. The business analysis plan outlines the requirement elicitation, requirements analysis, and validation/verification efforts, etc.

This could be prepared using excel also. It includes all the deliverables that must be completed within time. You need to list down the business analysis techniques, stakeholder groups, estimate the efforts, etc.

Read Also… Do Business Analysts Need To Know Programming? Here’s The Truth

3. Business Requirements Document (BRD)

Business Requirement Document is created during the project analysis phase. It is a well-written and detailed document that describes the business needs and expectations. A BRD is a very critical document and failing to prepare a solid business requirement document can lead to project failure.

This document is focused on “what the system should do?“. It has all the business logic, constraints, assumptions, key stakeholders, etc. Business Analyst prepares a BRD with the help of stakeholders, subject matter experts, business praters. It is written in simple terms without any use of technical jargon.

Each company has its template to draft a business requirement document. Once it is drafted, it has to be reviewed and peer, business analyst, before it goes to the business for approval. A business analyst will have many meetings, brainstorming sessions, and utilize various techniques to gather the requirements and draft them to a BRD.

4. Functional Requirement Specification (FRS)

Business Requirement Documents are written in simple terms without any technical jargon. This document could be referred by anyone and it is easy to follow. However, it is not enough for the development team to understand the complete expectation from the system. Therefore, we need to have a functional requirement specification. This document is required in IT-related projects.

If a Business Requirement Document focuses on “what system should do?” then a functional specification document explains “how the system should behave?“. This document is also called a functional specification document i.e. FSD. A business analyst will list down the system’s input, output, operation, properties, data model, etc.

A business requirement document is mainly built for gathering the functional requirement in a way that is easy for any individual to refer and understand whereas a functional requirement specification is derived from the BRD and focused on the technical requirements of the project.

5. Software Requirement Specification/Document (SRS or SRD)

A Software Requirement Specification or Software Specification Document is required for the software projects. An SRS or SRD describes the complete behavior of the system to be developed. This document consists of functional as well as non-functional requirements that include;

  1. Set of use cases that describe all the interactions that a user will have with the system.
  2. Functionality fo the system
  3. Type of software requirements
  4. Explain the system properties and constraints like response time, database and storage requirements, etc.

6. Visual Documents i.e. Wireframe and Prototype, and Mock-up

It is very important to have a visual representation of the TO-Be system. This helps the business stakeholder to understand the future system and business analyst to understand the client’s expectations. A business analyst draws the blueprint of the system with the help of wireframe design and pass it on to the designers to draw the system prototype.

These diagrams could save a lot of time during the analysis phase and also it helps to stay aligned with stakeholder’s expectations. Wireframe or Prototype or Mock-up diagrams then attached to the requirements which will be then referred by the development team.

7. Use Case Diagrams

Business analysts should be able to create the use cases. Use cases are used on system analysis to identify, define, and organize system requirements. The use cases are the simplest diagram that represents the user’s interaction with the system. It helps in recording the scenarios in which a user will interact with the system.

Use Case Diagram has the following important components;

  1. Use Cases – Set of actions
  2. Actors – End users
  3. Boundary – System’s Scope.
  4. Relationship – between actors and the use cases.

8. Requirement Traceability Matrix (RTM)

An RTM i.e. Requirement Traceability Matrix is a very important document that a business analyst prepares and manages. Requirement traceability matrix is used for mapping and tracking project requirements to the test cases and related defects. This document shouldn’t miss any test cases therefore, it assures all the functionality of the application is covered and tested.

Requirement Traceability Matrix is prepared in excel i.e. in tabular format with the many-to-many relationship between requirements and test scenarios. This document is used through the project life-cycle.

9. Test Cases and UAT

There is testing or QA i.e. Quality Assurance team who performs the system’s testing once it is developed, however in some organizations, the business analysts are responsible for doing the functional testing before UAT.

Moreover, a business analyst assists the business stakeholders or users in completing the user acceptance testing. Therefore, they need to prepare the test case documents that business users can follow to finish the UAT. Business Analyst should list down the scenarios as well as the expected result for the UAT process.

10. Change Management

You will come across many changes in the initially requested business requirements as you progress in project development. The business users request many changes when they see the system or gets hands-on. Sometimes, due to regulatory requirements or business strategy, some changes are required in initially raised requirements.

Any additional requirements after the business requirements are baselined are considered as change requests. Each change request goes through the change management process before it could be added to the project scope.

A business analyst will be responsible for understanding the requested change, analyzing, doing impact analysis, and getting necessary approvals. The change request documents are very critical therefore, it should be captured properly before pushing it to the development team.

There are many other documents that a business analyst prepares and manages.

A business analyst also responsible for scheduling meetings and maintaining the minutes of meetings. They also maintain the requirement issue log to make sure nothing is getting missed during the implementation process. All the email communication and approvals are logged and maintained by the business analysts.

Documents Prepared By Business Analyst

Read Also…

Conclusion

Project Documentation is one of the key tasks that a business analyst has to deliver. There are many documents a business analyst prepares and manages as per the projects demand.

Now, you know the top 10 important documents prepared by a business analyst. Each company has its template to capture the requirements however, the content remains common.

Documentation is not limited to the project analysis phase but it continues till the project is delivered.

I hope you found this article useful and it was able to clarify your doubts related to business analyst documents. Please consider sharing this article with your friends and colleagues. You can also subscribe with your email to get the latest post in your inbox. Don’t worry! we hate spamming. 🙂

Leave a Reply

Top 6 Best Business Analyst Certifications Top 7 Most Wanted Career Paths For The Business Analysts How to become a business analyst without experience