System Analysis and Design Report for Headspace Cloud

This report offers a comprehensive system analysis of Headspace, an organization supporting youth with mental health issues. It examines the challenges of existing systems and proposes a cloud-based solution. The report delves into non-functional requirements like usability, reliability, performance, and security, crucial for a healthcare system handling sensitive patient data. It compares these with functional requirements and highlights the strengths and weaknesses of the proposed cloud solution, including data security concerns and the importance of data encryption. The report advocates for the Agile method in developing the cloud-based framework, outlining its advantages and disadvantages. References supporting the analysis are also included, providing a detailed overview of system analysis and design principles for Headspace.

Running Header: System Analysis 1
System Analysis & Design
Submitted by
Course
Professor
Date

System Analysis 2
Introduction
This report is about Headspace - the association that works with youth whose age is between 12
and 25 and suffering from mental ill health. The stress as well as anxiety are the main cause of
their mental health. The suicide cases of young people in territorial NSW between 16 to 24 age
group has been especially a cause of alarm, between Indigenous youth. The main issue was that
the young one who is suffering from some dysfunctional behavior can analyze various experts
before visiting any specialist. Every time he has to discuss his story again and again which is
very much irritating for him. It can be a General Practitioner, a clinician, or a psychiatrist.
Firstly, the patient has to go to the manager of Headspace, then after that they need to discuss the
same with medical staff. The main objective of hospital is to address the health as well as
prosperity issues of youngsters by giving a comprehensive stage of care. This would give
comfort to young people that their help will be coordinated by primary care and concentrate on
the 'ailment' as well as social incorporation and recuperation.
Non-Functional Requirements
The Non-Functional Requirements (NFR) may be characterized as the auxiliary class
prerequisite that are mainly overlooked during the development procedure of an application.
These requirements remain hidden, dominated or we can say are dismissed or overlooked. These
requirements are very hard to manage and are the most costly in specific cases. NFRs turn out to
be even more imperative with cloud framework on the grounds that the simultaneous load and
reaction idleness are more helpless utilizing public systems as compared to being used on private
systems. Comparatively much efforts are required to map NFR models into programming code.
Building up a cloud based framework with useful prerequisites just isn't sufficient to develop a

System Analysis 3
good as well as useful programming. NFRs ought to wind up noticeably an essential part of
development process.
Neglecting to address NFRs requirements in the designing process can make the product fail as
its difficulty in the usage in spite of the fact all the functional requirements are fulfilled. By
including non-functional requirements into the development process, the software application
can handle all the requirements as well as it can provide the ease of use as indicated by the
current principles. These requirements show how the framework acts and incorporates
necessities managing framework execution, operation, required assets and costs, confirmation,
documentation, security, portability as well as dependability. Fulfilling non-functional
requirements is very important to build up a cloud based application speed up the opportunity to-
the-marketing process. The main non-functional requirements are as following: (Devata, S. &
Olmsted, A., 2016).
1. Usability – The main users for the cloud based system solution will be the doctors’ team who
can view the status of particular system online. The system will be easy to adopt. The condition
of patient who really need the doctor assistance is entered into the system by doctor or medical
staff, so that information once entered can be accessed by authorized users whenever required.
(Kaur, H. & Ahamad, S., 2015).
2. Reliability - Easily accessibility, its accessibility as well as its reliability make cloud
computing system a better answer for medicinal services interoperability issues. While
frequently referred to as a potential obstacle to open cloud reception, expanded requirement for
security and dependability prompts economies of scale because of its fixed part of speculation
which is required to accomplish operational security for a reliable system. In case of hiring cloud
computing space from the supplier, it makes cloud computing a minimal cost with more security.

System Analysis 4
Coordinated Exchange empowers Headspace project to effortlessly and safely send the patient
data, like lab reports and results, patient referrals, patient condition etc. to another specialist. This
data is sent over the Internet in an encoded, secure, and reliable path from one specialist to
another. (Telecom Regulatory Authority of India, 2016).
3. Performance - The performance of the cloud framework is defined as the limit of the
framework or programming in order to process the equal transactions every time as it is
submitted to it without facing any error. Regardless of the way that the framework is functional
as well as dependable when it neglects to make productive utilization of assets like CPU cycles,
disk space etc. Its execution isn't great that is the execution of the framework isn't up to the
check. Performance of the system is that how the execution of framework can perform regardless
of in spite of the fact that the product will be able to reach its response time targets. It also finds
that how the cloud based framework in Headspace project must have the ability to scale with
incalculable exercises for each second, minute, or hour. Performance is the ability of system that
various transaction can be made at the same time whether doctor is accessing the system or
medical staff is using the system. It does not affect the database of the system. (Kaur, H. &
Ahamad, S., 2015).
4. Security – As the system which is to be implemented is based on cloud computing, therefore,
it needs to be protected from any unauthorized access or malicious threat. These type of threats
must not be allowable on the cloud based system. Security initiatives must be based on some
standards or laws like HIPPA needs to be implemented on Headspace system because patient
information is very confidential and no one has right to use it for wrong purpose. After
implementation of cloud based system, strict rules must be implemented. (Md. Rahman, M. &
Ripon, S., 2013).

System Analysis 5
Comparison between Non-Functional Requirements with Functional Requirements
As the functional requirements are based on the system, how it looks, what type of options it has,
on the other hand, non-functional requirements are focused on how to use the system, what are
the security concerns, is the system a reliable to use etc. In case of Headspace project, the
healthcare system must be focused on what type of information it must save and it is considered
as functional requirement. (Goldsmith, R., F., n.d).
NFRs have a few qualities that are different as that of FRs. The non-functional requirements are
subjective, relative, as well as interfacing. Subjective in light of the fact that they can be seen,
deciphered, and assessed contrastingly by various individuals. Relative implies that the
translation and significance of them may differ contingent upon the specific framework being
created and also the contribution of stakeholder. Cooperating in light of the fact that they have a
tendency to meddle, struggle or negate with each other. This implies accomplishing a specific
NFRs can harm or help the accomplishment of different NFRs. Dissimilar to FRs, NFRs are
more theoretical in nature. In developing a cloud based framework, clients regularly state NFRs
as general objectives, for example, convenience, the capacity to recuperate from its failure, or
great response time. Subsequently, these obscure objectives leave the issue with various
translation among partner. (Mairiza, D. & Zowghi, D., 2009).
Review of Cloud Based Solution
Strengths - The primary favorable position of cloud computing is that Headspace don't have to
pay for framework, its installation, required labor to deal with such foundation and support. In a

System Analysis 6
cloud processing framework, there's a noteworthy workload shift. The recuperation of patient
relies on the correct treatment. To get the correct treatment there must be appropriate
communication amongst patients and specialists. Coordinating distributed computing and
Headspace illuminate many issues. For better treatment consistent therapeutic supervision of
interminable patients or habitants at remote, secluded and underserved areas is required. The
innovative electronic healthcare administrations are required to be made accessible through a
system whenever, wherever and to anybody. Cloud computing can be utilized for capacity as
well as processing of gigantic medicinal records. These records will be accessible at cloud and
can be easily accessible at any place. Specialists can utilize these records to track and screen
understanding patient health status. Patients can likewise see their records. (Chowdhury, C., R.,
2014).
Weakness - By switching to cloud based solution in Headspace, the main risks can be its
security, its accessibility as well as its control to the third party shows that Headspace has
positively no influence over where the data is stored. By having trust on the cloud supplier can
be against the distinctive significance. Security as well as protection of data must be
impenetrable. Other main challenge is its information accessibility, error restrictions, disaster
reinforcement and fast response times. The unauthorized access of information brings about
serious results to the organization and more cost in its recovery and reestablishing information
and also notify the influenced people. (Lusk, R., 2012).
Data Security
The threat to compromise patient data is very high because of the inclusion of numerous groups,
devices as well as applications attracted for the control of medicinal information due to an
enhanced number of access focuses to the healthcare information of patients that is stored on

System Analysis 7
cloud foundation. It plays an imperative part in keeping up and managing control over
Headspace association medicinal information that is being stored crosswise over various remote
cloud database areas.
The confidentiality of data can be achieved by encrypting techniques and algorithms that
incorporate public key sets, symmetric key, and length of the key and administration of the key
in the situation of symmetric cipher. Security is thought to be a critical tenant of cloud
framework w.r.t HIPPA standard and the trust of the human services associations end. The
Headspace project must be given with the translucency in their operations and confirmation of
security by the cloud provider organizations. (Khattak & Abbas, 2015).
Pros of SDLC Approach
In developing a cloud based framework for Headspace project, agile method will be used. In
Agile method every development procedure appears as something else and the current strategies
should be customized all together to best suit the undertaking prerequisites. It gives strategies to
evaluate the advancement and dangers and furthermore the bearing all through the development
lifecycle. For Headspace project, agile platform will be used because it helps to reduce the
expenses as well as change of uncertainty. The main advantages of agile systems are as
following:
Advantages – 1. It understands the necessities as well as changing nature of programming
advancement by considering genuine activities regardless of their sizes.
2. It advances cooperation. Everybody engaged with the advancement process cooperate at the
same time on various territories of the product.
3. A working programming item is accessible in the early periods of the product.

System Analysis 8
4. Very few rules are applied to agile development process. It moreover requires the base
measure of assets analyzed to different models.
5. Here, planning is a willful stage and makes the procedure simple to oversee and adaptable.
(Kannan, V. & Jhajharia, S., 2014).
Disadvantages - 1. Indistinct timelines: With the majority of its focal points, the adaptability of
Agile could leave the door to delaying of project. Since the task needs to be reprioritized as well
as developed with every cycle, the time can be extended into boundlessness.
2. Expertise dependent groups: Agile must be intended for small multidisciplinary groups. It is
implied to single individual for each part (i.e., the creator).
3. High time duty: Agile is good if everyone is concentrated on the project. This is valid for
Agile on the grounds that some part of the technique is centered around dynamic group
contribution and up close and personal effort that could be tedious as compared to the
conventional approach.
4. Inclination to disregard documentation: The Agile model accentuates working programming
over far reaching documentation. (Upwork Global Inc., 2015).

System Analysis 9
References
Agile vs. Waterfall: A Side-by-Side Comparison. Upwork Global Inc. (2015). Retrieved from -
https://www.upwork.com/hiring/development/agile-vs-waterfall/
Chowdhury, C., R. (2014). A Survey of Cloud Based Health Care System. International Journal
of Innovative Research in Computer and Communication Engineering Vol. 2, Issue 8,
August 2014. Retrieved from -
https://www.ijircce.com/upload/2014/august/17_ASurvey.pdf
Consultation Paper on Cloud Computing. Telecom Regulatory Authority of India (2016).
Retrieved from -
http://www.trai.gov.in/sites/default/files/Cloud_Computing_Consultation_paper_10_june
_2016.pdf
Devata, S. & Olmsted, A. (2016). Modeling Non-Functional Requirements in Cloud Hosted
Application Software Engineering. Conference: CLOUD COMPUTING 2016, The
Seventh International Conference on Cloud Computing, GRIDs, and Virtualization Cite
this publication. Retrieved from -
https://www.researchgate.net/publication/301700605_Modeling_Non-
Functional_Requirements_in_Cloud_Hosted_Application_Software_Engineering?
enrichId=rgreq-b98a0caf80c0ec2f4aba0dbe9fd2277c-
XXX&enrichSource=Y292ZXJQYWdlOzMwMTcwMDYwNTtBUzozNTYyOTE4NTI2
ODUzMTJAMTQ2MTk1ODAwNTUyNg%3D
%3D&el=1_x_3&_esc=publicationCoverPdf

System Analysis 10
Goldsmith, R., F. (n.d). Differentiating between Functional and Nonfunctional Requirements.
Retrieved from - http://searchsoftwarequality.techtarget.com/answer/Differentiating-
between-Functional-and-Nonfunctional-Requirements
Kannan, V. & Jhajharia, S. (2014). Agile vs waterfall: A Comparative Analysis
. International Journal of Science, Engineering and Technology Research (IJSETR),
Volume 3, Issue 10, October 2014. Retrieved from -
http://ijsetr.org/wp-content/uploads/2014/10/IJSETR-VOL-3-ISSUE-10-2680-2686.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
Khattak, H., A., K. & Abbass, H. (2015). Security Concerns of Cloud-Based Healthcare
Systems: A Perspective of Moving from SingleCloud to a Multi-cloud Infrastructure.
Retrieved from -
https://www.researchgate.net/publication/282730079_Security_Concerns_of_Cloud-
Based_Healthcare_Systems_A_Perspective_of_Moving_from_Single-Cloud_to_a_Multi-
cloud_Infrastructure
Lusk, R. (2012). Cloud Computing in the Health Care Setting: Advantages and Disadvantages.
Retrieved from - http://www.enttoday.org/article/cloud-computing-in-the-health-care-
setting-advantages-and-disadvantages/
Mairiza, D. & Zowghi, D. (2009). Managing Conflicts among Non-Functional Requirements.
Retrieved from - https://opus.lib.uts.edu.au/bitstream/10453/10861/1/2009001884.pdf

System Analysis 11
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