Author Topic: Business Analyst delivered documents.  (Read 10437 times)

Mahesh27

  • Global Moderator
  • Newbie
  • *****
  • Posts: 4
Business Analyst delivered documents.
« on: May 19, 2016, 05:02:04 pm »
Here are the list of few documents that a BA is expected to deliver:
Business Case
BRD-Business Requirement Document
FRS/FS-Functional Specs
SRS-Software Requirement Specification
Test Cases
User Stories
User Manuals
RTM-Requirement Traceability Matrix

MadhaviL

  • Global Moderator
  • Newbie
  • *****
  • Posts: 12
Re: Business Analyst delivered documents.
« Reply #1 on: May 19, 2016, 09:19:36 pm »
Documentation is one of the integral job functions of a business analyst and he, throughout the course of a project, prepares many documents. These documents are created to fulfill the varied project needs and cater to audiences belonging to different spheres of a project.
The type and specifications a business analyst is expected to create in an organization depends upon many parameters like organization’s processes and policies, need 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. The documents are:

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

170416102

  • Global Moderator
  • Newbie
  • *****
  • Posts: 13
Re: Business Analyst delivered documents.
« Reply #2 on: April 19, 2017, 06:13:56 pm »
Documents are required to capture details at every stage of SDLC and forms an important liaison to understand the process and service/product.
From the project initiation to project closure, a BA is required to deliver the below documents:
1. BRD
2. SRS
3. FRD
4. RTM
5. Test Plan(not mandatory and can be taken care by Testers)
6. Test Case Document(not mandatory and can be taken care by Testers)
7. User Manual

YeswanthPM

  • Global Moderator
  • Newbie
  • *****
  • Posts: 3
Re: Business Analyst delivered documents.
« Reply #3 on: June 01, 2017, 01:28:42 pm »
Documents useful to business analyst can be many things in many formats, from actual printed documents to printouts of screenshots to websites and blogs containing company and department information.
Documents like BRD,FRD,SRS,
In this documents they will use like REPORTS, LETTERS, AND BROCHURES
WEBSITES
SCREENLAYOUT'S etc....

Jaishree Singh

  • Global Moderator
  • Newbie
  • *****
  • Posts: 2
Re: Business Analyst delivered documents.
« Reply #4 on: June 20, 2017, 05:50:02 pm »
Documents prepared by business analyst during SDLC are - 

1) BRD
2) FRD
3) SRS
4) RTM
5) Test cases   

170422303

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Business Analyst delivered documents.
« Reply #5 on: July 02, 2017, 12:49:42 pm »
BUSINESS ANALYST deliverable's in a project are:
*) Project Charter/vision
    Project Vision or Project Charter is a very high-level document which describes the purpose of the project and what value it will add to
    the business i.e. business objective to be achieved by the project.

*) Requirement Project Plan
    This document is created at planning phase of the project and it contains all the information about the project to manage the project
    from start to end. This documents describes, who is responsible for what.

*) Use Cases:
    Use case analysis provides an overview of business goals without knowing the system requirements in detail, hence easy to
    understand. It’s always the best practice to create use case to gather and track the business requirement.

*) Wire-frames, prototypes, mock-ups and other visual documents:
     Business Analyst often asked to create a prototype or mock-up screen to gather functional or business process requirements. It’s
     easy for stakeholders to view what they will be getting before approving it. A well-drawn mockup screens can save a lot of your time
     in the analysis phase.
 
*) User Stories in Agile project:
     In the agile development environment, User Stories are the functionalities written in user’s point of view which business should
     provide. The user stories are not very descriptive and only captures ‘who’, ‘what’ and ‘why’ of a requirement in limited detail.

*) Business Requirement Document (BRD):
    This document describes the reasons why a project has been initiated, the objectives that the project will achieves. BRD describes
    the need of the organization as a whole.

*) Functional Requirement Specification (FRS):
     A Functional requirement specification or Functional Specification Document describes the intended behavior of a system including
     data, operations, input, output and the properties of the system. Fictional requirement document or specification is written more
     technical than Business requirement document. If BRD describes “what” needs to be some then FRD/FRS describes “how” it should
     be done. This document is referred to development and testing team as it has more insight of the system, input, output, processes,
     operations, system’s property etc.

*) Requirement Trace-ability Matrix (RTM):
    The Requirement Traceability Matrix (RTM) is a document that links requirements throughout the validation process. The purpose of
    the Requirements Traceability Matrix is to ensure that all requirements defined for a system are tested in the test protocols.
    It is maintained in excel sheet by listing each requirement and corresponding test case numbers. Each organization has their own
    template for Requirement Traceability Matrix. This is used throughout the project life cycle to manage the agreed requirements.

*) Test Cases:
    Business analysts contribute in preparing test cases with Testers and sometimes they test the functional testing by referring the test
    cases. It’s important for a Business Analyst to have some basic idea of test cases i.e. how it’s prepared? What are the key elements?
    Etc.

*) System Requirement specification Document (SRS):
    A Software Requirements Specification (SRS) is a description of a software system to be developed. It lays out functional and non-
    functional requirements, and may include a set of use cases that describe user interactions that the software must provide. This
    document elaborates the requirements from the perspective of observational behavior.

171525904

  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: Business Analyst delivered documents.
« Reply #6 on: July 04, 2017, 12:15:45 pm »
Business Analyst delivered documents vary from project to project and organization to organization and based many other factors.Not necessarily all the organization or projects contain same amount of documents.below are the few standard documents delivered by business analyst.

1)Business analysis planing document
2)BRD (Business requirement document)
2)FRD (Functional requirement document)
3)SRS (system/ solution requirement document)
4)RTM (requirement Tracking tractability).
5)End user manual
6)Test case specification document
7)UAT (user acceptance testing document)
8)Project closure document

172031605

  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: Business Analyst delivered documents.
« Reply #7 on: August 02, 2017, 04:38:32 pm »
The type and specifications a business analyst is expected to create in an organization depends upon many parameters like organization’s processes and policies, need 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. The documents are:

    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

Pranjal Dutta

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Business Analyst delivered documents.
« Reply #8 on: September 01, 2017, 01:41:24 pm »
Document preparation is the essential KRA (Key Responsibility Area) of any Business Analyst’s job profile. BA prepares and maintains many documents throughout the given Project Life Cycle.
a) Business Requirement Document (BRD): Here BA defines the Project Scope, Objective, Business Rules and in short it describe the need of the Organization as a whole.
b) Functional Requirement Document (FRD): BA defines functional requirements of the proposed system. This is useful for Developer and tester.
c) System Requirement Specification Document (SRS): It defines the whole system requirement and contains both Functional and Technical requirement specification. This is useful for Developer, Tester and System Design and Architecture.
d) Use Case Description Document: This document describes how the user(s) interacts with the system.
e) Requirement Traceability Matrix (RTM): This document was maintained by BA to keep track of the progress of the project in every stage of the Product development life cycle.
f) Acceptance Testing Document: BA prepares this test case script to do the final Testing with client before the sign-off the Client Acceptance Form.
g) User Manual: BA prepares the User Manual throughout the whole Project Life Cycle for the System User(s).

1170220109

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Business Analyst delivered documents.
« Reply #9 on: October 18, 2017, 05:40:30 pm »
The list of documents that are delivered by Business Analyst are:
1. Project vision document
Although mainly the client/project manager creates a project vision document, business analyst are also expected to contribute to this document. A Project vision document entails the purpose and intent of the product/software to be developed and describes on a high level ‘what’ business objective will be achieved.
1)The Project vision document contains:
– Introduction
– 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 till 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 towards defining requirements
– Approach towards Requirements Traceability
– Workflows and Activities
– Change Management
 
3. Use cases
Each and every project is an endeavor to achieve ‘requirements’ and the document which defines these requirements is a use case. A use case is a methodology 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
 
4. User stories
In agile development environment, a user story is a document describing the functionality a business system should provide and are written from the perspective of an end user/customer/client. The user stories are not very descriptive and only captures ‘who’, ‘what’ and ‘why’ of a requirement in limited detail. If any requirement is too big for 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 story 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 login credentials of the user and redirect him to the dashboard in case of 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 expected from the product/process. It is one of the most widely accepted project requirement document and is referred throughout the development life-cycle for any project.
A BRD mainly focusses on answering ‘what is the business solution’ as opposed to ‘how to achieve the business solution’ and thus it’s mainly centered around the business requirements. A BRD is created with the help of the project team (BA, client, subject matter exerts, business partners) and is also used as a communication tool 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, development, testing and release of the project/product. This is done by maintaining an excel sheet which lists the complete user and system requirements for the system (in form of use cases) which are in-turn mapped to the respective documents like Functional Requirement, Design Document, Software Module, Test Case Number, etc.
A 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, operations, input, output and the properties of the system.
In a BRD the requirements are high level but in a FRS/FSD they are written in much more details to capture each and every aspect of a requirement. 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 and behavioral requirements of the system. This document elaborates 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 but they must understand what they constitute and how to create one, as they 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 particular piece of functionality is behaving as intended (or as documented in the requirement documentation). Thus, a test case becomes a standardized document which should be referred 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 referred through the project’s life-cycle for communication, reference and revision.

VIJAY POGULA

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Business Analyst delivered documents.
« Reply #10 on: December 11, 2017, 11:45:33 am »
Documents are used to capture the project progress and status in SDLC. Below are the few documents which you can find in a software development project.
 * Business Case
 * Stakeholder document
 * Business requirements document (BRD)
 * user requirements document (URD)
 * Functional requirements document (FRD)
 * Supplementary specification document (SSD)
 * Software requirements specifications (SRS)
 * Requirements traceability matrix (RTM)
 * High level design document (HDD)
 * Application design document (ADD)
 * Checklists
 * Test strategy and test plan
 * Client acceptance forms
 * User manuals
 * Project closure document
 * Change request log and Change tracker (CT)

1171921109

  • Global Moderator
  • Newbie
  • *****
  • Posts: 12
Re: Business Analyst delivered documents.
« Reply #11 on: January 21, 2018, 09:49:28 pm »
Business Analyst delivered documents.

Each of these documents has a specific template and it’s a part of the overall project documentation. The documents are:

1) Project vision Document
2) Requirement Management Plan
3) User stories
4) Use cases
5) Business Requirement Document
6) Requirement traceability matrix (RTM)
7) Functional requirement specification (FRS)/ Functional Specification Document (FSD)
8) System requirement specification (SRS)/ System Requirement Document (SRD)
9) Test case

1171948312

  • Global Moderator
  • Newbie
  • *****
  • Posts: 34
Re: Business Analyst delivered documents.
« Reply #12 on: February 13, 2018, 07:19:57 pm »
BA submit documents according to the client requirement and project requirement. Here I am mentioning few documents, they are:-
1.Business case
2.BRD-Business Requirement Document
3.FRS-Functional Requirement Specification
4.SRS- System Requirement specification
5.FRD-Functional Requirement Document
6.Test case
7.UAT
8.Sign off Document
9.MOM-Minutes of Meeting
10.Understanding Document.

1170944412

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Business Analyst delivered documents.
« Reply #13 on: March 10, 2018, 01:02:30 pm »
Documentation is an integral part of Business analyst’s job and there are several documents that they will prepare throughout the project. The number of documents delivered can vary with organisation, but a few common ones are mentioned below
o   Project plan/Project vision document
o   Requirement management plan document
o   Use case description document
o   Visual documents such as Wireframes, prototype or mockup etc.
o   User stories in Agile project
o   Business requirement document (BRD)
o   Functional requirement document (FRD)
o   Software requirement specification document (SRS)
o   Requirement traceability Matrix (RTM)
o   Test cases

Nitin John

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Business Analyst delivered documents.
« Reply #14 on: March 10, 2018, 02:29:44 pm »
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. The documents are:

•   Project vision Document
            Project Vision or Project Charter is a very high-level document which describes the purpose of the project and what value it will add to the business i.e. business objective to be achieved by the project. Generally, it is prepared by the project manager but Business analyst needs to contribute in this document.

•   Requirement Management Plan
            This document is created at planning phase of the project and it contains all the information about the project to manage the project from start to end. It’s a plan that outlines the elicitation, requirements analysis, and validation/verification efforts as well as clearly indicates who is responsible for what. This document is referred to Project Manager, Project Lead, Project Sponsor or any member who needs to be involved in project life cycle.

•   User stories
      In the agile development environment, User Stories are the functionalities written in user’s point of view which business should provide. The user stories are not very descriptive and only captures ‘who’, ‘what’ and ‘why’ of a requirement in limited detail.
•   Use cases
      A use case is a methodology used in system analysis to identify, define and organize system requirements. A use case is created from the perspective of a user. This also helps to identify the key stakeholders of the process. This is again high-level document and it shows all end users and major processes and how they interact with each other.

•   Business Requirement Document (BRD):-
         Here BA defines the Project Scope, Objective, and Business Rules and in short it describe the need of the Organization as a whole.

•   Requirement traceability matrix (RTM)
            This document was maintained by BA to keep track of the progress of    the project in every stage of the Product development life cycle.

•   Functional requirement specification (FRS)/ Functional Requirement Document (FRD)
         BA defines functional requirements of the proposed system

•   System requirement specification (SRS)/ System Requirement Document (SRD)
      It defines the whole system requirement and contains both Functional and Technical requirement specification.
•   Test case
      BA prepares this test case script to do the final Testing with client before the sign-off the Client Acceptance Form
•   User Manual:
         BA prepares the User Manual throughout the whole Project Life Cycle for the System User(s).