Headspace Newaccess Project 2022

Running head: HEADSPACE NEWACCESS PROJECT
Headspace NewAccess Project
Name of the Student:
Name of the University:

1HEADSPACE NEWACCESS PROJECT
Table of Contents
1. Introduction..................................................................................................................................2
2. Non-functional requirements.......................................................................................................2
2.1 System qualities.....................................................................................................................2
2.2 System interfaces...................................................................................................................3
2.3 User interface requirements...................................................................................................3
2.4 System constraints.................................................................................................................3
2.5 FURPS+ Functionality, Usability, Reliability, Performance and Security...........................4
3. Review of cloud based.................................................................................................................5
3.1 Strengths of cloud based solutions........................................................................................5
3.2 Weaknesses of cloud based solutions....................................................................................5
4. SDLC approach...........................................................................................................................6
4.1 Pros to approach the project using the ‘Predictive’ SDLC....................................................6
4.2 Cons to approach the project using the ‘Predictive’ SDLC...................................................6
4.3 Pros to approach the project using the ‘Adaptive’ SDLC.....................................................7
4.4 Cons to approach the project using the ‘Adaptive’ SDLC....................................................8
4.5 Recommend to either Predictive SDLC or Adaptive SDLC.................................................8
5. Conclusion...................................................................................................................................9
References......................................................................................................................................10

2HEADSPACE NEWACCESS PROJECT
1. Introduction
The project is based on “Headspace NewAccess Project” where the company is provided
mental health intervention and its target age group is between 17-25 years. Headspace is in a way
to trail a new system for targeting the persons those has higher level of depression and anxiety.
The problem that the company faces is regarding that each time the mental patients are visited
the physicians, then they are required to tell their story (Moja et al., 2015). The analyst of the
company is implemented a new system which will capture the story when at the first time the
mental patient tells his/her story. The proposed system can aim to address health as well as well-
being of young people by offering them a holistic standard. In this study, the selected system is
computerized patient record system.
This paper summarizes the non-functional necessities of the computerized patient record
scheme and appraisal a cloud based solutions to the system so that it can provide require medical
as well as healthcare services to the Headspace NewAccess. System Development Lifecycle
(SDLC) approaches are used in the study so that the business can get benefited and it can able to
record all the medical history of the mental patients into the system.
2. Non-functional requirements
2.1 System qualities
Integration of the computerized patient record system is enabled with following system
qualities such as:
 The system has ability to initiate the documents scan from the user interface.

3HEADSPACE NEWACCESS PROJECT
 There is proper synchronization of the patient data as well as clinical documents where
the data are stored such as the information related to Patient ID, Patient Name and others
(Amato et al., 2017).
 It has ability to attach the hyperlinked documents towards the patient’s medical records.
2.2 System interfaces
The computer based patient record is such a system which can reside into the system
designed to support the users by offering them accessibility for completion of accurate data,
clinical decision supports system along with patient’s reminders.
2.3 User interface requirements
The user interface is required to achieve uniformity among the healthcare by collection of
validated system designs by means of description of the qualities as well as applicable contexts.
The user interface requirements of this proposed system are that it is secured as well as
convenient (Miller et al., 2015). There is required to protect authorization of the information
from the unauthorized access, maintenance of the patient’s clinical data along with tracking of
the payments into the progress.
2.4 System constraints
The system constraints are that the proposed system has complexity in its designing as
well as there is large number of user’s requirements. There is lack of practical standards as well
as overload of the information. Due to lack of system design, there are limitations of the system
performance (Wager, Lee, & Glaser, 2017). Some of the staffs are not having technical skills as
well as knowledge to develop and use the computerized patient record system so that they do not
understand the clinical workflows.