Business Analysis of Medigood Health Insurance System

This report focuses on analysis of the case study based on “Medigood” which is a national health insurance system that pays for visit of patients to family doctors. In this report, the discussions are carried out on the analysis of stakeholders associated with the system and a vision statement has been produced in context to the system.

Running head: BUSINESS ANALYSIS
Business Analysis S1 2018 - Assignment 1
Student Name:
University Name:

1BUSINESS ANALYSIS
Table of Contents
Introduction......................................................................................................................................2
Task 1.01: Stakeholder analysis......................................................................................................2
Task 1.02: System or Product Vision statement..............................................................................2
Problem Description....................................................................................................................3
System Capabilities.....................................................................................................................3
Business Benefits.........................................................................................................................4
Task 1.03: “AS-IS” process flow diagram......................................................................................4
Task 1.04: Product backlog.............................................................................................................5
Task 1.05: Use cases........................................................................................................................6
Task 1.06: Object classes.................................................................................................................9
Task 1.07: Video Transcript............................................................................................................9
Conclusion.....................................................................................................................................10
Bibliography..................................................................................................................................11
Appendix - Project Journal............................................................................................................13

2BUSINESS ANALYSIS
Introduction
This report focuses on analysis of the case study based on “Medigood” which is a
national health insurance system that pays for visit of patients to family doctors. In this report,
the discussions are carried out on the analysis of stakeholders associated with the system and a
vision statement has been produced in context to the system. The scenario of the existing system
has been illustrated by designing the “AS-IS” process flow diagram. A product backlog table has
been presented along with MoSCoW Analysis for identification of gaps in the existing system.
The different use cases depicts the sub systems of the system that will be used by the users. The
object classes has been identified and demonstrated to analyze key functions of the system.
Task 1.01: Stakeholder analysis
Stakeholders are considered to be essential for any system and they form an integral part
of the system. Hence, the key stakeholders that has been identified in context to the presented
case of Medigood are presented as below:
Stakeholder Role Interest Influence
Patient User High Low
Family Doctor User Medium High
Office Administrator Admin Medium Medium
Medical Specialist User High Low
Task 1.02: System or Product Vision statement
According to Satzinger, Jackson and Burd (2011), a system vision document helps to
understand the functions that a system will perform along with the benefits that will be achieved

3BUSINESS ANALYSIS
by implementing a new system. Hence, the system vision document in context to the business
case of Medigood is presented as below:
Problem Description
Medigood is a national health insurance system that provides payment as bonus to family
doctors when a patient visits for consultation with medical specialist. The consultation process is
done either by phone or telehealth equipment but the patient has to qualify according to their
criteria. The Family doctors has the liability to find suitable patients as well as medical
specialists in order to confirm a consultation procedure and receive bonus. The finding of patient
as well as medical specialist is a complex procedure and the scheduling of appointments also
gets delayed which results into longer process time for the consultation. The Family doctors has
to check the availability of patients as well as medical specialists for confirming an appointment
for consultation. Sometimes, the patients are busy and sometimes the specialist or even the
patient may not appear at all during the scheduled appointment. Thus, it makes it difficult for the
family doctors to complete the process successfully. Hence, it is recommended that a new system
have to be implemented to easier the consultation process.
System Capabilities
The new system should have the following listed capabilities in order to meet the
requirements of Medigood as listed below:
 Collection and storage of information related to patient and medical specialist.
 Collection of information about the appointments of medical specialist.
 Storing the availability information of patient as well as medical specialist.
 Monitoring the schedule of appointments according to availability.

4BUSINESS ANALYSIS
Business Benefits
It is determined that the introduction of a new system will help to improve the business
processes within Medigood with following benefits:
 Improvements in response time from patient as well as medical specialists.
 Reducing the labor required for finding suitable patient and medical specialist.
 Maintenance of correct and updated information of patient and medical specialist.
 Easier processing of payments through online mode.
Task 1.03: “AS-IS” process flow diagram
Figure 1: “AS-IS” process flow diagram of Medigood
(Source: Created by Author)

5BUSINESS ANALYSIS
Task 1.04: Product backlog
The product backlog has been designed after estimating the user stories in context to the
system of Medigood and it is presented in the table as below:
Product Backlog for New Payroll System
Task ID Story Estimate Priority
4 As a patient, I want to edit my personal information so that
my record is kept up to date.
5 1
2 As an administrator, I want to monitor scheduled
appointments so that consultation can be processed
efficiently.
4 2
3 As a patient, I want to log in to the system so that I can find
available doctors and specialist.
4 3
1 As a patient, I want to log off functionality so that
erroneous information is not input into the system.
4 4
6 As a medical specialist, I want to register into the system so
that patients can easily view availability.
10 5
5 As an administrator, I want to process the claim for
payment so that both the family doctor and specialist
receives the bonus.
7 6
MoSCoW Analysis
This analysis helps to prioritize the requirements to ensure success of a project and it has
been carried out on the Medigood system as presented below:
Must Haves
 Facility to register
 Login functionality
 Information of users
 Easy to use interface
Should Haves
 Facility for data retrieval
 Functionality to make modifications
of personal information
 Scheduling of appointments
Could Haves Wont Haves

6BUSINESS ANALYSIS
 Call facility from user information
 Email and messaging services to
inform the users
 Make payments online
 Slow response time
 Complex user interface
 Complexity in data retrieval
 Error or bugs
Task 1.05: Use cases
Use Case Diagram Description
Register This use case depicts the
registration functionality
of the system that the users
will use to enroll
themselves into the
system. The registration
will hold the personal
information of users.

7BUSINESS ANALYSIS
Login This use case depicts the
login functionality that the
users will use to access the
system with their personal
credentials that is
username and password.
This facility will help the
user to avail the services
offered by the system.
Find
patient
This use case depicts the
role played by family
doctor to find a suitable
patient. They have to login
into the system as user and
then they can request to
search the patient database
to find suitable patient
according to the criteria for
consultation.

8BUSINESS ANALYSIS
Find
specialist
This use case depicts the
function of finding a
specialist so that
consultation can be
processed. At first the
Family doctor logs in to
the system then searches
for specialist and chooses
the suitable one according
to requirement of patient.
Schedule
appointmen
t
This use case depicts the
functionality of booking
appointment for
consultation. The Family
doctor finds suitable
patient and specialist and
then checks their schedule
to confirm availability.
After confirmation of
availability the Family
doctor schedules an
appointment for

9BUSINESS ANALYSIS
consultation.
Task 1.06: Object classes
The five key classes that has been identified in context to the Medigood system are listed
below along with their attributes:
Class Attribute
Patient Patient_ID, Patient_Name, Patient_Address, Criteria
Family Doctor Doctor_ID, Doctor_Name, Doctor_Address
Medical Specialist Specialist_ID, Specialist_Name, Specialist_Address, Speciality
Appointment Appointment_ID, Patient_Name, Doctor_Name, Specialist_Name
Consultation Consultation_ID, Patient_Name, Specialist_Name, Fees
Task 1.07: Video Transcript
I have undertaken this project on Medigood which is a national health insurance system
that has introduced the bonus scheme for family doctor whenever a patient visits for
consultation. I have read the case study thoroughly and analysed that there are various issues
within the existing system of Medigood. I determined that the issues lead to poor performance of
the business and leads to delay in the consultation procedure. After analysing the issues, I
concentrated on identifying the stakeholders that are associated with Medigood to determine the
requirements properly. I prepared a stakeholder analysis in context to the business scenario of
Medigood and then I prepared a system vision document to present the business benefits that will
be achieved by implementing a new system.
I determined the present process flow within the business and deigned a “AS-IS” process
flow diagram to illustrate on the current business process and identified the gaps. I prepared the

10BUSINESS ANALYSIS
Product Backlog from the perspective of each user by determining the requirements of each user
from the system. I conducted the MoSCoW analysis to prioritize the requirements in context to
the new system. I designed five key use cases to present the modules that have to be incorporated
into the system. I identified the five key classes that are required for designing of the new system
such that business as well as user requirements are fulfilled by the system.
Conclusion
From the analysis on case of Medigood health insurance system, it has been identified
that there is a gap in their business process due to which often there is delay in the consultation
process. In the system vision document, the discussions states that there is a need to implement a
new system for making improvements in the business process. The system will help to meet the
requirements of various stakeholders associated with the business. The illustration on the current
business process flow depicts that there is a gap in communication which leads to delay or even
cancellation of the consultation procedure. The MoSCoW analysis illustrates on the requirements
that the new system have to fulfil in order to improve the business process of Medigood. The use
case diagrams present the various modules that has to be incorporated into the system to fulfil
requirements of the user in context to the business of Medigood.

11BUSINESS ANALYSIS
Bibliography
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Cuppen, E., 2016. 15 Stakeholder Analysis. Foresight in Organizations: Methods and Tools,
p.208.
Dingsoyr, T., Dyba, T., Gjertsen, M., Jacobsen, A.O., Mathisen, T.E., Nordfjord, J.O., Røe, K.
and Strand, K., 2018. Key Lessons from Tailoring Agile Methods for Large-Scale Software
Development. arXiv preprint arXiv:1802.05118.
Hajri, I., Goknil, A. and Briand, L., 2017. A change management approach in product lines for
use case-driven development and testing. In 23rd International Working Conference on
Requirements Engineering: Foundation for software Quality (REFSQ 2017).
Huang, L., Duan, Y., Gao, H., Li, H., Li, C. and Lin, Z., 2016. Checking Relationship
Consistency and Class Redundancy in a Class Diagram under Model-Driven
Engineering. International Journal of Hybrid Information Technology, 9(10), pp.185-200.
Khan, A.S., Oracle America Inc, 2016. System and method for automatically generating XML
schema for validating XML input documents. U.S. Patent 9,286,275.
Maslennikov, V.V. and Kalinina, I.A., 2015. Analysis of satisfaction of consumers of public
services. International Business Management, 9(6), pp.1141-1146.
Missonier, S. and Loufrani-Fedida, S., 2014. Stakeholder analysis and engagement in projects:
From stakeholder relational perspective to stakeholder relational ontology. International Journal
of Project Management, 32(7), pp.1108-1122.

12BUSINESS ANALYSIS
Sabharwal, S., Kaur, P. and Sibal, R., 2017. Empirical and Theoretical Validation of a Use Case
Diagram Complexity Metric.
Satzinger, J.W., Jackson, R.B. and Burd, S.D., 2011. Systems analysis and design in a changing
world. Cengage learning.
Shah, S.A.A., Shahzad, R.K., Bukhari, S.S.A. and Humayun, M., 2016. Automated Test Case
Generation Using UML Class & Sequence Diagram. British Journal of Applied Science &
Technology, 15(3).
Singh, A. and Sharma, E.S., 2014. Functional Test Cases Generation Based on Automated
Generated Use Case Diagram. International Journal of Innovative Research in Advanced
Engineering (IJIRAE), (8).

13BUSINESS ANALYSIS
Appendix - Project Journal
Number Date Activity Explanation Status
1 25/03/2018 Studying the case
study
This activity involved reading
the case study and determining
the key requirements.
Completed
2 28/03/2018 Identification of
Stakeholders
In this activity the key
stakeholders of Medigood were
identified along with their
interest and influence over the
project.
Completed
3 01/04/2018 Producing a system
vision statement
This activity required an
understanding of system analysis
and design for producing a
vision document in context to the
system of Medigood.
Completed
4 05/04/2018 Preparing the “AS-
IS” process flow
diagram
This activity was carried out to
illustrate upon the existing
processes within Medigood.
Completed
5 07/04/2018 Determining the
product backlog
from different user
perspectives
This activity involved
determining the product backlog
for Medigood to improve their
current business process.
Completed
6 10/04/2018 Conducting In this activity the analysis is Completed

14BUSINESS ANALYSIS
MoSCoW Analysis carried out to prioritize the key
requirements identified from the
case of Medigood.
7 12/04/2018 Identification of five
key classes
In this activity the five key
classes required for the system
are identified.
Completed