System Analysis and Design Report: Headspace Mental Health Platform

This report provides a comprehensive system analysis and design for Headspace, a mental health organization. It begins with an executive summary and introduction, outlining the organization's goal of building a system to capture patient stories. The report then delves into non-functional requirements, including critical system qualities, system interfaces, and user interface requirements, alongside the FURPS+ model. Comparisons between functional and non-functional requirements are discussed. The report evaluates the strengths and weaknesses of cloud-based solutions for storing mental health data, considering factors like cost-effectiveness, usability, and security. Furthermore, it explores System Development Life Cycle (SDLC) approaches, comparing predictive and adaptive methodologies, specifically Waterfall and Agile, and concludes with a recommendation for the project. The report is related to the Australian mental health organization Headspace.

Running head: SYSTEM ANALYSIS AND DESIGN
SYSTEM ANALYSIS AND DESIGN
Name of the Student
Name of the University
Author’s Note

1SYSTEM ANALYSIS AND DESIGN
Executive Summary
This report is all about Headspace which is an organization that works with various youth
ranging from 12 to 25 who have a mental ill health. Depression and anxiety are most common
type of health problems. Initially they are thinking to build a system which the easily capture the
story at the first time it told. This will ultimately help the various professionals so that various
case notes and story can be easily upgraded and young person can be treated in a better way.
Use of FURPS that is functional usability, reliability, performance and security, comparison has
also been discussed. Three comparison and contraction between non-functional and functional
requirement has been discussed.

2SYSTEM ANALYSIS AND DESIGN
Table of Contents
Executive Summary.............................................................................................................1
Introduction..........................................................................................................................3
Discussion............................................................................................................................3
Non-Functional Requirements.............................................................................................4
Critical system qualities...................................................................................................4
System Interface..............................................................................................................4
User interface requirements.............................................................................................4
FURPS+...........................................................................................................................4
Non-functional requirements vs Functional Requirement...............................................5
Strengths and weaknesses of cloud based solutions............................................................6
SDLC Approach..................................................................................................................7
Pros and cons of Predictive approach..............................................................................7
Pros and cons of Adaptive approach...............................................................................8
Conclusion...........................................................................................................................8
References..........................................................................................................................10

3SYSTEM ANALYSIS AND DESIGN
Introduction
This report is all about Headspace which is an organization that works with various
youth ranging from 12 to 25 who have a mental ill health (Ameller et al.,2012). Depression and
anxiety are most common type of health problems. Initially they are thinking to build a system
which the easily capture the story at the first time it told. This will ultimately help the various
professionals so that various case notes and story can be easily upgraded and young person can
be treated in a better way.
In this report various parameters like non-functional requirement, strength and weakness
of cloud based solution, SDLC approach has been discussed in brief. Non-functional requirement
consists of various parameters like critical system qualities, interface of requirements and system
constrain has been discussed in brief.
Use of FURPS that is functional usability, reliability, performance and security,
comparison has also been discussed (Tiwari & Mishra, 2012). Three comparison and contraction
between non-functional and functional requirement has been discussed.
Discussion
Non-Functional requirement in software system engineering is nothing but software
requirement which does not describes the function of software on the contrary it stresses on the
fact that how the software will perform the work (Filieri, Ghezzi & Tamburrelli, 2012). It
focuses on certain areas like performance requirement of software, External requirements of
software, design constraint and quality of software attributes. It checks the usability and
efficiency of the entire system. It defines many system attributes like security, reliability,
performance, maintainability, scalability and usability.

4SYSTEM ANALYSIS AND DESIGN
Non-Functional Requirements
Critical system qualities
Critical system can be either complex integrated system or small subsystems which refers
to the quality and performance of which are critical and performance of a large system.
System Interface
The ultimate goal of system is to transform input into output. Inputs must come from any
system that generally comes from other system and similar the output is generally made into
other system and so interface can be defined as the collection of inputs and outputs of a system.
User interface requirements
A user interface is nothing but a part of physical product, system or designed software
which shows the detail implementation of product, system and requirements of software. Design
of user interface in one of the biggest activity that is being carried out in the definition of
requirement.
FURPS+
FRUPS many stands for Functionality, Usability, Reliability, Performance, and
supportability which is provided over the period of time. FURPS is a useful technique which is
required to check the basic requirements after making a clear view of the needs of the client. F in
the FRUPS checks the features of different product that are familiar with the business domain of
the solution that is developed. Functional requirement includes certain function like auditing,
licensing, reporting, security and management of the system. Usability focuses on certain areas
like capturing and relating the requirements on the interface issue of user. It emphsizes on certain
areas like accessibility, interface and consistency (Ameller et al.,2012). Performance involves
certain things like information through system, response time of given system, recovery and start

5SYSTEM ANALYSIS AND DESIGN
up time. Supportability in the part where a number of other requirements such as testability,
adaptability and many other factors. The plus sign in FRUPs refers other parameters like design,
implementation, interface and physical constraints.
Non-functional requirements vs Functional Requirement
Functional requirement specifies the function of a system or in other words it describes
the particular requirement of function of a system when certain conditions are meet (Tuteja &
Dubey, 2012). Typical functional requirement includes business rules, administrative function,
authentication, authorization, external interference and historical data.
Non-functional requirements specify on the system can perform a given function. Non-
Functional requirement describes the behavior of a system and limits its functionality
(Blackwell, Lucas & Clark, 2014). Nonfunctional requirement focuses on certain area that is
performance, capability, maintainability, regulation and data integrity.
Strengths and weaknesses of cloud based solutions
There are certain advantages for using cloud computing for the storage of mental health
data for this organization that is headspace (Bibi, Katsaros & Bozanis,2012). Headspace is an
organization that works for the youth whose age ranges from 12 to 25 and they experience a
mental illness. The advantages are cost effective, usability, bandwidth, accessibility, data
recovery during disaster. There are certain disadvantages also like usability, Bandwidth,
accessibility, data security and software. Now the advantages will be discussed in brief that
usability of cloud storage provides a wonderful option to the various user to easily drag and drop
various files between cloud storage and their local storage (Khan et al., 2016). Cloud storage
provides a wonderful option like various employees of head space can easily email the link of the

6SYSTEM ANALYSIS AND DESIGN
patient file to the respective professionals and therefore it reduces the burden of uploading and
sending the whole file. Employees of this organization can easily access the required patient file
from any device through an internet connection. Cloud storage provide a option of disaster
recovery in which it can act as backup plan in case of emergency for this organization that is
headspace. Cloud storage will be cost effective for headspace as cloud storage cost about three
cents per gigabyte for internal storage of data and there is no requirement of internal power for
the storage of information.
On the contrary it has some disadvantages of using cloud storage that is the employees of
Headspace must be careful about the fact while using drag and drop option as this will
permanently move the document from original location to cloud storage location (Balaji &
Murugaiyan, 2012). In this way some important files of various patients can be easily lost.
Headspace must look for cloud service providers that provides unlimited bandwidth as there are
certain cloud service provider that charges a certain amount of money if they cross the given
limit. The biggest disadvantage that this organization will face is that it cannot access important
files on cloud storage without a proper internet connection (Chung, Nixon & Mylopoulos, 2012).
Employees of Headspace need certain software if they want to access important files through
multiple devices. Security of data is an important factor as there are many cases of data breach in
cloud storage on the contrary cloud storage promises to provide security of important data.
Data can be easily stored and can be kept secure in cloud storage and if their certain
third-party products then it will not affect the laws of Australia as there are certain third-party
application that will protect the given data from authorized use, reproduction, external
distribution or publication and it will also prevent the usage of data which is manly used for
identifying person. Various third-party application ensures that the data which is stored on cloud

7SYSTEM ANALYSIS AND DESIGN
is only accessible to more than two individual or employees within provided health network
(PHN).
SDLC Approach
SDLC stands for System Development Life Cycle or Project life cycle and it consists of
eight steps that is initiation, planning, analysis, design, construction, QA testing implementation,
support. Predictive approach to a given project are those in which an individual can assume the
steps and the user is needed to take and after that a plan is made on it (Elliott, Huizinga &
Menard, 2012). The most common type of predictive method is Waterfall and its pros and cons
has been discussed below. Predictive approach checks on sequential planning of phases and then
execution of it with little or no overlap. Adaptive approach is related to the scope of project it
can change as per the needs or requirement of the project. The most common type of adaptive
approach is Agile.
Pros and cons of Predictive approach
Pros of Predictive approach is that Waterfall model are on managed projects waterfall
model can be proved to provide more confidence to team to the team members and it reduces the
burden of team members to be co-located (Mahalakshmi & Sundararajan, 2013). Waterfall
model can be useful for managing interface and dependencies which are merely present outside
the development of product as this model have certain tools for managing the models.
Cons of Predictive approach is that many organization and people cannot find the
requirements of the project and made assumptions may be flawed (Modi et al., 2013). Risk in
this approach can be higher in waterfall model as it has invalid assumptions in it. Waterfall

8SYSTEM ANALYSIS AND DESIGN
projects are made up of teams within team and this factor can be considered to be the major
disadvantage of Waterfall.
Pros and cons of Adaptive approach
Pros of adaptive approach is that agile has some practices that are suitable of the
developers for current development. Agile model helps the developers and clients which
ultimately helps in getting proper feedback (Ameller et al.,2012). This model help is reducing the
silos which exits in teams working on the project and which can damage the projects.
Cons of adaptive approach is that although agile model is very simple to understand on
the contrary it is very hard at first attempt (O’Driscoll, Daugelaite & Sleator, 2013). This model
has less prediction of what is delivered as the end result. Agile model requires a high level of
collaboration and regular communication between developers and user of the product.
From the above discussion it can be stated that Predictive approach of SDLC is better for
the given project (Rao, Sasidhar & Kumar, 2012). Predictive approach of SDLC that is waterfall
model is better for this given project. Waterfall model is good for any project related to
information technology and this is IT of Headspace organization
Conclusion
From the above discussion it can be concluded that the report emphasizes on non-
functional requirement, review of cloud based solution and approach of SDLC. The beginning of
the report is all about qualities of critical system, interface of system, user interface
requirements, FRUPs and comparison of non-functional and functional requirement. The next
part of the report is about the strength and weakness of cloud based solution and sensitive nature
of mental health data and its security has been discussed. The last part of the report provides a

9SYSTEM ANALYSIS AND DESIGN
brief description about the pros and cons using predictive SDLC, pros and cons of Adaptive
SDLC and proper recommendation for this project is also provided. All the above-mentioned
factors are being related to the Australian mental health organization that is Headspace.

10SYSTEM ANALYSIS AND DESIGN
References
Ameller, D., Ayala, C., Cabot, J., & Franch, X. (2012, September). How do software architects
consider non-functional requirements: An exploratory study? In Requirements
Engineering Conference (RE), 2012 20th IEEE International (pp. 41-50). IEEE.
Balaji, S., & Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A comparative study
on SDLC. International Journal of Information Technology and Business
Management, 2(1), 26-30.
Bibi, S., Katsaros, D., & Bozanis, P. (2012). Business application acquisition: on-premise or
SaaS-based solutions?. IEEE software, 29(3), 86-93.
Blackwell, D. L., Lucas, J. W., & Clarke, T. C. (2014). Summary health statistics for US adults:
national health interview survey, 2012. Vital and health statistics. Series 10, Data from
the National Health Survey, (260), 1-161.
Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2012). Non-functional requirements in
software engineering (Vol. 5). Springer Science & Business Media.
Elliott, D. S., Huizinga, D., & Menard, S. (2012). Multiple problem youth: Delinquency,
substance use, and mental health problems. Springer Science & Business Media.
Filieri, A., Ghezzi, C., & Tamburrelli, G. (2012). A formal approach to adaptive software:
continuous assurance of non-functional requirements. Formal Aspects of
Computing, 24(2), 163-186.

11SYSTEM ANALYSIS AND DESIGN
Khan, F., Jan, S. R., Tahir, M., Khan, S., & Ullah, F. (2016). Survey: Dealing Non-Functional
Requirements at Architecture Level. VFAST Transactions on Software Engineering, 9(2),
7-13.
Mahalakshmi, M., & Sundararajan, M. (2013). Traditional SDLC Vs Scrum Methodology–A
Comparative Study. International Journal of Emerging Technology and Advanced
Engineering, 3(6), 192-196.
Modi, C., Patel, D., Borisaniya, B., Patel, H., Patel, A., & Rajarajan, M. (2013). A survey of
intrusion detection techniques in cloud. Journal of Network and Computer
Applications, 36(1), 42-57.
O’Driscoll, A., Daugelaite, J., & Sleator, R. D. (2013). ‘Big data’, Hadoop and cloud computing
in genomics. Journal of biomedical informatics, 46(5), 774-781.
Rao, N. M., Sasidhar, C., & Kumar, V. S. (2012). Cloud computing through mobile-
learning. arXiv preprint arXiv:1204.1594.
Tiwari, P. K., & Mishra, B. (2012). Cloud computing security issues, challenges and
solution. International Journal of Emerging Technology and Advanced Engineering, 2(8),
306-310.
Tuteja, M., & Dubey, G. (2012). A research study on importance of testing and quality assurance
in software development life cycle (SDLC) models. International Journal of Soft
Computing and Engineering (IJSCE), 2(3), 251-257.