Information System Development at Headspace

This document discusses the development of an information system at Headspace, including stakeholder mapping, questionnaire, and use case diagram.

Running head: INFORMATION SYSTEM DEVELOPMENT AT HEADSPACE
Information System Development at Headspace
Name of the Student
Name of the University
Author’s Note:

1INFORMATION SYSTEM DEVELOPMENT AT HEADSPACE
Table of Contents
1. Stakeholder Map:.........................................................................................................................2
2 Questionnaire:...............................................................................................................................2
3 Use Case Diagram:.......................................................................................................................4
Bibliography:...................................................................................................................................7

2INFORMATION SYSTEM DEVELOPMENT AT HEADSPACE
1. Stakeholder Map:
Figure 1: Stakeholder Mapping
(Source: Created by Author)
2 Questionnaire:
The questionnaire is developed for the general practitioner.
i. How do you think you can work fast?

3INFORMATION SYSTEM DEVELOPMENT AT HEADSPACE
ii. Do you want the patient to upload their treatment related data into system or you
want check original reports and prescriptions?
iii. Do you think auto generated suggestions are good approach?
iv. Do you think giving some control or monitoring ability to patient is a good
choice?
v. How do you want to access the system?
vi. Do you want to access the system from remote locations?
vii. Are you accustomed of using any information system?
viii. What is your main responsibility?
ix. Do you need support for handling your secondary work?
x. What are your secondary works?

4INFORMATION SYSTEM DEVELOPMENT AT HEADSPACE
3 Use Case Diagram:
Figure 2: Headspace System UML Use Case Model
(Source: Created by Author)

5INFORMATION SYSTEM DEVELOPMENT AT HEADSPACE
Brief Description of Use Cases:
i. Record Patient Health: The ED staff is responsible for recording patient health
into system. This use case is associated with patient health progress report.
ii. Login: Every staff have to login to the system. The login has pre-condition that
user has already registered.
Fully described use case description:
Name of the use case Record Patient Story
Scenario The case worker listens to the patient story. After collecting the
required data, the case worker records the data into system
Trigger Event A new patient has arrived for treatment
Description The case worker is responsible for communicating with the
patient. The case worker has an interface that will allow him/her
to store the data into system
Actors Case Worker
Related use case Access Patient Story
Stakeholders General practitioner, case worker, Psychiatrist and Vendor
Organization
Preconditions The patient should have new illness
Activity Actor System
Open the page to enter story The system loads the client
side script for formal
verification of form

6INFORMATION SYSTEM DEVELOPMENT AT HEADSPACE
Case worker fill patient record
form
The system checks the
format and type of data
The patient submit the form The system does in-depth
analysis on the data
Post conditions The patient story is stored into the system and accessible by
every authorized staff
Exemption conditions The illness is not treated in the healthcare center

7INFORMATION SYSTEM DEVELOPMENT AT HEADSPACE
Bibliography:
Almutairi, A., Wheeler, J.P., Slutzky, D.L. and Lambert, J.H., 2019. Integrating Stakeholder
Mapping and Risk Scenarios to Improve Resilience of Cyber‐Physical‐Social Networks. Risk
Analysis.
Khurana, N., Chhillar, R.S. and Chhillar, U., 2016. A Novel Technique for Generation and
Optimization of Test Cases Using Use Case, Sequence, Activity Diagram and Genetic
Algorithm. JSW, 11(3), pp.242-250.