Headspace Project: System Analysis, Stakeholder & Use Case Report

This report presents a system analysis of the Headspace project, encompassing a stakeholder map, questionnaire, and use case diagrams. The stakeholder map identifies and categorizes stakeholders, detailing their areas of interest within the project. A questionnaire was developed to gather feedback on system experience, advantages, disadvantages, and suggestions for improvement. The use case diagram illustrates the system's functionalities, including patient registration, case insertion, and information updates, involving actors like Headspace staff, doctors, and patients. Detailed use case descriptions are provided for each function, outlining business goals, prerequisites, success conditions, and main paths. The report aims to provide a comprehensive overview of the system's design and functionality, supporting improvements and efficiency.

Running head: ASSESSMENT ITEM 2
System Analysis for Headspace Project: Assessment Item 2
Name of the Student
Name of the University
Authors’ Note

1ASSESSMENT ITEM 2
Table of Contents
1. Stakeholder Map..........................................................................................................................2
1.2 Stakeholder Categorization....................................................................................................3
1.3 Stakeholder and their Areas of Interest.................................................................................3
2. Questionnaire...............................................................................................................................4
3. Use Case Diagram.......................................................................................................................6
3.1 Use Case Description of each use case..................................................................................7
3.2 Detailed Use case description..............................................................................................10
References......................................................................................................................................12

2ASSESSMENT ITEM 2
Information System Manager
Headspace staffs
Workers
Medical Personnel
Doctors and Physicians
Government of Australia
Patients across Australia
Headspace project authority
Internal-Operation Stakeholders Internal-Executive Stakeholders
External-Executive StakeholdersExternal-Operation Stakeholders
High
HighLow
1. Stakeholder Map
As per analysis of the case study of Headspace project, the stakeholders are identified
along with their individual role based segmentation. The role wise specification of stakeholder is
performed under four different quadrants such as ‘external-executive’, ‘internal-operation’,
‘external-operation’, and ‘internal-executive’. Stakeholder map is prepared and shown as
underneath:
Figure 1: Headspace Project Stakeholder Analysis Map

3ASSESSMENT ITEM 2
(Source: Created by author)
1.2 Stakeholder Categorization
The map states some internal and external stakeholders in this case study of Headspace
project. Categorization and identification of stakeholder is performed under tabular format as
shown following:
Stakeholder
Types
Internal Headspace staffs, Information System Manager, workers,
Headspace project authority
Externa
l
Medical Personnel, Doctors and Physicians, Government of
Australia, and Patients across Australia
1.3 Stakeholder and their Areas of Interest
Areas of interest identification is the way of realizing individual stakeholder roles so that
individual stakeholder can be involved with their work intentions. Their individual
responsibilities are addressed in the following table in detail:
Stakeholder
Roles
Areas of Interest
Medical
Personnel
Medical personnel can be benefitted from system once the system can store
appointments and medicine details. The personnel can collect the patient
applications and review them so that applications can be sent to doctors.
Doctors and
Physicians
Doctors and physicians are interested for viewing patient case and update the
patient case details once diagnosis is completed. The appointment is allowed

4ASSESSMENT ITEM 2
for individual patients.
Government of
Australia
Australian government will be incorporated in the system for their area of
interest on system applications. Government personnel can easily overview
entire details about medical staffs, Australian patients, and supplier of
medicines.
Patients across
Australia
Patients are part of the system as they can check availability of doctors and
can view his/her treatment description and details.
Headspace staffs Headspace staffs are incorporated in the system as they can operate the
system along with databases with proper efficiency. Personnel can modify,
update, delete, and select stored data.
Information
System Manager
Information system manager will be responsible for developing the entire
system; therefore, he or she will be responsible as well.
Workers Workers are responsible for viewing the patient status, their updated details,
patient case scenario, and appointment as well.
Headspace
project authority
Headspace project authority can perform their activity with patient
information stored into database. Newly designed system could be useful for
obtaining profit, additional cost for treatment, medicinal requirements, and
booking appointment, and others.
2. Questionnaire
Headspace authorities need to identify the patient and staff overview of the system and
new system implementation. Henceforth, the questionnaire is prepared with all questions

5ASSESSMENT ITEM 2
regarding collection of opinions. The feedback and opinions are for reviewing in later so that
new system can be improved along with recommended settings and functionalities. The
questionnaire is shown as following:
1. Inform us about system experience; share us whether you are experiencing it for
first time or you have used the system before.
2. What do you require the system to do or what will be expectations from the
system?
3. Identify what are the advantages and disadvantages of system.
4. Identify the ways to remove disadvantages in the system; provide suggestions
for removing the disadvantages.
5. Identify what will be benefits from the system.
6. Provide some suggestions about the functionality that should be included in the
new system.
7. Tell us how you will be affected by the system.
8. Tell us whether the staff performance is improved or not after the system is
implemented.
9. Inform us what glitches that you have faced or bugs that you have experienced
till now.
10. Provide rating on the system performance with including overall feedback as
well.

6ASSESSMENT ITEM 2
3. Use Case Diagram
This particular use case is designed with scenario of identifying specific yet appropriate
functionalities regarding the system. Use case of the system included some different actors, such
as Headspace personnel, doctors, and patients. The doctors are identified as other, Headspace
personnel are identified as primary, and patients are identified as secondary actors. Workers take
responsibility of registering the patients, update patient information, include their individual
cases, and viewing treatment status. The physicians will update the patient information when the
patient diagnosis is completed. Medical personnel can complete booking of appointment along
with individual doctors while checking doctors’ availability, reviewing staff details, and teenager
case. The medical personnel can insert medical treatment details and can update the booking
details. The patients can view individual information, check the appointment details, detailed
diagnosis, and medicine records. The use case diagram is essential for adding specific
functionalities in order to make system useful to database.

7ASSESSMENT ITEM 2
Figure 2: Headspace Project for Use Case Diagram
(Source: Created by author)
3.1 Use Case Description of each use case

8ASSESSMENT ITEM 2
Use Case Description
Patient
Registration
This particular option can be utilized for registering the patient for first time,
the registration process require patient details.
Insert patient
case
Staffs can enter individual case and health problem scenario from this option.
View patient
status
The option can be utilized for viewing the patient status when they are under
appointment schedule.
Update patient
status
The update patient status option can be used for updating patient status when
the diagnosis and treatment is completed from doctors. The update option is
available from medical staffs and Headspace personnel.
Update patient
information
Doctors are responsible for updating patient information as per individual
appointment is completed. The doctors can add details regarding patient
information along with medical records such as medicine, patients’ case as
well.
Book doctor
appointment
Medical staffs can use this particular option with individual doctor
appointment so that individual patient details can be included. The book
appointment option can add patient information with detailed steps and
necessary routine of work.
View patient
information
This option is typically used from staff side showing patient information with
details of patient treatment details and medicines.
Update
treatment of
patient
When the diagnosis and treatment is completed; the doctor can update
treatment details to assure consistency in stored data for the system.

9ASSESSMENT ITEM 2
Use Case of Inserting Patient Cases
Figure 3: Use case diagram for insertion of patient cases into the system
(Source: Created by author)
Description: The use case is relevant for using from staffs, doctors, and patients side.
The use case is a part of the system for insertion of patient case into the system; the option can
allow staffs to view the patient details. The patient can check their appointment details when
staffs have stored the details in the stored information tab. Doctors can be able to view the
patient scenario as they discussed about it to the staffs. The doctors can easily identify the
disease with earlier diagnosis with offering appropriate treatment for the patients. The patient can
easily book as per the doctor appointment status and availability.

10ASSESSMENT ITEM 2
3.2 Detailed Use case description
Use Case Name: Insertion of the Patient cases into the system
Primary Actor: Headspace Staffs
Secondary Actors: Patients
Other Stakeholders: Doctors
Business Goal: The business goals are as following:
1. Reduction of treatment cost
2. Faster response to treatments
3. Record storing for individual patients
Prerequisites: The prerequisites were:
A. Portal sign-in
B. Applicable for registered patients
Success Condition Success criteria and condition is flawless registration for each
patient.
Main Path In the Use Case flow path, the patient first starts conversation with
staffs to initiate the activity. Once, the patient has provided their
health details. Then the staffs can store the collected information
from patients into the system.

11ASSESSMENT ITEM 2
Post condition: The patient case is inserted and doctors can review the patient case
as well.