System Analysis and Design

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.

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

4SYSTEM ANALYSIS AND DESIGN
linked with reliability. The data stored in the system should be linked with cloud storage so that
even in times of a disaster, the records stored in the system are easily retrieved.
Performance: Evaluation of the non-functional requirement of the NewAccess system on
basis of performance is necessary as Headspace aims in delivery of a system which will show
improved and efficient performance. The performance measures of the system is considered to
be the rate at which the data is processed by a system. A low and prompt response time is
therefore the identified non-functional requirement of the information system based on the
performance of the system.
Supportability: Non-functional requirement of NewAccess is needed to be evaluated on
basis of supportability as well since the system is being designed for the use of patients. As a
non-functional requirement, the system’s maintenance should be minimal to ascertain that the
patients or their family member does not find it difficult to maintain or use the application that is
being developed.
The “+” of the FURPS+ indicates the constraints that are linked with a proposed system.
The NewAccess system mainly has design constraints as the application is to be developed in
such a manner that it would be easier to understand for the patients or their family members. The
system’s interface should be basic and easy to understand. This is the recommended step to
address the design constraint linked with NewAccess project.
2. Review of Cloud-based
Identification of the non-functional requirement, highlights the ne3ed of implementation
of the system in a secure platform. Since the health records of patients will be kept in the
information system, reviewing the cloud based solution of the system is necessary (Goyal, 2014).

5SYSTEM ANALYSIS AND DESIGN
The could environment in which the proposed NewAccess system can be developed include, the
Public cloud, private and the Hybrid cloud. considering the functionalities of the proposed
system and the security implications of each of the available cloud options, a suitable cloud
environment is chosen for the NewAccess system .
2.1. Review of Public Cloud
The public cloud environment mainly involves the cloud environment that is arranged by
third party cloud service providers. In this cloud, the entire responsibility of information
management and management of the cloud services is undertaken by the cloud provider. The
Weakness of this cloud environment is the same. The information accessibility is often provided
to the third party, which is one significant disadvantage of public cloud. However, one strength
of this cloud environment is that all the responsibilities of managing the information is up to the
provider (Sen, 2015). Furthermore, in order to make use of this cloud environment, there is no
need to own separate hardware for the cloud, which is another significant advantage, as it
reduces the cost of implementing this cloud.
Although there are quite a few advantage of making use of public cloud, it has a number
of disadvantages based on the security aspects and therefore, this cloud based solution cannot be
considered for the NewAccess project.
2.2. Review of Private Cloud
A virtualized data center with added data security are the basic characteristics of a private
cloud. Private cloud is a cloud computing model which is generally considered for a particular
organiztaion. Separate hardware optimization is needed in an organization for using private
cloud network (Coyne et al., 2018). The strength of using private cloud is that, an organization

6SYSTEM ANALYSIS AND DESIGN
can ensure effective data security. Furthermore, the accessibility of data stored in a private cloud
is limited, which adds to the extra layer of security that is needed to protect the confidential
information sources. However, one weakness of this environment is that a lot of investment is
needed for the installation of separate hardware for private cloud.
Although the use of private cloud fulfills the basic criteria of security needed to
implement a system, it is to be noted that the accessibility of the information to be stored is quite
limited. The information should not only be accessed by the physicians of Headspace but also to
other doctors that the patient might need to consult. Therefore, the private cloud environment is
not recommended for the system either. Furthermore, a lot more investment is needed if
NewAccess is to be linked with private cloud, which may not be affordable for Headspace.
2.3. Review of Hybrid Cloud
Hybrid cloud specifically merges the benefits of public cloud and private cloud (Lu et al.,
2014). The security of private cloud, which is absent in public cloud is restored in hybrid cloud.
The strength of hybrid cloud is that, it ascertain efficient data security, same as that of private
cloud. The Weakness is that its implementation cost is higher than that of public cloud platform.
2.4. Cloud Environment Chosen
A hybrid cloud is chosen for the NewAccess project mainly because it provides the
advantages of public and private cloud environment. This cloud will enable secure data access
and will not limit the accessibility of the data. This cloud is capable of performing all the need
functionalities of NewAccess and therefore, this particular cloud approach is recommended for
the Headspace project.

7SYSTEM ANALYSIS AND DESIGN
3. SDLC Approach
An appropriate system development approach is to be opted to ensure planned
implementation of the NewAccess project. The pros and cons of both predictive and adaptive
SDLC models are indicated in the following sections.
3.1. Predictive
The pros or the benefit of the model is that, this model ascertain and guarantees the
completion of the project within the estimated time. This is possible as this approach is based on
implementation of a project according to a predetermined requirements. The con or
disadvantage is that, it has no scope of implementation of changes in the project execution stage.
3.2. Adaptive
The pros or benefit of adaptive approach is that this SDLC model is open to changes and
a system can be implemented as per the feedback of the client (Shah, 2016). The disadvantage
or the cons of the approach is that a project cannot be completed within a stipulated time if the
changes to be incorporated in the project is way lot more than expected.
3.3. Recommended approach
An adaptive or agile approach is recommended for the deployment of the NewAccess
system. This is linked with the need of bringing in the changes in the application as per the
feedback of the clients. Since the requirements of the system is clear, it is expected that not much
delay will occur in the project even if an adaptive approach is chosen.
Conclusion

8SYSTEM ANALYSIS AND DESIGN
The report provides an idea of the requirements to be incorporated in the proposed
NewAcess project. The non-functional requirements of proposed system are identified based ion
FURPS+. A hybrid environment or cloud approach is recommended for the information system
that is set to be implemented using an adaptive approach. The report discusses the strengths and
the weakness of hybrid cloud along with the pros and cons of the adaptive approach chosen. The
report justifies the choice of both hybrid approach and adaptive model.

9SYSTEM ANALYSIS AND DESIGN
References
Charles, D., Gabriel, M., & Furukawa, M. F. (2014). Adoption of electronic health record
systems among US non-federal acute care hospitals: 2008-2013. ONC data brief, 16, 1-9.
Coyne, L., Dain, J., Forestier, E., Guaitani, P., Haas, R., Maestas, C. D., ... & Vollmar, C.
(2018). Ibm private, public, and hybrid cloud storage solutions. IBM Redbooks.
Darmon, D., Sauvant, R., Staccini, P., & Letrilliart, L. (2014). Which functionalities are
available in the electronic health record systems used by French general practitioners? An
assessment study of 15 systems. International journal of medical informatics, 83(1), 37-
46.
De Moor, G., Sundgren, M., Kalra, D., Schmidt, A., Dugas, M., Claerhout, B., ... & Kush, R.
(2015). Using electronic health records for clinical research: the case of the EHR4CR
project. Journal of biomedical informatics, 53, 162-173.
Goyal, S. (2014). Public vs private vs hybrid vs community-cloud computing: a critical
review. International Journal of Computer Network and Information Security, 6(3), 20.
Hu, Y., & Bai, G. (2014). A systematic literature review of cloud computing in eHealth. arXiv
preprint arXiv:1412.2494.
Lu, Y., Xu, X., & Xu, J. (2014). Development of a hybrid manufacturing cloud. Journal of
Manufacturing Systems, 33(4), 551-566.
Marceglia, S. A. R. A., Fontelo, P., Rossi, E., & Ackerman, M. J. (2015). A standards-based
architecture proposal for integrating patient mhealth apps to electronic health record
systems. Applied clinical informatics, 6(03), 488-505.

10SYSTEM ANALYSIS AND DESIGN
Pearce, C., & Bainbridge, M. (2014). A personally controlled electronic health record for
Australia. Journal of the American Medical Informatics Association, 21(4), 707-713.
Sen, J. (2015). Security and privacy issues in cloud computing. In Cloud Technology: Concepts,
Methodologies, Tools, and Applications (pp. 1585-1630). IGI Global.
Shah, U. S. (2016). An excursion to software development life cycle models: an old to ever-
growing models. ACM SIGSOFT Software Engineering Notes, 41(1), 1-6.