Business Analysis Essential Documents

24/11/22, 17:00 9 important Documents created by every Business Analyst | The Business Analyst Job Description
Job Description Roles What is Analysis ? Documents Skills Salary Interview Certification Resume
9 Important Documents Created by Every Business Analyst
Documentation is one of the integral job functions of business analysts, and they, throughout the course of a project, prepare many documents.
These documents are created to fulfill the varied project needs and cater to audiences belonging to different spheres of a project.
PSST… Don’t forget to download your FREE Business Analyst Documents Template Toolkit at the end of this article !!
The type and specifications a business analyst is expected to create in an organization depend upon many parameters like the organization’s p
cesses and policies, the needs and expectations of the business, and the stakeholder requirements.
Detailed below are the common documents a business analyst is expected to create, and they are extensively used throughout the course of a
project. Each of these documents has a specific template, and it’s a part of the overall project documentation.
Here are the key documents prepared by Business Analyst (BA):
Project Vision Document

Requirement Management Plan
User Stories
Use Cases
Business Requirement Document
Requirement Traceability Matrix (RTM)
Functional Requirement Specification (FRS)/ Functional Specification Document (FSD)
System Requirement Specification (SRS)/ System Requirement Document (SRD)
Test Case
Let’s discuss each of these documents in detail.
1. Project Vision Document
Although mainly the client/project manager creates a project vision document, business analysts are also expected to contribute to this docume
Project vision document entails the purpose and intent of the product/software to be developed and describes ‘what’ business objective will be
achieved on a high level.
The Project vision document contains:
– Introduction
https://thebusinessanalystjobdescription.com/documents-created-by-a-business-analyst/ 1/8
– Description of users in the system
– Project stakeholders
– Product Overview
– Product Features
– Product requirements
– Constraints/Limitations
– Quality/documentation requirements
2. Requirement Management Plan
The Requirements Management plan is used to document the necessary information required to effectively manage project requirements from
project initiation to delivery.
The Requirements Management Plan is created during the Planning Phase of the project. Its intended audience is the project manager, project
team, project sponsor, and any senior leaders whose support is needed to carry out the plan.
The Requirement Management Plan contains:
– Purpose of plan
– Responsibility assignment
– Tools and procedures to be used
– Approach to defining requirements
– Approach toward Requirements Traceability
– Workflows and Activities
– Change Management
3. Use cases
Each project is an endeavor to achieve ‘requirements,’ and the document that defines these requirements is a use case. A use case is a metho
ogy used in system analysis to identify, define, and organize system requirements.
A use case is created from the perspective of a user and achieves the following objectives:
1. Organizes the functional requirements,
2. Iterative in nature and updated throughout the project life-cycle
3. Records scenarios in which a user will interact with the system
4. Defines other aspects like negative flows, UI elements, exceptions, etc..
The Use Case document contains:
– Actors
– Description
– Trigger
– Preconditions
– Normal Flow
– Alternative Flows
– Exceptions
– Special Requirements
– Assumptions
– Notes and Issues
Also View: 60+ Business Analyst Interview Question and Answers – Download PDF
4. User stories
In an agile development environment, a user story is a document describing the functionality a business system should provide and is written fr
the perspective of an end-user/customer/client.
The user stories are not very descriptive and only capture ‘who’, ‘what’, and ‘why’ of a requirement in limited detail. If any requirement is too big
a single user story, it’s broken down into a number of user stories making it easier for estimation and discussion. In such cases, the main user s
will act as an Epic (parent) user story.
Some examples of user stories are:
– The system shall be able to sort the values in ascending and descending order
– The application must allow the user to enter his name, date of birth, and address.
– The system shall verify the user’s login credentials and redirect him to the dashboard in case of a successful login.
5. Business Requirement Document
A Business Requirement Document is created to describe the business requirements of a product/process and the intended end result that is e
pected from the product/process. It is one of the most widely accepted project requirement documents and is referred to throughout the develop
ment 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 mainly c
tered around the business requirements.
A BRD is created with the help of the project team (BA, client, subject matter experts, business partners) and is also used as a communication
for other stakeholders/external service providers.
The Business Requirement Document contains:

– 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
6. Requirement traceability matrix (RTM)
A Requirement traceability matrix is used to record and track the relationship of the project requirements to the design, documentation, develop
ment, testing, and release of the project/product. This is done by maintaining an excel sheet that lists the complete user and system requiremen
for the system (in the form of use cases), which are in turn mapped to the respective documents like Functional Requirement, Design Documen
Software Module, Test Case Number, etc.
An RTM is maintained throughout the lifecycle of the various releases in a project, and it’s a vital document to track project scope, requirements
and changes in any project.
The Business Requirement Document contains:

– Requirement ID
– Requirement Description
– Functional Requirement
– Status
– Architectural/Design Document
– Technical Specification
– Software Module
– Test Case Number
– Tested In
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, opera
tions, input, output, and the properties of the system.
In a BRD, the requirements are high level, but in an FRS/FSD, they are written in many more details to capture each and every aspect of a requ
ment. Thus a functional specification 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:
– Product Context
– Assumptions
– Constraints
– Dependencies
– Functional Requirements
– User Interface Requirements
– Usability
– Performance
– Manageability/Maintainability
– System Interface/Integration
– Security
– Requirements Confirmation/sign-off
8. System requirement specification (SRS)/ System Requirement Document (SRD)
A detailed document containing information about ‘how’ the complete system has to function and enumerates hardware, software, functional an
behavioral requirements of the system.
SRS/BRD elaborates on the requirements from the perspective of observational behavior only and doesn’t consider technical or design bias.
The System requirement specification (SRS)/ System Requirement Document (SRD) contains:
– Product Perspective
– Product Functions
– User Characteristics
– General Constraints
– Assumptions and Dependencies
– External Interface Requirements
– Functional Requirements
– Classes / Objects
– Non-Functional Requirements
– Inverse Requirements
– Design Constraints
– Sequence Diagrams
– Data Flow Diagrams (DFD)
– State-Transition Diagrams (STD)
– Change Management Process
9. Test case
Although Business analysts are not explicitly asked to create test cases, they must understand what they constitute and how to create one, as t
sometimes have to test functionalities by referring to the test cases.
A test case is a document, which has a set of test data, preconditions, variables, and expected results created to verify and validate whether a
ticular piece of functionality is behaving as intended (or as documented in the requirement documentation). Thus, a test case becomes a stand
ized document that should be referred to every time a requirement has to undergo testing.
The components of a test case are:
– Test Case ID
– Test Scenario
– Prerequisite
– Test Data
– Test Steps
– Expected Results
– Actual Result
– Status
– Remarks
– Test Environment
All the above documents are created by a business analyst and are part of the project/product documentation. These documents are constantly
ferred through the project’s life cycle for communication, reference, and revision.
Download BA Documents Template Toolkit (for Free)!!
Our free Template Toolkit contains the following pre-formatted and professional Business Analyst Document templates:
Use Case Document Template

Requirement Traceability Matrix (RTM) Template
Requirement Management Plan Template
Project Vision Document Template
Test Case Template
FREE TOOLKIT
BA Documents Template Toolkit
Just enter your details in the form below and have the
Toolkit delivered to your Inbox:
Name
Email
Email Me!
ALSO ON THE BUSINESS ANALYST JOB DESCRIPTION
Most Asked Business 9 Quick Tips to BRD v

Analyst Interview … improve … Detail
8 years ago • 6 comments 5 years ago • 1 comment 4 years
We have consolidated In this post, we shall look at In this

several (60+) frequently some of the most basic d
asked Business Analyst … efficacious, yet actionable … BRD, S
Sponsored
20-piece Signature Cast Iron Cookware-Only $19.99 today

Shobing-Online Clearance Store Shop Now
Jennifer Grey Is Probably The Most Beautiful 61 Year Old Woman

News Sharper
Respira profundo antes de ver la cuenta de Marc Anthony

Protagonista
En 2010 las nombraron las gemelas más bellas del planeta, ahora son así
Dailyforest
Maribel Guardia, de 63 años, sin maquillaje, nos dejó sin palabras

Paperela
Clasificamos los países con las mujeres más bellas, quién es el número 1
Oceandraw
2 Comments 
1
Join the discussion…
LOG IN WITH
OR SIGN UP WITH DISQUS ?
Name
Sort by Best  26 ⥅
Shereen Samuel • 5 years ago

Hello there,
Thanks for the good link and the valuable set of

documents - I happened to see your website today
while searching something related to Business
Analysis. As you rightly mentioned that the set of
document a Business Analyst need to work on/be
exposed to would differ based on the company
structure you work with. I have worked with Service
companies and directly with established European
Banks and I must say the way my work differed a lot
when I try to compare between them. Former hardly
focused on documents and wanted the end product
more, hence the template or documents just a little.
On the other hand in the Bank we had documents for
each and every step starting from project initiation
phase till hand over to the implementation team.
Quality in terms of each work product – whether its
document or code mattered a lot here.
see more
3△ ▽ • Reply • Share ›
Sajal Gupta • 5 years ago

very good material ........
△ ▽1 R l Sh
Sponsored
20-piece Signature Cast Iron Cookware-Only $19.99 today-Make it easy to make any cuisine!
Shobing-Online Clearance Store
Trabajadores encuentran serpiente gigante - No creerás lo que tenía adentro

Dailyforest
Thalía desmaquillada es probablemente la mujer más bella del momento

Oceandraw
Ciudad Ojeda: Government Fund Money That You Don't Have To Repay
Government Grants | Search Ads
Ella era hermosa, hoy luce irreconocible

Horizontimes
10 alimentos que destapan las arterias (la mayoría de la gente ignora)

Vitaminews

Business Analysis Essential Documents

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Business Analysis Essential Documents

Uploaded by

Copyright:

Available Formats

24/11/22, 17:00 9 important Documents created by every Business Analyst | The Business Analyst Job Description

9 Important Documents Created by Every Business Analyst

Here are the key documents prepared by Business Analyst (BA):

Project Vision Document

Let’s discuss each of these documents in detail.

1. Project Vision Document

The Project vision document contains:

– Description of users in the system

2. Requirement Management Plan

The Requirement Management Plan contains:

– Tools and procedures to be used

– Approach to defining requirements

– Approach toward Requirements Traceability

– Workflows and Activities

1. Organizes the functional requirements,

2. Iterative in nature and updated throughout the project life-cycle

3. Records scenarios in which a user will interact with the system

4. Defines other aspects like negative flows, UI elements, exceptions, etc..

The Use Case document contains:

– Notes and Issues

Some examples of user stories are:

5. Business Requirement Document

The Business Requirement Document contains:

– Business goals and objectives

– Dependencies of existing systems

6. Requirement traceability matrix (RTM)

The Business Requirement Document contains:

– Test Case Number

7. Functional requirement specification (FRS)/ Functional Specification Document (FSD)

The Functional requirement specification (FRS)/Functional Specification Document (FSD) contains:

– User Interface Requirements

8. System requirement specification (SRS)/ System Requirement Document (SRD)

– Assumptions and Dependencies

– External Interface Requirements

– Data Flow Diagrams (DFD)

– State-Transition Diagrams (STD)

– Change Management Process

The components of a test case are:

Download BA Documents Template Toolkit (for Free)!!

Use Case Document Template

BA Documents Template Toolkit

ALSO ON THE BUSINESS ANALYST JOB DESCRIPTION

Most Asked Business 9 Quick Tips to BRD v

We have consolidated In this post, we shall look at In this

20-piece Signature Cast Iron Cookware-Only $19.99 today

Jennifer Grey Is Probably The Most Beautiful 61 Year Old Woman

Respira profundo antes de ver la cuenta de Marc Anthony

Maribel Guardia, de 63 años, sin maquillaje, nos dejó sin palabras

Join the discussion…

OR SIGN UP WITH DISQUS ?

Shereen Samuel • 5 years ago

Thanks for the good link and the valuable set of

Sajal Gupta • 5 years ago

Trabajadores encuentran serpiente gigante - No creerás lo que tenía adentro

Thalía desmaquillada es probablemente la mujer más bella del momento

Ella era hermosa, hoy luce irreconocible

10 alimentos que destapan las arterias (la mayoría de la gente ignora)

You might also like