S1 2018 Business Analysis: Medigood National Health Insurance Report
VerifiedAdded on 2023/06/15
|21
|3622
|290
Report
AI Summary
This report delivers a comprehensive product analysis of Medigood National Health Insurance, focusing on the implementation of a software system to improve patient management and telehealth consultations. The analysis includes a stakeholder analysis identifying key players and their roles, a product vision document outlining the project's goals and features, an "As-is" process flow diagram illustrating the current business processes, a product backlog prioritizing system requirements using the MoSCoW technique, and use case diagrams and descriptions detailing system interactions. The report also identifies object classes relevant to the system, providing a thorough evaluation of the project's scope and requirements. Desklib offers a variety of similar solved assignments and past papers.

Running head: PRODUCT ANALYSIS REPORT
Product Analysis Report: Medigood National Health Insurance
Name of the Student:
Student ID:
Name of the University:
Author’s note:
Product Analysis Report: Medigood National Health Insurance
Name of the Student:
Student ID:
Name of the University:
Author’s note:
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

1PRODUCT ANALYSIS REPORT
Table of Contents
Task 1.01 Stakeholder Analysis......................................................................................................2
Task 1.02 System/Product Vision Document..................................................................................3
Task 1.03 “As-is” Process Flow Diagram.......................................................................................4
Task 1.04 Product Backlog..............................................................................................................6
MoSCoW Technique.......................................................................................................................6
Task 1.05 Use Case Diagram and Description................................................................................7
Task 1.06 Object Classes Identification........................................................................................15
Bibliography..................................................................................................................................17
Appendix Task A: Project Journal.................................................................................................20
Table of Contents
Task 1.01 Stakeholder Analysis......................................................................................................2
Task 1.02 System/Product Vision Document..................................................................................3
Task 1.03 “As-is” Process Flow Diagram.......................................................................................4
Task 1.04 Product Backlog..............................................................................................................6
MoSCoW Technique.......................................................................................................................6
Task 1.05 Use Case Diagram and Description................................................................................7
Task 1.06 Object Classes Identification........................................................................................15
Bibliography..................................................................................................................................17
Appendix Task A: Project Journal.................................................................................................20

2PRODUCT ANALYSIS REPORT
Task 1.01 Stakeholder Analysis
The stakeholder analysis is done for ensuring that activities of the project would be
implied for listing the development of the operations and alignment of the effective evaluation of
the stakeholders (Jonasson 2016). The project stakeholders would be deployed for forming the
analysis of the supplementary development of the activities. The stakeholders of the project are
customer, supplier, sponsor, end users, help desk, regulators, executives, project team. The
stakeholders of the project would be responsible for user of the software system developed,
provide materials required for the project completion, provide investment to the project team for
doing the project, would utilize the developed project outcome, support and help for the progress
of the project, changes in the project would be modified, would be responsible for taking
effective key decisions in the project, and would have to carry out the operations of the project
and form the achievement of the final deliverable (Hailes 2014). The stakeholder analysis for the
software implementation project along with the patient management system for Medigood
National Health Insurance is given below,
Name Roles Attitudes Authority Power Influence
Customer User of the software system
developed
Neutral Accountable High High
Supplier Provide materials required for
the project completion
Interested Informed Low High
Sponsor Provide investment to the
project team for doing the
project
Highly
Interested
Informed High High
Task 1.01 Stakeholder Analysis
The stakeholder analysis is done for ensuring that activities of the project would be
implied for listing the development of the operations and alignment of the effective evaluation of
the stakeholders (Jonasson 2016). The project stakeholders would be deployed for forming the
analysis of the supplementary development of the activities. The stakeholders of the project are
customer, supplier, sponsor, end users, help desk, regulators, executives, project team. The
stakeholders of the project would be responsible for user of the software system developed,
provide materials required for the project completion, provide investment to the project team for
doing the project, would utilize the developed project outcome, support and help for the progress
of the project, changes in the project would be modified, would be responsible for taking
effective key decisions in the project, and would have to carry out the operations of the project
and form the achievement of the final deliverable (Hailes 2014). The stakeholder analysis for the
software implementation project along with the patient management system for Medigood
National Health Insurance is given below,
Name Roles Attitudes Authority Power Influence
Customer User of the software system
developed
Neutral Accountable High High
Supplier Provide materials required for
the project completion
Interested Informed Low High
Sponsor Provide investment to the
project team for doing the
project
Highly
Interested
Informed High High
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

3PRODUCT ANALYSIS REPORT
End Users Would utilize the developed
project outcome
Neutral Accountable High Low
Help Desk Support and help for the
progress of the project
Interested Consulted Low Low
Regulators Changes in the project would
be modified
Uninterested Responsible Low High
Executives Would be responsible for
taking effective key decisions
in the project
Highly
Interested
Accountable High High
Project
team
Would have to carry out the
operations of the project and
form the achievement of the
final deliverable
Interested Responsible Low Low
Task 1.02 System/Product Vision Document
Product Vision Document
Software Implementation in Medigood National Health Insurance
Version: 1.0 Date: 5/4/18
Introduction: The document is developed for listing the product characteristics and description
that would be required for the completion of the project of software for data management in
Medigood National Health Insurance.
Product overview: The implication of the software development for data analysis would be
End Users Would utilize the developed
project outcome
Neutral Accountable High Low
Help Desk Support and help for the
progress of the project
Interested Consulted Low Low
Regulators Changes in the project would
be modified
Uninterested Responsible Low High
Executives Would be responsible for
taking effective key decisions
in the project
Highly
Interested
Accountable High High
Project
team
Would have to carry out the
operations of the project and
form the achievement of the
final deliverable
Interested Responsible Low Low
Task 1.02 System/Product Vision Document
Product Vision Document
Software Implementation in Medigood National Health Insurance
Version: 1.0 Date: 5/4/18
Introduction: The document is developed for listing the product characteristics and description
that would be required for the completion of the project of software for data management in
Medigood National Health Insurance.
Product overview: The implication of the software development for data analysis would be
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

4PRODUCT ANALYSIS REPORT
aligned for the implication of the effective management of the data along with the patient
management system for Medigood National Health Insurance.
Product Features: The product developed would act as the effective management of the data
implication management. The supply of the effective integration would result in forming the
deployment of the successive management operations. The registering in the system would help
in monitoring the online operations by the Telehealth technology. The use of Telehealth
equipments would also be useful for the modification of the operations development. The
completion of the consultation would result in generation of the payment for both specialist and
family doctor.
Constraints: the qualifying patients must have appointment with the specialist
Documentation Required: System design documentation
Task 1.03 “As-is” Process Flow Diagram
The “As-is” Process Flow Diagram for the operations of Medigood National Health
Insurance would be implied for the alignment of the operations for the development of the
effective software processing in the organization (Jouen et al. 2015). The alignment of the
effective process flow diagram would help in understanding the existing information processing
as shown below,
aligned for the implication of the effective management of the data along with the patient
management system for Medigood National Health Insurance.
Product Features: The product developed would act as the effective management of the data
implication management. The supply of the effective integration would result in forming the
deployment of the successive management operations. The registering in the system would help
in monitoring the online operations by the Telehealth technology. The use of Telehealth
equipments would also be useful for the modification of the operations development. The
completion of the consultation would result in generation of the payment for both specialist and
family doctor.
Constraints: the qualifying patients must have appointment with the specialist
Documentation Required: System design documentation
Task 1.03 “As-is” Process Flow Diagram
The “As-is” Process Flow Diagram for the operations of Medigood National Health
Insurance would be implied for the alignment of the operations for the development of the
effective software processing in the organization (Jouen et al. 2015). The alignment of the
effective process flow diagram would help in understanding the existing information processing
as shown below,

5PRODUCT ANALYSIS REPORT
Figure 1: “As-is” Process Flow Diagram for Medigood National Health Insurance
(Source: Created by the author in Ms-Visio)
Explanation of information flow from the diagram above: The three main entity of
the “As-is” Process Flow Diagram are Office Administrator or family doctor, medical specialist
consultation, and Patients. The patients would have to initiate the information flow by requesting
for the Medigood health insurance by applying for it (Hau 2015). The office administrator or
family doctor would be responsible for analysing and evaluating whether the patient who have
applied for Medigood National Health Insurance is applicable for the getting the insurance. The
office administrator or family doctor would check the credentials of the patients for the criteria
of over 65, indigenous, and suffering chronic disease. If the patient passes all these credentials,
he or she would be approved for getting the insurance clearance. Else, the process of information
flow would cease and the application or request would be rejected. After approving the patient
Figure 1: “As-is” Process Flow Diagram for Medigood National Health Insurance
(Source: Created by the author in Ms-Visio)
Explanation of information flow from the diagram above: The three main entity of
the “As-is” Process Flow Diagram are Office Administrator or family doctor, medical specialist
consultation, and Patients. The patients would have to initiate the information flow by requesting
for the Medigood health insurance by applying for it (Hau 2015). The office administrator or
family doctor would be responsible for analysing and evaluating whether the patient who have
applied for Medigood National Health Insurance is applicable for the getting the insurance. The
office administrator or family doctor would check the credentials of the patients for the criteria
of over 65, indigenous, and suffering chronic disease. If the patient passes all these credentials,
he or she would be approved for getting the insurance clearance. Else, the process of information
flow would cease and the application or request would be rejected. After approving the patient
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

6PRODUCT ANALYSIS REPORT
for getting the Medigood insurance, the office administrator or family doctor would check with
the medical specialist consultation if they would be available for meeting and examining the
patient. The specialist’s time table and appointment list would be evaluated for finding out the
possible day for meeting with the patient (Valacich, George and Hoffer 2014). The office
administrator or family doctor would ensure that a date feasible for both patient and specialist
and convey the appropriate time table to both of them. The specialist and the patient would get
the meeting time and date and the process would be stopped.
Task 1.04 Product Backlog
User User Story
Business Analyst As a business analyst, I want the implication of the software tools so that the
software would help in easing the business of the Medigood insurance
Customer As a customer, I want the user manual for the software tool so that I would
be able to utilize the system comfortably
Sponsor As a sponsor, I want the detailed report of the cost expended so that I would
be able to calculate the net profit from the project
Executives As an executive, I want the proper implication of the products and services
so that the organization would achieve smart profit from the system.
Project team As a project team, I want the completion of the project so that the project
team would get the benefit of final deliverable.
MoSCoW Technique
Must have: Feasible software design
for getting the Medigood insurance, the office administrator or family doctor would check with
the medical specialist consultation if they would be available for meeting and examining the
patient. The specialist’s time table and appointment list would be evaluated for finding out the
possible day for meeting with the patient (Valacich, George and Hoffer 2014). The office
administrator or family doctor would ensure that a date feasible for both patient and specialist
and convey the appropriate time table to both of them. The specialist and the patient would get
the meeting time and date and the process would be stopped.
Task 1.04 Product Backlog
User User Story
Business Analyst As a business analyst, I want the implication of the software tools so that the
software would help in easing the business of the Medigood insurance
Customer As a customer, I want the user manual for the software tool so that I would
be able to utilize the system comfortably
Sponsor As a sponsor, I want the detailed report of the cost expended so that I would
be able to calculate the net profit from the project
Executives As an executive, I want the proper implication of the products and services
so that the organization would achieve smart profit from the system.
Project team As a project team, I want the completion of the project so that the project
team would get the benefit of final deliverable.
MoSCoW Technique
Must have: Feasible software design
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

7PRODUCT ANALYSIS REPORT
Should Have: Security of operations
Could Have: Cloud Conputing
Won’t Have: Tangible data storage
Task 1.05 Use Case Diagram and Description
The use case is developed for successfully aligning with the development of the effective
operations for the alignment of the improved operation development (Gonen 2014). The
implication of the use case diagram would help in realization of the actor and the successful
development of the process development for the operations. The implication of the successive
development model would help in easing the information processing and execution of the
processes for the organization of Medigood National Health Insurance. The following is the use
case diagram for the existing system at the organization,
Should Have: Security of operations
Could Have: Cloud Conputing
Won’t Have: Tangible data storage
Task 1.05 Use Case Diagram and Description
The use case is developed for successfully aligning with the development of the effective
operations for the alignment of the improved operation development (Gonen 2014). The
implication of the use case diagram would help in realization of the actor and the successful
development of the process development for the operations. The implication of the successive
development model would help in easing the information processing and execution of the
processes for the organization of Medigood National Health Insurance. The following is the use
case diagram for the existing system at the organization,

8PRODUCT ANALYSIS REPORT
Figure 2: Use Case Diagram for Medigood National Health Insurance
(Source: Created by the author in Ms-Visio)
Use Case #0005101
Use Case Name: Check if patient is applicable for insurance
Scenario: The scenario has depicted the use of the information flow for
knowing whether the patient would be applicable for the inclusion of
the operation for the deployment of the effective operations. The
scenario would show that the office administrator or family doctor
would check if the patient who has applied for getting the Medigood
is applicable for getting the support on medical insurance. The office
Figure 2: Use Case Diagram for Medigood National Health Insurance
(Source: Created by the author in Ms-Visio)
Use Case #0005101
Use Case Name: Check if patient is applicable for insurance
Scenario: The scenario has depicted the use of the information flow for
knowing whether the patient would be applicable for the inclusion of
the operation for the deployment of the effective operations. The
scenario would show that the office administrator or family doctor
would check if the patient who has applied for getting the Medigood
is applicable for getting the support on medical insurance. The office
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

9PRODUCT ANALYSIS REPORT
administrator or family doctor would check if the patient is over 65,
indigenous, and suffering chronic disease. The checking would be
initiated from the submitted information and various health records.
Triggering Event: Patient applying for Medigood Health Insurance and the existence of
the information of the patient
Brief Description: The office administrator or family doctor would be responsible for
analysing and evaluating whether the patient who have applied for
Medigood National Health Insurance is applicable for the getting the
insurance. The office administrator or family doctor would check the
credentials of the patients for the criteria of over 65, indigenous, and
suffering chronic disease.
Actors: Patient, office administrator or family doctor
Stakeholders: Patient, Medigood National Health Insurance, office administrator or
family doctor
Preconditions: Patient had applied for the Medigood Insurance
Post conditions: Patient would be either approved for getting Medigood Insurance or
Rejected from getting Medigood Insurance
Flow of Activities: Patient’s report Office Administrator or Family Doctor Health
Database Office Administrator or Family Doctor Patient
Exception Patient would not be validated for getting the Medigood Insurance
administrator or family doctor would check if the patient is over 65,
indigenous, and suffering chronic disease. The checking would be
initiated from the submitted information and various health records.
Triggering Event: Patient applying for Medigood Health Insurance and the existence of
the information of the patient
Brief Description: The office administrator or family doctor would be responsible for
analysing and evaluating whether the patient who have applied for
Medigood National Health Insurance is applicable for the getting the
insurance. The office administrator or family doctor would check the
credentials of the patients for the criteria of over 65, indigenous, and
suffering chronic disease.
Actors: Patient, office administrator or family doctor
Stakeholders: Patient, Medigood National Health Insurance, office administrator or
family doctor
Preconditions: Patient had applied for the Medigood Insurance
Post conditions: Patient would be either approved for getting Medigood Insurance or
Rejected from getting Medigood Insurance
Flow of Activities: Patient’s report Office Administrator or Family Doctor Health
Database Office Administrator or Family Doctor Patient
Exception Patient would not be validated for getting the Medigood Insurance
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

10PRODUCT ANALYSIS REPORT
Conditions:
Use Case #0005102
Use Case Name: Search for suitable medical specialist
Scenario: The scenario would depict the searching of a medical specialist by the
office administrator or family doctor. The patient who have applied
for the Medigood Health Insurance would be cross checked for the
feasibility of the getting the approval of the insurance. The office
administrator or family doctor would then check for any specialist for
the patient.
Triggering Event: Approval of the patient for getting Medigood and All criteria of over
65, indigenous, and suffering chronic disease are met.
Brief Description: If the patient passes all these credentials, he or she would be approved
for getting the insurance clearance. After approving the patient for
getting the Medigood insurance, the office administrator or family
doctor would check with the medical specialist consultation if they
would be available for meeting and examining the patient. The
specialist’s time table and appointment list would be evaluated for
finding out the possible day for meeting with the patient.
Actors: office administrator or family doctor
Stakeholders: medical specialist, Medigood National Health Insurance, office
Conditions:
Use Case #0005102
Use Case Name: Search for suitable medical specialist
Scenario: The scenario would depict the searching of a medical specialist by the
office administrator or family doctor. The patient who have applied
for the Medigood Health Insurance would be cross checked for the
feasibility of the getting the approval of the insurance. The office
administrator or family doctor would then check for any specialist for
the patient.
Triggering Event: Approval of the patient for getting Medigood and All criteria of over
65, indigenous, and suffering chronic disease are met.
Brief Description: If the patient passes all these credentials, he or she would be approved
for getting the insurance clearance. After approving the patient for
getting the Medigood insurance, the office administrator or family
doctor would check with the medical specialist consultation if they
would be available for meeting and examining the patient. The
specialist’s time table and appointment list would be evaluated for
finding out the possible day for meeting with the patient.
Actors: office administrator or family doctor
Stakeholders: medical specialist, Medigood National Health Insurance, office

11PRODUCT ANALYSIS REPORT
administrator or family doctor
Preconditions: Search for the appropriate medical specialist consultation would be
initiated by the office administrator or family doctor
Post conditions: Appropriate Medical Specialist Consultation would be founded for
the patient
Flow of Activities: Office administrator or family doctor database of health records
record of medical specialist office administrator or family doctor
Exception
Conditions:
Patient would not be validated for getting the Medigood Insurance
Use Case #0005103
Use Case Name: Meeting time is fixed and Patients consults with specialist
Scenario: The scenario would depict office administrator or family doctor
checking and going through the appointment list and time schedule of
the specialist. The office administrator or family doctor would have to
ensure that the approval of the patient for the Medigood would help in
easing the patient by aligning a meeting between the specialist and
patient.
Triggering Event: Approval of the patient for getting Medigood and Specialist is
available for the patient
Brief Description: The specialist’s time table and appointment list would be evaluated
administrator or family doctor
Preconditions: Search for the appropriate medical specialist consultation would be
initiated by the office administrator or family doctor
Post conditions: Appropriate Medical Specialist Consultation would be founded for
the patient
Flow of Activities: Office administrator or family doctor database of health records
record of medical specialist office administrator or family doctor
Exception
Conditions:
Patient would not be validated for getting the Medigood Insurance
Use Case #0005103
Use Case Name: Meeting time is fixed and Patients consults with specialist
Scenario: The scenario would depict office administrator or family doctor
checking and going through the appointment list and time schedule of
the specialist. The office administrator or family doctor would have to
ensure that the approval of the patient for the Medigood would help in
easing the patient by aligning a meeting between the specialist and
patient.
Triggering Event: Approval of the patient for getting Medigood and Specialist is
available for the patient
Brief Description: The specialist’s time table and appointment list would be evaluated
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide
1 out of 21
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.