System Analysis and Design: Cloud Computing

Running head: SYSTEM ANALYSIS AND DESIGN: CLOUD COMPUTING 1
System Analysis and Design: Cloud Computing
Student Name
Institutional Affiliation

SYSTEM ANALYSIS AND DESIGN: CLOUD COMPUTING 2
Executive Summary
Cloud computing is now being considered by several enterprises as a solution to their
increasing information needs such as data storage, shared application, back up and disaster
recovery strategies. Additionally, cloud computing offers high level of availability, flexibility,
and scalability. The main benefits that the cloud-based solution will offer include wide
availability, cost effectiveness, backup and disaster, and high scalability. However, it is also
faced with numerous challenges concerning data privacy, ownership, interoperability, technical
issues, and trust. As such, it is recommended that Headspace adopt cloud-based solution. This
report seeks to propose to Headspace the critical aspects that should be considered when
implementing the NewAccess project including non-functional requirements, strengths and
weaknesses of cloud computing, security requirements, and the type of system development life
cycle approach that Headspace can adopt.

SYSTEM ANALYSIS AND DESIGN: CLOUD COMPUTING 3
Table of Contents
Executive Summary.........................................................................................................................2
Introduction......................................................................................................................................4
Non-functional Requirements..........................................................................................................4
Review of cloud-based....................................................................................................................6
Strengths of Cloud-Based Solution..............................................................................................6
Weaknesses of Cloud-Based Solution.........................................................................................7
System Development Life Cycle (SDLC).......................................................................................8
Advantages of adaptive SDLC.....................................................................................................8
Disadvantages of Adaptive SDLC...............................................................................................9
Advantages of Predictive SDLC................................................................................................10
Disadvantages of Predictive SDLC............................................................................................10
Best Approach Headspace.........................................................................................................10
Conclusion.....................................................................................................................................11
References......................................................................................................................................12

SYSTEM ANALYSIS AND DESIGN: CLOUD COMPUTING 4
Introduction
Technology evolution and the continued innovation in the IT industry has led to the
emergence of cloud computing which many institutions, enterprises, and governments are now
shifting their IT infrastructure to. The increasing dependence by many organizations has led to
the need to have systems and applications that can be accessed by millions of users without
affecting the overall performance and productivity while maintaining high level availability
(Viswanathan, 2018). This report seeks to propose to Headspace the critical aspects that should
be considered when implementing the NewAccess project including non-functional
requirements, strengths and weaknesses of cloud computing, security requirements, and the type
of system development life cycle approach that Headspace can adopt.
Non-functional Requirements
When considering a cloud-based solution, many at times people tend to focus more on
the functional requirements which are the features and abilities expected by users to be
performed by the system, that is, what the system should do. Functional requirements tend to
vary across the different departments and employees. However, every solution has non-
functional requirements that are also very crucial and should never be abstracted or overlooked
(Crudele & Castiglioni, 2014). an application may have met all the functional requirements but it
will be considered a failed project if it does not meet the non-functional requirements. In
traditional software development, the developers have often modified the shape and size of the
application in order to respond to the non-functional requirements. Non-functional requirements
define the features that a cloud solution should have and the functional constraints. They include,
but not limited to, security, usability, performance, and reliability.