Scribd
Upload
58 views

Business Analysis Project Report: Group No

The document provides a template for a business analysis project report on analyzing and improving a claims process. It outlines sections for describing the current ("As Is") process, identifying requirements and opportunities for automation, proposing an improved ("To Be") process, developing use cases and interaction diagrams, prioritizing use cases, defining user acceptance test scenarios, and creating data flow diagrams to map the information flows. The template is designed to guide a thorough analysis and documentation of the "As Is" process, proposed improvements, and testing plans.

Uploaded by

UjjwalBansal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
58 views

Business Analysis Project Report: Group No

The document provides a template for a business analysis project report on analyzing and improving a claims process. It outlines sections for describing the current ("As Is") process, identifying requirements and opportunities for automation, proposing an improved ("To Be") process, developing use cases and interaction diagrams, prioritizing use cases, defining user acceptance test scenarios, and creating data flow diagrams to map the information flows. The template is designed to guide a thorough analysis and documentation of the "As Is" process, proposed improvements, and testing plans.

Uploaded by

UjjwalBansal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Team details

BUSINESS ANALYSIS
PROJECT REPORT
Group No :
1 Table of Contents
1 Executive Summary of the project
<Describe the project in brief)

2 Analysis Phase
2.1 As Is process (Swimlane flow)
<Describe the current flow of the claims process)

2.1.1 Missing Requirements/Redundant requirements


<Describe the missing requirements/redundant requirements/any other problems identified from the
above flow>

2.1.2 Understanding of Ambiguous requirements


Business SMART Observations Modified Requirement Assumptions and
Requirement(each for the requirement (after fixing problems rationale behind
sentence in the claims identified through assumptions
case could be a SMART)
requirement)

2.1.1 Steps to be automated in the current process in 2.1.1

3 To Be Process ((Swimlane flow)


<Provide different color coding for the processes changed/automated and
new processes added)

4 Use case Interaction diagram


<describe the interaction among all the functionalities and use the include and Extends concepts
wherever applicable>

5 Use case design


<describe the use cases derived based on the To be Process. Follow the template for use case used in
the class. It is important to include the system behavior and also the business rules have to be addressed
in the use case design for each of the step. Data required for each step in the use case need to captured.
The non functional requirements should be captured for each use case>
6 Prioritization of the usecases (interms of criticality – High meium-
Low)

7 User acceptance test scenarios


7.1 Usecase scenarios and the corresponding UAT scenarios
<Provide user acceptance test scenarios for each of the scenario in each use case>

Usecase Usecase scenario User acceptance test scenario

7.2 User acceptance test scenarios


<describe user acceptance test scenarios as identified in the above table using the User acceptance test
case template>

8 Data Flow Diagrams (follow the rules for creating DFDs)


8.1 Context Diagram
<create a context diagram by identifying the external entities and the interaction between the external
entities and the claims system)

8.2 Level 0 Data flow diagram (Logical DFD)


<create the level 0 DFD by identifying the high level processes and describe the data flow among them>

You might also like