System Design and Analysis: Headspace Case Scenario

This article discusses the system design and analysis of Headspace case scenario. It includes stakeholder design, questionnaires, and use case diagram.

Running head: SYSTEM DESIGN AND ANALYSIS
System Design and Analysis: Headspace Case Scenario
Name of the student:
Name of the university:

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Stakeholder design.......................................................................................................................2
1.1 Stakeholder map....................................................................................................................2
1.2 Stakeholder map description..................................................................................................3
2. Questionnaires.............................................................................................................................4
3. Description and diagram of the use diagram...............................................................................5
3.1 Use case model for the information system for the headspace project..................................5
3.2 Brief description of the use case diagram..............................................................................7
3.3 Illustration of combines use case diagram.............................................................................8
References......................................................................................................................................10

2SYSTEM ANALYSIS AND DESIGN
1. Stakeholder design
Figure 1: Stakeholder Map for the Headspace
(Source Created by author)
1.1 Stakeholder map
The stakeholders of this specific case scenario are differentiated into two different parts
such as external and external stakeholders. The internal system operation will be operated by the
internal stakeholders and on the other hand the external stakeholders are responsible to manage
the external activities. Professionally well trained experts are required to be hired by the system
developers and system designer to make sure that the data management system developed by the
company has all functional and operational abilities and the users can use those applications in
the accurate place.

3SYSTEM ANALYSIS AND DESIGN
1.2 Stakeholder map description
Stakeholders Interest
System developer To deliver a secured and successful system to
the employees and all stakeholders
System analyst To provide all necessary platform to the
employees associated to the project
Patients To improve their current health condition
Specialists and doctors To take the situation of the patient under
consideration and improve their health
condition
Details information store regarding the youths: In the year of 2005, the Australian
Government has invested approximately $54 Million for the successful establishment of National
Youth Mental Health Foundation. The server is capable to store all related information regarding
the youths who belongs to the age group of between 12 and 25. Not only the medical details of
the patients but also details of the specialist are also stored in the server as a recorded format.
Not only this but also the issues that the youth generation is facing are also stored in the server.
Share of important data: The record or story capturing system that has been developed
by the headspace medical center, are secured enough. Due to the high level security of the
system none of the data will be shared to any unwanted frauds. The specialists are only allowed
to access the medical status tracking report of the youth patients and none of external users can
access data from the server without permission.

4SYSTEM ANALYSIS AND DESIGN
System analysis: The system analysts are responsible to check the details application of
the system just to make sure that whether the system is meeting all the consumer’s requirements
and running appropriately or not. If the analyst fails to deliver their expected job role then the
project will fail to meet the expectation of the developers.
Legislation: With the help of the legislation the system will be able to deliver set of
regulation, norms to the employees and other associates of the company. In order to implement
the system successfully it is mandatory for the project developers to define this set of norms and
regulations.
Governance: with the help of proper project governance any project can move towards
success. The medical center can successfully deliver secured data management system to
employees who are operating the system. It is the role of the assigned business analyst and the
system developer to understand the details operation capabilities developed by the Headspace
medical company. In the healthcare industry this particular application plays active roles.
Data storage: Information storage is the other important factor that plays crucial role in
the business success. Information can be easily deleted, inserted and also updates with its
application.
2. Questionnaires
For this specific system a set of questionnaires is prepared and elaborated in the below
section:
 Who are the internal and external executives associated to the application that has
been developed by the headspace medical center?

5SYSTEM ANALYSIS AND DESIGN
 What are the different incredible profit that can be generated from the newly
evolves digitized system by Headspace?
 How the details patients and specialists information rather the credentials can kept
secured from the external attackers?
 What different challenges are there that the headspace developed system is
facing?
 For the long term sustainability of the company what are the different aspects to
be considered by the system analysts and system developers of Headspace?
 How the record keeping system developed by Headspace can operate all the
necessary applications successfully?
 What are the different discrimination strategies adopted by the company to
identify the different patient details and the specialist details?
 What are the different business driving factors using in this case for governing the
system?
 What are the different consequences that may negatively impact the staffs,
patients and the specialists also?
 For both the internal and the external stakeholders how this system beneficial
from the business perspectives?
3. Description and diagram of the use diagram
3.1 Use case model for the information system for the headspace project
After analyzing the case details it has been found that, the system should have
professional access to the capture story of the patients. Currently no such emergency department

6SYSTEM ANALYSIS AND DESIGN
is available therefore the developers are required to design a new information system which
holds the record keeping abilities are also elaborated this use case diagram. In order to assists the
system successfully this particular application and procedure is very much beneficial from the
business aspects.
Figure 2: Use case diagram for the headspace project
(Source: created by author)

7SYSTEM ANALYSIS AND DESIGN
3.2 Brief description of the use case diagram
From the above diagram the actors and their roles in the healthcare organization can be
identified easily. It is expected that if all of the members serve their job roles successfully then
the issues that may interrupt the success of the company will be completely minimized rather
resolved. For this particular case scenario the two different actors who are playing the most
crucial roles are client or patients (from the age group between 12 and 25) and the doctor or the
specialists. The clinical reminder or the knowledge services server by the company is required to
be very much effective from the business perspectives.
The followings are the actions taken by the patents are registration for the patient data,
remind of the examination data, gathering recommendations from the specialists, alert for the
different abnormal activities taking place from the patient’s end.
 The responsibilities of the patients are as follows:
 Submission of health related data to the company server
 Getting accurate examination remainders
 Collecting relative recommendations from the patients end
 Getting alert
The responsibilities of the physician or the specialists are as follows:
 Modification of the remainder conditions
 Modification on the recommendations
 Modification of the alert conditions

8SYSTEM ANALYSIS AND DESIGN
3.3 Illustration of combines use case diagram
Name of the activities Description
Actors Specialist and the patients (belongs to the age
group of between 12 and 25) are the actors for
this particular case scenario
Relevant use case Login and registration
Project stakeholders Patients, specialists, report generators and
administrators
Pre condition Before entering to the system the patients and
the specialists are required to have proper login
id and success registration. If they fail to
register themselves to the system then they will
not be able to become the pat of the system.
Simultaneously they need to have respective
login id and password as well so that they can
successfully operate and access necessary
information from the server. Proper cloud
access are also available for the system
therefore, the system developers will get
enough space for storing their credentials.
However, the other operation associated tp the
system include information access, registration,
login, system analysis and package installation.

9SYSTEM ANALYSIS AND DESIGN
Post condition All the patients and the specialists are required
to have their login id and password
accordingly. the users who do not have
successful registration will nit be able to access
data from the server.

10SYSTEM ANALYSIS AND DESIGN
References
Ahmadi, H., Nilashi, M., & Ibrahim, O. (2015). Organizational decision to adopt hospital
information system: An empirical investigation in the case of Malaysian public
hospitals. International journal of medical informatics, 84(3), 166-188.
Cummins, M., Bush, J. S., Jennings, L., & Saef, S. H. (2017). 345 Appropriateness of Trauma
Alert Activation and Validation of a Two-Tiered System for Trauma Alert Activation at
an Academic Medical Center. Annals of Emergency Medicine, 70(4), S137.
Ekblaw, A., Azaria, A., Halamka, J. D., & Lippman, A. (2016, August). A Case Study for
Blockchain in Healthcare:“MedRec” prototype for electronic health records and
medical research data. In Proceedings of IEEE open & big data conference (Vol. 13, p.
13).
Krasowski, M. D., Schriever, A., Mathur, G., Blau, J. L., Stauffer, S. L., & Ford, B. A. (2015).
Use of a data warehouse at an academic medical center for clinical pathology quality
improvement, education, and research. Journal of pathology informatics, 6.
Laudon, K. C., & Laudon, J. P. (2016). Management information system. Pearson Education
India.
Lewis, S. L., Bucher, L., Heitkemper, M. M., Harding, M. M., Kwong, J., & Roberts, D.
(2016). Medical-Surgical Nursing-E-Book: Assessment and Management of Clinical
Problems, Single Volume. Elsevier Health Sciences.

11SYSTEM ANALYSIS AND DESIGN
Nelson, L. S., Davis, S. R., Humble, R. M., Kulhavy, J., Aman, D. R., & Krasowski, M. D.
(2015). Impact of add-on laboratory testing at an academic medical center: a five year
retrospective study. BMC clinical pathology, 15(1), 11.
Slicker, K., Lane, W. G., Oyetayo, O. O., Copeland, L. A., Stock, E. M., Michel, J. B., & Erwin,
J. P. (2016). Daily cardiac catheterization procedural volume and complications at an
academic medical center. Cardiovascular diagnosis and therapy, 6(5), 446.
Tarhini, A., Arachchilage, N. A. G., & Abbasi, M. S. (2015). A critical review of theories and
models of technology adoption and acceptance in information system
research. International Journal of Technology Diffusion (IJTD), 6(4), 58-77.
Wager, K. A., Lee, F. W., & Glaser, J. P. (2017). Health care information systems: a practical
approach for health care management. John Wiley & Sons.