Business Analysis Report: Work Breakdown Structure and System Design

This business analysis report details the work breakdown structure (WBS) of a project, dividing it into manageable components with a Gantt chart illustrating the timing. It includes a 'TO-BE' design activity diagram that outlines the future state of the project, focusing on processes and organizational culture, contrasting it with the 'AS-IS' diagram to highlight organizational changes. The report also covers screen designs to show client system interaction, acceptance criteria for patient and specialist registration, and the application architecture. Furthermore, it addresses the Request For Tender (RFT), defining client requirements for software functionalities like patient and specialist registration, doctor connections, and fund allocation. Finally, the document compares Agile and Waterfall methodologies, noting their differences in client involvement, team organization, and development speed, emphasizing the importance of selecting the appropriate approach based on project needs. Desklib provides access to this and many other 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.
Timing behavior of the system is displayed in
gantt diagram.
This decomposition is displayed by using the
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
diagram.
TO-BE diagram for the system is given on
next page:

Organisational Change
AS-IS Diagram TO-BE diagram
Current working of the
system is showed
Registration process of the
client is not mentioned
Funds processing is not
shown in this diagram.
Stakeholders is not
Main component of the
project are discussed
Main focus on outlook of
the project.
Outline of the project is
mentioned .
. Future working of the
project is showed
Registration process of the
client is mentioned
Funds processing is shown
in this diagram.
Stakeholders is mentioned
Every are mentioned in the
diagram.
Main focus on the working
of the project.
External and internal
property is

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
Registration of
patients
Registration of medical
specialists

Acceptance Criteria
Acceptance criteria for
registration
1. Field should be
properly mentioned.
2. Details should be
stored on submitting.
3. Condition should be
satisfy while taking
the input.
4. Address must be
entered accordingly.
Acceptance criteria for the
admin:
1. Specific ID should be
enter
2. Contact number of the
specialist should be
there.
3. Details should be
stored on submitting.
4. Text area should be
provided for entering
the information.

Application Architecture
Shows the organization architecture of the
system.

REPORT TO CLIENT
Request For Tender(RFT)
1.Determines
The request for tender determines the requirements of client
to fulfil the functionalities of software used by organisation
which consist of registering of patients and medical
specialists, connect various specialized doctors, raise funds
and bonus.
2. Purpose/Outcomes
The request for tender utilized for fulfil the purpose of this
software which provides platform to register patients and
specialist which will help in assisting medical treatment and
Medigood Insurance System provide fund for treatment of
patients with bonus for family doctors and specialists as well.

Differences between Agile and Waterfall
Agile Methodology Waterfall Method
Client is not involved during
development.
Development team is self
motivated and self
organized.
End result is user friendly
Concern about the product
development.
Development is slower but
risk factor is low.
After every stage, user
determines the product
Client is involved during
development.
According to the
different phase, the team
is divided.
End result is not user
friendly.
Concern about the
project development.
Development is faster
but risk factor is more.
Updation of software is