Business Analysis: Work Breakdown Structure, Design, and RFT Report

This business analysis report provides a detailed overview of a project's work breakdown structure, illustrating how the project is divided into smaller, manageable components and managed by a team. It includes a 'TO-BE' design activity diagram, contrasting the current 'AS-IS' state with the future desired state, highlighting improvements like registration and ordering steps. The report also covers screen design using mock diagrams to visualize the client system interface and customer interaction. Furthermore, it outlines acceptance criteria for both the insurance company and the admin, ensuring critical elements such as patient details, specialist information, and appointment dates are accurately captured. The application architecture is presented, followed by a Request for Tender (RFT) analysis, determining specifications needed from suppliers. Finally, the report compares Agile and Waterfall methodologies, emphasizing the differences in client involvement, team organization, user-friendliness, and risk factors, providing a comprehensive understanding of the project's analytical foundation. Desklib offers more resources for students including past papers and solved assignments.

BUSINESS ANALYSIS

WORK BREAKDOWN STRUCTURE
Project is divided into small components.
Components are managed by team
accordingly.
We can see work breakdown structure as a
hierarchical decomposition.
This decomposition is displayed by using the
gantt chart.
Timing behavior of the system is displayed in
gantt chart.

‘TO- BE’ DESIGN ACTIVITY
DIAGRAM
Diagram describe the future aspect of the
project.
Processes involved in project and
organizational culture is showed in this
duagram.
TO-BE diagram for the system is given on
next page:

Organisational Change
AS-IS Diagram TO-BE diagram
Shows current working
of project
Registration is not
involved.
Ordering step is not
involved
Main component is
mentioned.
Working of the system is
not specified.
Shows future aspect of
project.
Registration is involved.
Ordering steps should be
there.
All the component is
mentioned.
Working of the system is
specified.

Screen Design
Design of the screen displayed using the
screen design.
Client system interface is there.
How customer interact with the system is
viewed.
Also known as mock diagrams.

Mock diagrams
Insurance Company Appointment
confirmation

Acceptance Criteria
Acceptance criteria for
insurance company:
Patient name should be
there.
Disease should be
mentioned properly.
The required fund
should be there in the
system.
There should be proper
address and contact
number of the patient.
Acceptance criteria
for the admin:
Patient name should
be there.
Specialist name
should be mentioned
clearly in the system.
The appointment date
should be mentioned
in the system.

Application Architecture
Shows the organization architecture of the
system.

REPORT TO CLIENT
Request For Tender(RFT)
1.Determines
It determines the points need to accomplish through
supplier for meet the specification requirement such
as provide fund, bonus, appointment, specialist for
treatment on the basis of clients view..
2. Purpose/Outcomes
The purpose of determining specifications for this
system is to help patients by providing fund for
treatment and bonus to family doctors and medical
specialist as well by confirming booking with medical
specialist of related disease..

Differences between Agile and Waterfall
Agile Methodology Waterfall Method
Involvement of the client
is there.
team is self motivated and
self organized.
More user- friendly.
Focus on development of
product.
Risk factor is less but
slower development.
After every stage, user
determines the product
Involvement of client is
not there.
team is divided
according to the
different phase.
Less user friendly.
Focus on development of
project.
Risk factor is more but
faster than agile.
Updation is easy