University: ITC 548 System Analysis Report on Cloud Solutions and SDLC

This report presents a system analysis for the NewAccess project, focusing on the secure storage of mental health patient information. It begins by identifying non-functional requirements based on the FURPS+ model, including functionality, usability, reliability, performance, and supportability. The report then evaluates cloud-based solutions, recommending a hybrid cloud approach for its balance of security and cost-effectiveness. It details the advantages (scalability, security) and disadvantages (cost, complexity) of this choice. Finally, the report explores System Development Life Cycle (SDLC) models, recommending an adaptive SDLC approach to accommodate potential changes during the project's implementation. The analysis underscores the importance of monitoring, control, and secure data storage in the context of this sensitive project, contributing to the development of an information system designed to address the challenges faced by mental health patients.

Running head: ITC 548 SYSTEM ANALYSIS
ITC 548 System Analysis
Name of Student
Name of University
Author Note

1ITC 548 SYSTEM 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. Supportability...........................................................................................................4
2. Review of cloud-based solution to be deployed..............................................................4
2.1. Advantages of Hybrid cloud.....................................................................................6
2.2. Disadvantages of Hybrid cloud................................................................................6
3. SDLC approach...............................................................................................................7
3.1. Predictive SDLC.......................................................................................................7
3.2. Adaptive SDLC........................................................................................................7
3.3. Recommendations.....................................................................................................7
Conclusion...........................................................................................................................8
References............................................................................................................................9

2ITC 548 SYSTEM ANALYSIS
Introduction
The NewAccess project is associated with the development of an information system that
aims in secure storage of the health information of the patients with mental health issues. The
proposed project aims in storing data of patients in order to reduce the issues faced by those
patients while retelling their story. The funding for development of this information system is
already proposed therefore the viability of making use cloud storage and solution for the system
will be judged (King et al., 2014). The report will be evaluating the nonfunctional requirements
of system proposed. The appropriate cloud based solution that can help in effective
implementation of the project will be discussed in this report. The system’s non-functional
requirements will be evaluated on basis of FURPS+ acronym to ensure that the functionalities
that are being proposed for the system implicates the usability, reliability, performance and the
security of a system. The report will evaluate the cloud system that will be useful for this
particular system (Meeks et al., 2014). The report reviews the cloud approaches and the SDLC
models that can be used in development of this NewAccess information system.
1. Non Functional Requirements
The non-functional requirement that is to be identified for the NewAccess system is
based on usability, reliability, performance and the security needs of a system. It is quite
essential to identify the systems’ nonfunctional specifications as it helps in identification of the
system’s operation. The system’s non-functional requirement provides an idea of attributes that
the proposed system will involve. The identified requirements of the proposed system provides
an idea of the main attributes of the system. The FURPS represents the model of classifying a
software on basis of the quality attributes.

3ITC 548 SYSTEM ANALYSIS
1.1. Functionality
The functionality of the proposed project represents the vital feature of the system that is
mainly familiar with the business domain of the solution that is being developed. The
functionality of the system is mainly technical oriented. The main nonfunctional requirement of
the proposed system based on its functionality includes improved performance. The proposed
system should be able to provide a high performance of speedy data processing and very less
response time.
1.2. Usability
The usability feature of a system incorporates is one vital nonfunctional requirement of a
project. Since the project will be used both by the doctors and the patients, it is essential to
develop a system having effective usability. The requirement of usability of the proposed project
includes development of a system that will ensure effective report generation that will in turn
improve the usability of the system. Therefore, continuous report generation of the medical
health of patients is an important nonfunctional requirement of the proposed system.
1.3. Reliability
Reliability is associated with one of the most significant nonfunctional requirement
particularly because this system deals with storing data of the patients. The system that is being
developed should be reliable as it is related with the management and data storage of the
healthcare patients. The system’s reliability can be enhanced by making use of encryption to
increase the data security.
1.4. Performance

4ITC 548 SYSTEM ANALYSIS
The non-functional requirement of the system proposed should be associated with the
system’s performance measure. The system’s performance is to be measured on basis of the
output that the system is providing. The nonfunctional requirement of the proposed system
related to the performance involves a good data processing speed. The data obtained from the
system should provide a high level of accuracy for ensuring that the system that is being
developed is able to provide an improved performance and accuracy in the data storage.
1.5. Supportability
The supportability of the system tend to specify a number of requirements associated
with the testability, adaptability and compatibility of the system. Since the system that is being
proposed is related to the treatment of the mental patients, it is quite necessary for the system to
provide supportability to all its users. In order to enforce supportability in the system, the
nonfunctional requirement of providing 24*7 customer support in the application is proposed.
This will help in improving the supportability of the system.
2. Review of cloud-based solution to be deployed
The system that is being proposed will make use of the cloud approach for improving the
accessibility of the system (Goyal, 2014). The proposed cloud based system needs to consider
the security of the information stored and therefore, it is quite vital to choose a correct approach
of cloud based solution. The system that is being proposed involves storage of the data of the
patients associated with Headspace. Therefore, it is quite essential to choose an appropriate cloud
based approach.

5ITC 548 SYSTEM ANALYSIS
There are mainly three types of cloud approaches that is mainly related to data storage
(Pluzhnik, Nikulchev & Payain, 2014). There are three types of cloud data storage which include
public cloud, hybrid cloud and private cloud.
The public cloud approach is mainly used to define the computing services that makes
data available to public. The use and implementation of a system by making use of public cloud
is a cost effective cloud approach (Li et al., 2015). Therefore, the public cloud in this system may
not be a good idea. The use of public cloud will not provide the required level of security in a
system and therefore, public cloud will not be appropriate for the proposed project.
Another cloud storage that is recommended for the system is the use of private cloud.
Private cloud is quite secure in consideration with the public cloud particularly because it
provides access of the data to the individuals who are allowed its access. The private cloud
model mainly associated with a cloud environment that is distinct and is allowed to be accessed
only by the specified client (Gagnon 2014). The private cloud may not be appropriately used in
this system particularly because the implementation approach of private cloud is quite high.
Apart from that the healthcare professionals need to have an access to patient’s data and
therefore, the system that is being proposed will not make use of private cloud.
Another cloud approach that is being proposed for implementation of the project is use of
hybrid cloud. The hybrid cloud is a combination of both public and private cloud (Pluzhnik,
Nikulchev & Payain, 2014). Hybrid cloud is a cloud environment that make use of on premises
private cloud and third party cloud services (Pluzhnik, Nikulchev & Payain, 2014). This cloud
environment is mainly recommended for this system particularly because it will provide access
of the data to the individuals who are allowed to access the system. This cloud environment is

6ITC 548 SYSTEM ANALYSIS
proposed for the NewAccess project particularly because it will ensure effective data security
and will help in implementing a system in a much lower cost than that of making use of private
cloud approach. The advantages and constraint of making use of hybrid cloud is indicated in the
sections below-
2.1. Advantages of Hybrid cloud
The NewAccess project will use hybrid cloud solution for this system. The most
prominent advantages of making use of Hybrid cloud are -
1. The use of hybrid cloud combines the functionality of public and private cloud which
is a significant advantage of the system.
2. This cloud environment involves improved scalability, which in turn helps in better
implementation of the system.
3. The much needed data security in the NewAccess system that is proposed is another
significant advantage of the system.
2.2. Disadvantages of Hybrid cloud
The use of hybrid cloud in the project although is quite beneficial, for the system, there
are certain disadvantage of using hybrid cloud, which include-
1. The cost of implementing a hybrid cloud is quite high in consideration to use of public
cloud.
2. The cloud implementation is complex in comparison to that of public cloud
3. switching of public and private cloud might result in security risks.

7ITC 548 SYSTEM ANALYSIS
3. SDLC approach
The system development life cycle (SDLC) models that can be used for development of
the system is predictive SDLC model and Adaptive SDLC model (Fenton & Bieman, 2014). The
models are evaluated in the sections below.
3.1. Predictive SDLC
In predictive SDLC model, a project plan is prepared at the beginning of project (Gupta,
Ahlawat & Sagar, 2017). The developed project plan helps in implementation of the project in a
planned manner so that the project is completed in the scheduled time (Stark, 2015). The main
advantage of predictive model is that it helps in reducing project delays and ensures requirements
fulfillment (Fuggetta & Di Nitto, 2014). However, the main disadvantage is that the particular
model is not open to changes. It might be quite difficult to implement a dynamic projetc by
making use of predictive model. The software project might require change according to the
users’ feedback. Incorporation of changes according to the feedback may not be possible in
predictive approach.
3.2. Adaptive SDLC
The SDLC adaptive models is quite distinct from predictive model (Krishnan, 2015). It
may not implement a project as per the plan and it is a systematic process of project
implementation (Abrahamsson et al., 2017). The advantages of SDLC is that contributes in
incorporation of changes in the project even in the implementation phase while its disadvantage
is that the time required for developing a system through this method is quite high.
3.3. Recommendations

8ITC 548 SYSTEM ANALYSIS
The SDLC approach is recommended for this NewAccess project is adaptive model as
this NewAccess project might incorporate changes in the execution phase as per the decision of
the stakeholders involved with the project. The project is based on development of a highly
sensitive information and therefore, making use of SDLC model is well justified.
Conclusion
The report provides a brief overview of the major nonfunctional requirements to be
incorporated in the proposed NewAccess project. The report provides a brief idea of the cloud
model that will be used in the project along with the SDLC model that can help in
implementation of the project in a successful manner. The project is particularly not complex, yet
it is a sensitive project. The adaptive model is proposed for the project as it will ensure
incorporation of the much needed changes in the project even if the project has already started its
implementation. It is quite vital to enforce appropriate monitoring and control in the NewAccess
project, for ensuring that the system is being developed as per the specifications of the
stakeholders. The use making use of hybrid model that is proposed for the NewAccess system
will help in secure storage of the patients’ data in the system.

9ITC 548 SYSTEM ANALYSIS
References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Fenton, N., & Bieman, J. (2014). Software metrics: a rigorous and practical approach. CRC
press.
Fuggetta, A., & Di Nitto, E. (2014, May). Software process. In Proceedings of the on Future of
Software Engineering (pp. 1-12). ACM.
Gagnon, M. P., Ghandour, E. K., Talla, P. K., Simonyan, D., Godin, G., Labrecque, M., ... &
Rousseau, M. (2014). Electronic health record acceptance by physicians: Testing an
integrated theoretical model. Journal of biomedical informatics, 48, 17-27.
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.
Gupta, D., Ahlawat, A. K., & Sagar, K. (2017). Usability prediction & ranking of SDLC models
using fuzzy hierarchical usability model. Open Engineering, 7(1), 161-168.
King, J., Patel, V., Jamoom, E. W., & Furukawa, M. F. (2014). Clinical benefits of electronic
health record use: national findings. Health services research, 49(1pt2), 392-404.
Krishnan, M. S. (2015). Software development risk aspects and success frequency on spiral and
agile model. International Journal of Innovative research in computer and
communication Engineering, (3), 1.

10ITC 548 SYSTEM ANALYSIS
Li, J., Li, Y. K., Chen, X., Lee, P. P., & Lou, W. (2015). A hybrid cloud approach for secure
authorized deduplication. IEEE Transactions on Parallel and Distributed Systems, 26(5),
1206-1216.
Meeks, D. W., Smith, M. W., Taylor, L., Sittig, D. F., Scott, J. M., & Singh, H. (2014). An
analysis of electronic health record-related patient safety concerns. Journal of the
American Medical Informatics Association, 21(6), 1053-1059.
Pluzhnik, E., Nikulchev, E., & Payain, S. (2014, June). Optimal control of applications for
hybrid cloud services. In Services (SERVICES), 2014 IEEE World Congress on (pp. 458-
461). IEEE.
Stark, J. (2015). Product lifecycle management. In Product Lifecycle Management (Volume
1) (pp. 1-29). Springer, Cham.