Case Study: Analysis of Headspace System and Stakeholders

This case study analyzes the Headspace system, focusing on its stakeholders, questionnaires, and use cases. The assignment begins with a stakeholder map identifying key actors such as case workers, cloud vendors, healthcare providers, and government entities. It then presents a questionnaire designed for patients and case workers to gather requirements and feedback. The core of the study involves a detailed use case analysis, outlining scenarios for registration, login, data input, story access, system updates, and other functionalities. Each use case includes descriptions, actors, related use cases, preconditions, postconditions, and exception conditions. The case study also references relevant literature to support its findings and recommendations. The assignment provides a comprehensive overview of the Headspace system, providing valuable insights into its design and functionality.

0ASSIGNMENT 2: CASE STUDY OF HEADSPACE
Assignment 2: Case Study of Headspace
Name of the Student
Name of the University

1ASSIGNMENT 2: CASE STUDY OF HEADSPACE
Table of Contents
1. Stakeholder Map:.........................................................................................................................2
2. Questionnaire:..............................................................................................................................4
3. Use Case:.....................................................................................................................................5
Bibliography:.................................................................................................................................13

2ASSIGNMENT 2: CASE STUDY OF HEADSPACE
1. Stakeholder Map:
Case worker: Case worker are classified as those employees within “Headspace” who are
capable of saving the patient data to the database.
Cloud application form: These packages that Headspace workers will probably be using
will be set up on all the impair infrastructure.
Cloud data Record: The details will be compiled within the appliances set up on
Headspace and redirected to cloud. These clump collection will probably support the data.
Cloud Vendor: These impair supplier will be supplying the impair pertaining products
and services to Headspace. It not acquire vacation service plan provider.
General practitioner or healthcare provider: Normal practitioner or healthcare provider
will probably habits reaching the patient to assemble mandatory data regarding patient condition.
Furthermore, all the stakeholder use the fact that data to help remedy patient.

3ASSIGNMENT 2: CASE STUDY OF HEADSPACE
Government: The US government will be managing the system development not directly
from your IT pertaining guidelines and legislation.
Input data: The case worker will probably enter everything compiled provided by the
patient into the tale area of system. The system cannot on auto-pilot enter data provided by many
different devices. Mainly approved employees may well enter the results into patient story board.
Legislation: The system implementation in fact need to be completed by immediately
after any nearby and country wide guidelines all the NSW and Sydney respectively.
Psychiatrist: Psychiatrist will habits reaching the patient to assemble mandatory data
regarding patient condition. Furthermore, all the stakeholder use the fact that data to help remedy
patient.
Psychologist: Psychologist will habits reaching the patient to assemble mandatory data
regarding patient condition. Furthermore, all the stakeholder use the fact that data to help remedy
patient.
Recording all the patient case: The system will have the ability to save the patient story
during the impair database. This valuable storyline will be raised for the inner role only. A lot of
the approved crew about headspace may well obtain the tale on the patient.
SLA: Program quality transaction will be the proof of variety of mutual acceptances in
regard to products and services that are provided by the impair supplier to the “Headspace”.
Along with this it also provides support to the procedure involved in the payment.
Stating the patient story: Providing of the patient story to some of the sales staff about
headspace. These headspaces will allow a lot of workers who are not bothered instance all round

4ASSIGNMENT 2: CASE STUDY OF HEADSPACE
practitioner or healthcare provider, psychologist and variety of different to discover the patient
story. The patient story many times seems only when the patient visit them.
System Analyst: The key about establishing the system in Headspace is the key analysist.
2. Questionnaire:
Questionnaire for patient or one’s own relative can be for the reason that following.
1) Just what exactly features are you interested the system to have got?
2) Which kind of material you should talk about?
3) The simplest way the system will have the option to aid you? In the opinion.
4) The simplest way some ways do you want to communicate with the human beings
on Headspace?
5) Do you wish to make an account problem towards the system?
6) Do you wish to present rating towards the staff which results in you'll?
7) Should really the system store the adventure?
8) The capabilities you need the system to have got?
The questionnaire for case worker are for the reason that following.
1) How should you choose the system to suggestions details of your stuff?
2) Would you like the system to admission to any kind of adventure of the patient?
3) For a way a number of days the system should retain an account?

5ASSIGNMENT 2: CASE STUDY OF HEADSPACE
3. Use Case:
Name of the use case Register
Description The registration of the user is must for the
purpose of using the functions present in a
system. User ID and a password is created by
the cloud vendor after the user is registered in

6ASSIGNMENT 2: CASE STUDY OF HEADSPACE
the system.
Actors Caseworkers, psychologist, general
practitioner and psychiatrist
Related use case For the purpose of Logging in.
Stakeholders Caseworker, psychologist, general
practitioner and psychiatrist and administrator
Preconditions In the system the users should be new.
Post conditions The patient would be recorded by the system.
Exception Unavailability of the proper connection
between the system and the database.
Name of the use case Logging in.
Description login by the user to the system for using the
system functions and features
Actors Caseworker, psychologist, general
practitioner and psychiatrist
Related use case Register
Stakeholders Caseworker, psychologist, general
practitioner and psychiatrist and administrator
Preconditions Registered user.
Post conditions User login is permitted
Exception The connection with the database is not

7ASSIGNMENT 2: CASE STUDY OF HEADSPACE
proper
Name of the use case The input of the story
Description Recording of the patient story into the system
will be done.
Actors Case worker
Related use case Access Story
Stakeholders Case worker, general practitioner,
psychologist, psychiatrist and cloud vendor
Preconditions The patient should be an existing one
Post conditions Record of story is successful
Exception Storing in the cloud is not done
Name of the use case Access Story
Description The authorized users are only able to visualize
the patient story.
Actors Case worker, psychologist, general
practitioner and psychiatrist
Related use case Input Story
Stakeholders Caseworker, psychiatrist, psychologist,
general practitioner and cloud vendor
Preconditions Authorization to access story is essential
Post conditions The access is permitted

8ASSIGNMENT 2: CASE STUDY OF HEADSPACE
Exception Corrupted story
Name of the use case System Update
Description The cloud system is updated by the vendor
periodically or according to the headspace
Actors Vendors of the cloud system
Related use case None
Stakeholders Case worker, psychologist, general
practitioner, psychiatrist and cloud vendor
Preconditions Update must be valid
Post conditions Update done
Exception Updating is not supported.
Name of the use case Installation of the packages
Description Installation of various software packages
within cloud application.
Actors Vendors of the cloud system
Related use case None
Stakeholders Case worker, psychologist, general
practitioner, psychiatrist and cloud vendor
Preconditions According to the needs of the organizations

9ASSIGNMENT 2: CASE STUDY OF HEADSPACE
packages are determined
Post conditions Installation done
Exception Corrupted system data
Name of the use case Assistance in the Analysis
Description Assistance will be provided to the patients by
the psycologists
Actors Psychologist
Related use case None
Stakeholders Case worker, psychologist, general
practitioner, psychiatrist and cloud vendor
Preconditions Authorization of the data inputted.
Post conditions Completely updated.
Exception Corrupted data.
Name of the use case Stored Mental Health Record
Description Recording of the data regarding the illness
and the progress that has been made by the
Psychologist.
Actors Psychologist
Related use case None

10ASSIGNMENT 2: CASE STUDY OF HEADSPACE
Stakeholders Case worker, psychologist, general
practitioner, psychiatrist and cloud vendor
Preconditions Authorization of the input data
Post conditions Completed update.
Exception Corrupted data
Name of the use case Check System Actions
Description The activities of the system will be monitored
by the administrator.
Actors Administrator
Related use case None
Stakeholders Case worker, psychologist, general
practitioner, psychiatrist and cloud vendor
Preconditions Access to the requested area by the admin.
Post conditions The monitoring is under progression
Exception Corrupted or jammed path of the information
flow
Name of the use case System Maintenance
Description The fundamental resources and functions the
system will be maintained the administrators
Actors Administrator