System Analysis

Running head: SYSTEM ANALYSIS
System Analysis
Name of Student-
Name of University-
Author’s Note-

1SYSTEM ANALYSIS
Table of Contents
Introduction......................................................................................................................................2
1. Non-Functional Requirements.....................................................................................................2
1.1. Functionality.........................................................................................................................3
1.2. Usability................................................................................................................................3
1.3. Reliability.............................................................................................................................3
1.4. Performance..........................................................................................................................4
1.5. Security.................................................................................................................................4
2. Cloud Based Solution..................................................................................................................5
2.1. Advantages of Hybrid Cloud................................................................................................5
2.2. Disadvantages of Hybrid Cloud............................................................................................6
3. SDLC Approach..........................................................................................................................6
3.1. Predictive SDLC...................................................................................................................6
3.2. Adaptive SDLC....................................................................................................................7
3.3. Recommended Approach......................................................................................................8
Conclusion.......................................................................................................................................8
References........................................................................................................................................9

2SYSTEM ANALYSIS
Introduction
The case that is taken in this report is the new information system of NewAccess. The
NewAccess is mental health institution of Headspace. The main aim of NewAccess is to store the
records as well as all the stories of the patients when they come to Headspace for the first time.
Headspace deals with the mentally ill patients. The new system of Headspace needs to keep all
those previous data of the patients so that they their doctors can get all the data related to their
health and can also recommend medicines to all patients (Fenton & Bieman, 2014). With the
developed system of NewAccess which is proposed in this report, all the issues that are involved
in the treatment process can be mitigated. The mentally ill patients can get treatment from
Headspace. With the treatment process that the Headspace is planning to provide, the patients
gets advantage as they do not have to explain all their problem every time they visit the doctor
and they have to say very little for the second visit.
This report describes the new system of Headspace known as NewAccess by identifying
as well as discussing non-functional requirements that are involved in the system. Moreover, this
report also discusses a cloud approach that can be selected for evaluating the project. The cloud
approach states the weakness as well as strength of the new system in Headspace. There is also a
SDLC approach that is described for implementing this project. The SDLC approach is further
categorized into two categories that are explained briefly in this report.
1. Non-Functional Requirements
For developing a system, many non-functional requirements are to be considered. All
those non-functional requirements are to be considered for implementing the NewAccess system
in Headspace. The non-functional requirements involved in a system mainly specifies many

3SYSTEM ANALYSIS
criteria that are used for judging all operations for the system that is being developed in the
system (Kerzner & Kerzner, 2017). The non-functional requirements are also known as quality
attributes that are implemented in the system. Non-functional requirement needed for system of
NewAccess is mainly evaluated with FURPS+. The FURPS+ contains functionality, usability,
reliability, performance, as well as the security that are to be implemented in the system.
1.1. Functionality
The first feature that is to be implemented is functionality. This functionality is an
important aspect while implementing a system (Hatley & Pirbhai, 2013). All the requirements
stated in the system should function properly according to the functionality feature of FURPS+.
It is very important for enforcing some the features which helps to improve functionality of the
system.
1.2. Usability
The second feature of FURPS+ is usability. This usability is one of the most important
non-functional requirement while developing a system. The system of NewAccess should be
usable to all the users who tries to use the system (Highsmith, 2013). The interface of the system
should be user friendly so that the user can efficiently use it. The professionals who are involved
with Headspace should use the system with easy. The patients should also be able to use the
system effectively.
1.3. Reliability
The third feature that is involved in FURPS+ is reliability. The application of NewAccess
that is to be developed is to be reliable so that all the data that are stored in the system is secured
and user feels reliable to keep their personal data in the system. The users are also to be key