System Analysis and Design

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of Student
Name of University
Author Note

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Introduction..........................................................................................................................2
1. Non-Functional Requirements: FURPS+........................................................................2
2. Review of Cloud-based....................................................................................................4
2.1. Review of Public Cloud............................................................................................5
2.2. Review of Private Cloud...........................................................................................5
2.3. Review of Hybrid Cloud...........................................................................................6
2.4. Cloud Environment Chosen......................................................................................6
3. SDLC Approach..............................................................................................................7
3.1. Predictive..................................................................................................................7
3.2. Adaptive....................................................................................................................7
3.3. Recommended approach...........................................................................................7
Conclusion...........................................................................................................................7
References............................................................................................................................9

2SYSTEM ANALYSIS AND DESIGN
Introduction
This requirements report is based on the Headspace project “NewAccess”. The project
that aims in delivering an information system that has the capability of securely storing the data
of the patients. This project is mainly proposed as a solution to the problems that patients who
visit a number of different physicians for medical help face while repeating their health issues.
The proposed NewAccess system has the capability of eliminating all these problems. The vision
document for the proposed system is already prepared and approved. This report aims in
discussing the suitable approach of cloud in which the system can be implemented (Hu & Bai,
2014). The non-functional requirements of the proposed NewAccess project will be discussed in
this report to understand the main functionalities of the system. The requirements report will
further identify the system development methodology that can be used to develop and deliver the
system. The identification of the system’s non-functional requirements on basis of FURPS+ will
enable a better understanding of the functionality of the system that is proposed (Pearce &
Bainbridge, 2014). The detailed requirements of NewAccess project by Headspace is identified
in the following paragraphs.
1. Non-Functional Requirements: FURPS+
A system’s non-functional requirements mainly define its attributes, constraints and the
restrictions related to the design and development of the system. The project by Headspace is a
sensitive project, which increases the need of accurately identifying the attributes and the
constraints of the project (De Moor et al., 2015). Accurate identification of these requirements
linked with the system will enable a better understanding of the approach that can be considered
for better development and implementation of a system. The main non-functional requirements

3SYSTEM ANALYSIS AND DESIGN
of the NewAcess project is particular based on the critical system qualities, system interfaces the
constraints and the user interface requirements linked with the NewAccess project.
Functionality: a system’s function sets out to be one key considerations prior to the
development of an information system. The clients of the NewAccess project are mainly the
individuals having mental health issues and therefore, the systems’ functionality is a critical
constraint of the project (Charles, Gabriel & Furukawa, 2014). It is anticipated that the system
will be able to provide an effective functionality and improved performance. The system is
expected to involve and “auto update” feature that will help the patients to maintain their records
in an easier manner and will enhance the system’s functionality as well.
Usability: The usability of an information system is another critical constraint or
considerations linked with system implementation. The NewAccess system will mainly be used
by the patients having mental health issue and therefore a lot of focus is needed to be provided
on the usability of the information system (Marceglia et al., 2015). The information system’s
interface should be easy to understand and should incorporate the use of large icons so that it
becomes easier for the patients and their families to understand the usability of the application.
These are the key non-functional requirements linked with usability of the system is to be
incorporated in the system that is being developed.
Reliability: The non-functional requirement of the NewAccess project by Headspace
should consider the attribute of reliability and the system is being designed for the patients
having mental health issues (Darmon et al., 2014). The NewAccess will help the patients and
their families to store the data and the records of the patients in a secure manner, so that it can be
easily accessed when required. The system’s nonfunctional requirement, should therefore be