Headspace Project 10: Cloud Based System Analysis and Design

This report provides a system analysis and design for Headspace, focusing on a cloud-based solution. It explores non-functional requirements such as usability, reliability, performance, and security, crucial for healthcare applications. The analysis highlights the strengths and weaknesses of cloud computing in this context, considering financial and operational aspects. The report delves into the Software Development Life Cycle (SDLC) approach and predictive modeling, offering recommendations for enhancing the system. It emphasizes the importance of data security, especially concerning patient information, and suggests adaptive approaches to handle changing requirements. The analysis also addresses the differences between functional and non-functional requirements, providing a comprehensive overview of the system's design and implementation challenges.

Headspace Project 1
System Analysis and Design
(Cloud Based Solution)
Submitted By
Course
Professor
Date

Headspace Project 2
Introduction
The rise of distributed computing prompts new improvements for various application domains.
This can be possible in case of healthcare organization subsequently making it worth to examine
the pertinent perspective as well as insights. In this scenario, we have discussed about modern
development with front line advancements in the cloud computing based frameworks for the
healthcare. The demand of cloud computing enhanced the consideration and it represents a
standout amongst the most vital research in the field of science and data frameworks. It alludes
to both the applications delivered as administrations over the Internet, hardware as well as
software frameworks in the data centers which give those administrations. Cloud is presently
observed as a substantial procedure and particular applications based on these innovations have
turned out to be across the board. Healthcare, as with some other administration operation, has
been affected by the cloud framework with the challenges as well as benefits. According to the
given scenario, my task is to develop system analysis and development report regarding its
challenges, advantages etc. (Stantchev & Palacious, 2014).
Non – Functional (FURP +) Requirements
Non-functional requirements are subjective necessities that mainly add to the development of the
framework: response speed performance, its reusability, unwavering quality, or accessibility of
the cloud based framework. These capacities are intended for acknowledging necessities since
framework advancements are perceived to be as effective just if such useful prerequisites are
obviously characterized. In spite of the objectives as well as foundation of the framework
improvement are composed and shared among partners, a few functions are there which may not
be used when they are delivered. Moreover, if a few traits of the capacities are not plainly
characterized, the framework won't accomplish anticipated levels of execution or ease of use and

Headspace Project 3
such configuration would need to be reassessed. Characterizing NFRs in the early outline stage
will address countless issues in the following stages. Despite the fact that, Headspace
organization has, experience, developed some NFRs, the scholarly community has been
attempting to set up a model to clarify the values of NFRs. (Hosono & Hara, 2010).
NFRs are the imperatives of the framework. These requirements are for the development process
as well as its arrangement process. The quality necessities are otherwise called nonfunctional
prerequisite. The specific qualities of the framework must have like precision, execution, its
easiness, modifiability, wellbeing, execution, dependability, security, adaptability etc. NFR are
dependably associated with its functional necessity. NFRs must be organized from the
perspective of stakeholder. Therefore, it ought to be first inspired from the partners. So the
elicitation strategy must be planned in such a way that it will connect intimately with the
partners. (Md. Rahman & Ripon, 2013).
1. Usability
The interface ought to be simple to figure out how to utilize and must be easy. The non-
functional requirements like usability for the cloud based interface configuration should be able
to support the accompanying from the perspective of its essential users:
Effectiveness of utilization: objectives are anything but difficult to finish rapidly and with few or
no client mistakes.
Intuitiveness: the framework must be simple to understand and explore; headings, and the error
messages which displays must be easy to understand.
Less workload: The cloud healthcare framework for Headspace project must be simple to utilize, instead
of frustrating, requesting and disappointing. (Usability & Web Design Services, 2015).

Headspace Project 4
The cloud based framework for Headspace project must have graphical UI as well as it must be able to
give instructive errors. The characteristics of the usability that may be measured can be learning time it
brings up the time which is required to take in the application, the errors that occur during working with
the typical speed moreover the similarity of the customer to quantify the framework i.e. the user
satisfaction in using the system. The cloud framework should be simple and easy to utilize and access.
The patient's condition who truly require the specialist help to get rid of their depression state must be
saved into the framework by specialist or medicinal staff, with the goal that data once entered can be
accessed by approved clients at whatever point required. (Kaur & Ahamad, 2015).
2. Reliability
Reliability can be defined as the limit of the product to keep up its execution over the time. It suggests
working of framework during its top hours. A powerful framework is one which has the ability to deal
with the errors and viruses without any type of failure i.e. how easily it solves the errors in light of
information or dealing with while working with the system, and if the Headspace project cloud
framework is robust it must also be reliable. The framework needs to be self-independent, steady as well
as complete. The cloud based framework must be enough reliable to safely transfer patient data from
doctor to medical staff who is attending the patient. (Kaur & Ahamad, 2015).
3. Performance
The NFR requirement can be defined as the limit of the framework or programming to process the various
transactions during each second as it is submitted without any type of error or failure. Notwithstanding
the way that the framework is useful and solid in the event that it neglects to make effective utilization of
assets like CPU cycles, disk space and also its execution isn't great that is the performance of the cloud
based framework isn't up to the point. This NFR requirement is about how well the framework can work
regardless of whether the product must have the ability for its response time targets. It measures that how
successfully the product will have the ability to scale with innumerable exercises for each second, minute,

Headspace Project 5
or hour. The internet managing an account framework is a multi-client framework, which infers
customers can get to the framework at the same time and the framework will work precisely and capably.
In case of Headspace project, many transactions must be possible at the same time when doctor is
monitoring a particular patient record and on the same time medical staff is updating the information of
that patient. (Kaur & Ahamad, 2015).
4. Security
Security is confirmation that only authorized people or elements can access the patients' information. The
illegitimate access as well as the data theft by staff in main reason for data leakage. Another issue which
can arise is unapproved access as well as malevolent assaults from the third party. Therefore, the
encryption, recognizable proof as well as access control of patient health information must be critical
requirement for the patient data safety.
The patient wellbeing data incorporates individual data, subtle elements of therapeutic history, side
effects, medications, and even the family wellbeing history. It is vital to guarantee that the patients can
approve precisely who can see the common wellbeing data as well as for what purposes. All the data
produced by a patient is not at a sensitive level. Information division may give a technique to secure
particular segments of wellbeing data while offering decisions to patients, and standing necessities of
legitimate. The technical ideas as well as meaning of sensitive data must be tended to while fragmenting
information. (Hu, Y., 2014).
Difference between Functional & Non-Functional Requirements
The functional requirements (FR) are commonly known as the highlights or the outline for which the
system may have a menu structure, like identification of authorized user and password, which service
needs to be used etc. If there should arise an occurrence of Headspace venture, the human services
framework must be centered on what sort of data it must spare and it is considered as practical
prerequisite.

Headspace Project 6
Non-functional requirements are traits that includes execution levels, its security, and some other utilities
like how easy it is to use, unwavering quality, as well as its accessibility. Constantly, the requirements get
framed in how the cloud framework is required to work and also can dismiss other components. When
these factors are not tended to enough, apparently legitimate item/framework working in actuality
neglects for working. Eg: a framework may distinguish its customers in moderate, insecure, as well as
difficult to use some key points that it can cause some errors that make data problematic. (Goldsmith,
2017).
Strengths of Cloud Based Solution
The financial pros of the cloud computing are at large extent as the cloud computing provides cost
adaptability as well as some potential for the reduced prices. Overwhelming capital use must be avoided,
as the IT resources are hired on demand according to the requirement and paid for as its operating cost.
Additionally, the staff resources must be required to maintain the organization’s IT resources that are
included in the price of cloud computing. In this manner, the need for extra healthcare supplier skilled
staff assets as well as related expenses needs to be reduced during usage of cloud computing. From the
operational perspective, cloud administrations offer versatility and the capacity to change in accordance
with its request. This system may have better security as well as protection for wellbeing information.
Cloud suppliers are considered as exceptionally secure and ensured against protected risks utilizing
managerial, physical and specialized techniques actualized and kept up by master proficient staff.
It offers advanced security controls, including information encryption and better access controls and
access logging. Medicinal frameworks assembled by using cloud administrations can give online access
to information, keeping away from the requirement to save the data. (Cloud Standards Customer Council,
2017).
Weakness of Cloud Based Solution

Headspace Project 7
A wide range of safety efforts, like hardware, programming, HR, as well as administration costs, are not
costly when it runs on very large scale. Most cloud suppliers reproduce customer data in various areas.
This can enhance data redundancy and can be a reason for system failure. The cloud supplier must
reallocate security assets for separating, or encryption with a specific end goal to enhance support for
security measures. As we know that the cloud computing is available to many clients. But in case when
supplier can't provide the sufficient resources, it may be a reason for security threats. In the numerous
occupancies condition, the hardware devices can be reused. This can be a major reason for threat to the
patient data. (Mork & Kimura, 2011).
Security is believed to be a basic occupant of cloud system w.r.t HIPPA standard and the trust of the
Headspace. The Headspace venture must be given with the translucency in their operations and
affirmation of security by the cloud supplier associations.
SDLC Approach
The predictive models are mainly used to analyze data as well as its outline patterns for understanding
client requirements and the system that they want while likewise distinguishing potential future
opportunities as well as risks.
Advantages - In its different structures—predictive modeling, decision analysis and improvement, data
transaction, as well as prescient pursuit which could be connected for business methodologies as well as
is the main player in marketing processes. These systems can provide managers as well as officials with
better decision making to impact upselling, sales and income anticipating, fabricating streamlining, and
even new item advancement.
Disadvantages -

Headspace Project 8
The main desire of Headspace is to use information decision making requirement to considerable
important information from the scope of its activities, and also big data is difficult to find. In spite of the
possibility that an organization has enough information, critics compete in suspecting human behaviors as
well as algorithms neglect to consider elements like changing condition to states of mind to connections
which may affect client acquiring designs. (Georgetown University, 2017).
Recommendations
Prediction modelling utilizes systems like AI to make a forecast profile (calculation) from past people.
The model is then "delivered" with the goal that another individual can get an expectation in a flash for
whatever the need is for the patient. Predictive examination enhances the exactness of determinations.
This analysis provides doctors with answers they are looking for singular patients. (Linda, A., 2014).
Adaptive approach is the approach that finds project more flexible as well as adaptable for changing the
requirements in case of progression of cloud based system. This approach is utilized when the correct
necessities or requirements of the clients are not surely known. A more adaptable approach is
requirements that enables the arrangement to be altered as the task advances. In case of Headspace
project, predictive approach will be better option. (System Analysis & Design in a changing world, n.d).

Headspace Project 9
References
Chapter 8 - Approaches to System Development. System Analysis & Design in a changing world, sixth
edition. Retrieved from -
http://web.cerritos.edu/dwhitney/SitePages/CIS201/LectureNotesOnTalonNet/
Chapter08Lecture.pdf
Goldsmith, R., F. (2017). Differentiating between Functional and Nonfunctional Requirements. Retrieved
from - http://searchsoftwarequality.techtarget.com/answer/Differentiating-between-Functional-
and-Nonfunctional-Requirements.
Hosono, S. & Hara, T. (2010). Prioritizing Service Functions with Non-Functional Requirements.
Retrieved from - http://www.ep.liu.se/ecp/077/017/ecp10077017.pdf
Hu, Y. (2014). Electronic Medical Records (EMR). Retrieved from -
http://www.bth.se/people/yhx.nsf/attachments/Lic%20(V5)_pdf/$file/Lic%20(V5).pdf
Impact of Cloud Computing on Healthcare Version 2.0. Cloud Standards Customer Council (2017).
Retrieved from - http://www.cloud-council.org/deliverables/CSCC-Impact-of-Cloud-Computing-
on-Healthcare.pdf
Kaur, H. & Ahamad, S. (2015). A Case Study upon Non-functional Requirements of Online Banking
System. International Journal of Computer Applications Technology and Research Volume 4–
Issue 4, 220 - 225, 2015, ISSN:- 2319–8656. Retrieved from -
http://ijcat.com/archives/volume4/issue4/ijcatr04041002.pdf

Headspace Project 10
Linda, A. (2014). Seven ways predictive analytics can improve healthcare. Retrieved from -
https://www.elsevier.com/connect/seven-ways-predictive-analytics-can-improve-healthcare
Md. Rahman, M. & Ripon, S. (2013). Elicitation and Modeling Non-Functional Requirements – A POS
Case Study. International Journal of Future Computer and Communication, Vol. 2, No. 5,
October 2013. Retrieved from - http://www.ijfcc.org/papers/211-S037.pdf
Mork, P. & Kimura, E. (2011). Opportunities and Challenges of Cloud Computing to Improve Health
Care Services. Journal Med Internet Res. 2011 Jul-Sep; 13(3). Retrieved from -
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3222190/
Pros and Cons of Predictive Analysis. Georgetown University (2017). Retrieved from -
http://scsonline.georgetown.edu/programs/masters-technology-management/resources/pros-cons-
predictive-analysis
Requirements Specification. Usability & Web Design Services (2015). Retrieved from -
http://www.usabilityfirst.com/about-usability/requirements-specification
Stantchev, V. & Palacious, R., C. (2014). Cloud Computing Based Systems for Healthcare. The Scientific
World Journal Volume 2014, Article ID 692619, 2 pages