University: Headspace Information System Development Project Report

This project report details the development of an information system for Headspace, a mental health organization. The assignment begins with a stakeholder map, identifying key individuals and groups involved in the system. A questionnaire designed for psychiatrists is presented, outlining questions to gather user requirements. A use case diagram illustrates the system's functionalities, including user activity tracking, registration, data monitoring, and patient health data management. Detailed descriptions of use cases, such as storing patient cases, are provided, covering scenarios, actors, and preconditions. The report also includes a bibliography of relevant sources. The project aims to analyze and design an information system to improve the efficiency and effectiveness of mental health services provided by Headspace.

Running head: THE HEADSPACE IS DEVELOPMENT PROJECT
Information System Development Project at Headspace
Name of the Student
Name of the University

1THE HEADSPACE IS DEVELOPMENT PROJECT
Table of Contents
1 Stakeholder Map:..........................................................................................................................2
2 Questionnaire:...............................................................................................................................5
3 Use Case Diagram:.......................................................................................................................6
Bibliography:...................................................................................................................................9

2THE HEADSPACE IS DEVELOPMENT PROJECT
1 Stakeholder Map:
Figure 1: Stakeholder Mapping
(Source: Created by Author)
Stakeholder Description Type
Case worker This stakeholder records the story of the patient within the
Headspace system
Internal
Executive
Cloud
application
The head pace system need additional vendor software support to
run the operations properly
External
Application
Remote
Database
The system will store every data into a database. This database is
selected to be cloud database. The cloud database are available
External
Application

3THE HEADSPACE IS DEVELOPMENT PROJECT
from any location at any time. Cloud data stores are very scalable
Cloud
Vendor
The third party cloud service provider will offer the service of
cloud to headspace. The system and database will be
implemented and maintained by the cloud vendor. Vendor will
update security and install patches.
External
Executive
Database
Managemen
t
The headspace will collect data from the staff end. If in future
patient is included in the user list then employee and patient both
will enter data into database. These data will be processed for
creating information and knowledge. The database management
allows the system to does all that using programming functions.
Internal
Application
Share
Patient Story
There are some authorization levels in the system so that
restriction on accessing the patient story can be implemented.
The patients are allowed to see only their story. The Psychiatrists
who are treating many patients can see only the stories of patient
they are seeing.
Internal
Application
General
practitioner
The general practitioner is the one who sees the patient first. The
patient for the first time tell their story to the general practitioner.
They can accept or reject patient admission based on the health
condition of the patient.
Internal
Executive
Government Government create rules that has to be followed by Headspace External
Executive
Cyber
protocols
The cyber protocols are the set of rule developed by the state and
national government for securing and controlling the cyber
External
Application

4THE HEADSPACE IS DEVELOPMENT PROJECT
activities. The protocols are same for the all the organization.
Few protocols are different based on the industry or business
specification.
Store Patient
Case
The patient story is stored by the case worker. The system will
provide an UI to the case worker. The case worker will fill the
form of patient case along with the case description and submit
the form. The system verifies the data and store the data into
database only after every checking result is positive.
Internal
Application
Psychiatrist Psychiatrists are responsible for treating the patients. They can
access the treatment data from the system and store treatment
processes into the system too. They can access the stories of
which patients they are treating.
Internal
Executive
Psychologist These employees are only assistant of the psychiatrists. Actually
they do the job of storing data on psychiatrist’s behalf.
Internal
Executive
SLA Service Level Agreement is the agreed list of services that both
the vendor and client must meet. The SLA includes the quality of
service vendor will provide and cost of service and client
responsibilities.
External
Application
System
Analyst
The system analyst is responsible for analyzing the business
requirements and user requirements collected by the business
analyst.
Internal
Executive
2 Questionnaire:
The chosen stakeholder is Psychiatrist.

5THE HEADSPACE IS DEVELOPMENT PROJECT
The questionnaire allows the system analyst to determine what user requires from the
system. Moreover, it also answer many questions regarding what they want from it. The
questionnaire is to be done for allowing the participants to take participate in the system analysis
phase. Total ten questions have been created in this questionnaire.
Following questions are proposed for the questionnaire.
i. What is your first expectation from the system?
ii. Do you think system assistance can increase patient treatment quality?
iii. What is your suggestion on fully automatic system?
iv. Do you think able to access all the patient story is necessary?
v. Do you think every step in the treatment should be stored or just procedure name
and result?
vi. With whom you have to remotely communicate during work?
vii. Would you prefer a chat box?
viii. What is your most complex task?
ix. Which task takes the most time?
x. Is registration of all individual staff is necessary?

6THE HEADSPACE IS DEVELOPMENT PROJECT
3 Use Case Diagram:
Figure 1: The Use Case Diagram of Headspace System
(Source: Created by Author)
Brief Description of Use Cases:
i. Track User Activity: The admin can track the data access and insert of the user
along with what requests the use have made.
ii. Registration: The patient registration will be done the case worker.
iii. Monitor Data Flow: The admin can track the data transmission from one node to
another

7THE HEADSPACE IS DEVELOPMENT PROJECT
iv. Update/Record Patient Health Data: Headsapce has one employee that is
responsible for completing this task
v. Update/Record Patient Test Report: The same employee is responsible to update
the patient required test data
vi. Suggest Test: It is the duty of general practitioner to suggest essential treatment
vii. Prescription: The patient will receive prescription from the psychiatrists
viii. Patient Health Progress Report: This report will suggest how much treatment
has been one;
ix. Access Patient Story: The authorize red personnel see the story o the patient
x. Record Patient Story: The case worker does the job of storing the patient story
into the system
Fully described use case description:
Name of the use case Store Patient Case
Scenario The case worker does the job of storing the patient story into the
system
Trigger Event New patient arrived
Description The patient story is stored by the case worker. The system will
provide an UI to the case worker. The case worker will fill the
form of patient case along with the case description and submit
the form. The system verifies the data and store the data into
database only after every checking result is positive
Actors Case Worker
Related use case Access Story

8THE HEADSPACE IS DEVELOPMENT PROJECT
Stakeholders Psychiatrist, case worker, , General practitioner, Headspace, and
cloud vendor
Preconditions Patient has different illness or new patient
Post conditions The patient story will be shared to authorized people.
Flow of activities Actor System
Open system and request
story record
Process request and provide
form
Fill form and submit Check form
Enter again Form is invalid
Form valid: Stores into database
Exemption conditions The patient illness is not treated currently

9THE HEADSPACE IS DEVELOPMENT PROJECT
Bibliography:
de Sousa, T. C., Kelvin, L., Neto, C. D., & de Carvalho, C. G. N. (2017). A Formal Semantics
for Use Case Diagram Via Event-B. JSW, 12(3), 189-200. Lin, M., Lu, B. and Zhang, K., 2017, May.
Ozone Desulfurization And Denitrification System Modeling Based On UML. In 2017 7th International
Conference on Applied Science, Engineering and Technology (ICASET 2017). Atlantis Press.
Forrester, J., Cook, B., Bracken, L., Cinderby, S. and Donaldson, A., 2015. Combining participatory
mapping with Q-methodology to map stakeholder perceptions of complex environmental
problems. Applied Geography, 56, pp.199-208.
Jagtap, S., Gawde, V., Pawar, R., Shendge, S., & Avhad, P. (2016). Generate Test Cases From
UML Use Case and State Chart Diagrams. International Research Journal of Engineering and
Technology (IRJET), 3, 873-881.
Looser, S. and Wehrmeyer, W., 2015. Stakeholder mapping of CSR in Switzerland. Social
Responsibility Journal, 11(4), pp.780-830.
Nassif, A. B., Capretz, L. F., & Ho, D. (2016). Enhancing use case points estimation method
using soft computing techniques. arXiv preprint arXiv:1612.01078.4
Reed, M.S. and Curzon, R., 2015. Stakeholder mapping for the governance of biosecurity: a
literature review. Journal of Integrative Environmental Sciences, 12(1), pp.15-38.