System Analysis and Design: Headspace's Cloud-Based Solution Report

This report provides a comprehensive system analysis and design for the Headspace organization, focusing on the implementation of a cloud-based New Access system for young patients aged 17-25. The analysis covers non-functional requirements, including FURPS (Functionality, Usability, Reliability, Performance, and Supportability), and evaluates the strengths and challenges of cloud-based solutions. The report also compares adaptive and predictive SDLC approaches, outlining their advantages and disadvantages to recommend the most suitable method for Headspace's development strategies. The case study highlights the need for an effective system to help patients easily share their stories with physiologists, ultimately improving their experience and the efficiency of the organization's services. The report also includes a stakeholder analysis, questionnaire and use case description.

Running head: SYSTEM ANALYSIS AND DESIGN 1
System analysis and Design
Headspace organization
Student Name
Institutional Affiliation
Date

SYSTEM ANALYSIS AND DESIGN 2
Table of Contents
Introduction..........................................................................................................................3
Headspace Organization Case study....................................................................................3
Non-Functional Requirements.............................................................................................4
Review on Strengths and Challenges of cloud-based solutions..........................................6
Strengths of Cloud-based Solutions.................................................................................7
Challenges of Cloud-Based solutions..............................................................................7
Advantages and Disadvantages of using the Adaptive SDLC.............................................8
Advantages of Adaptive SDLC.......................................................................................8
Demerits of Adaptive SDLC Approach...........................................................................9
Merits and Demerits of Predictive SDLC Approach...........................................................9
Merits of Predictive SDLC..............................................................................................9
Demerits of Predictive approach...................................................................................10
Best SDLC Approach........................................................................................................10
List of References..............................................................................................................11

SYSTEM ANALYSIS AND DESIGN 3
Introduction
In the current era, many businesses have migrated to the use of cloud based solutions to
avoid data loss, insecurity issues and much more easy access to their information. In addition,
large space capacity that is needed by most businesses in storing the big data has also made
many organizations to move to cloud based. There are so many problems in relation to the
physical storage of information in the firm premises. This has indeed many firm managers to
adopt the use of cloud based solutions. In understanding the basic or context of cloud-based
solutions one must know the type of information systems to be installed in the company and
which will meet the objectives of the company. In understanding the context of the needed
solution, one must understand the environment which is noted as everything that will influence
or maybe influenced by the IS and its purpose. Ideally, the detailed description of the IS will
have an impact on the mentioned environment and thus in turn the environment will impact the
IS.
This report has been presented by giving an explanation of what is really Cloud-based
solutions. In explaining the new access infrastructure, it is good for Headspace organization to
understand some of the strengths or benefits of using cloud-based solutions and the weaknesses.
Ideally, there is need for one to understand and explain the cons and pros of both adaptive and
predictive SDLC so us to know which approach to use when gathering information using the
questionnaire. By identifying their pros and cons it will be easy for one to help Headspace
Organization to choose the best method that suits its development strategies.
Headspace Organization Case study
In this case, the report will major on the context of the Headspace organization who have
a thought of implementing an effective New Access system for the youth’s aged 17 to 25 years.

SYSTEM ANALYSIS AND DESIGN 4
The reason for such a move is to make the patients who cannot be able to narrate their stories to
their physiologist to see it easy in all aspects. In the cloud based solutions, it will be easy for the
youth patients to be able to converse with the physiologists without fear. Through the
development of a new access infrastructure in to the organization will help the management with
the stories.
Information system can be defined as the performance of sets of procedures or processes that
work together to achieve the objectives of the organization. In the context of IS, IS Processes can
be termed as the collection, organization, storage and retrieval among others such as displaying
and receiving. Headspace organizatin will ask for such services so that they can be helped with
storage and an integrated system that they can control in the same platform.
Non-Functional Requirements
Ideally, as per the information given the case study of Headspace, this project of cloud-
based solutions will consider several aspects of the IS in adopting the Cloud-based services.
Some of the aspects to be considered are the data security that includes the ownership of the data.
In addition this will major in all the major and fundamental aspects of cloud solutions. Some of
them are the non-functional requirements that Headspace Organization, reviewing of the cloud-
based services and the Software development lifecycle approaches which can be used in
integrating the services in the cloud-based technologies. In this case, to explain the concept of
non-functional requirement the report has approached it by the use of the Functionalities,
usability’s, reliability, performance and the Supportability abbreviated as FURPS.
FURPS
In most cases, with regards to the non-functional requirements for the system to be
developed or adapted, the features considered are such as qualities of the system, the

SYSTEM ANALYSIS AND DESIGN 5
requirements of the user interface, overall system requirements and the system constraints which
must be followed to avoid over budgeting or not being able to work within the given timeframe.
In understanding the overall requirements, the requirements are explained in details below.
Notably, in terms of the helping the youths with their stories who are their patients,
Headspace Organization should consider the cloud-based solutions capabilities and reusability.
The first thing before doing anything else with the system is for them to understand the system
capabilities. Understanding the capabilities will help the organization to understand the features
and thus making an informed decision with regards to which IS cloud-based solution to select.
The objectives dictates the Cloud-based solution to choose as every business needs is to satisfy
the customer’s needs. Another function is the reliability of the system. Since the system is online
and easily accessible it should be reliable all the time to the patients and thus making the work to
be done anywhere without problems of system errors or inaccessible. Reliability strengthens the
relationship between the patients and the Headspace Organization.
Secondly is the usability which usually has features such as human factors, consistency
and the responsiveness. Any system no matter online or offline should cater for the usability
functions. This can be tested by the human factors such as the consistency and responsiveness.
By consistency, the system should follow a given trend always not displaying various features
each day and thus bringing confusion to the users. Ideally, by efficient consistency the system
will make the patients to adapt to it very fast thus using it easily. Another feature is the
responsiveness, the new access system should have a user interface that the user can easily
interact with it by using of icons, graphics and context which are simple and easy to use and
much more user-friendly.

SYSTEM ANALYSIS AND DESIGN 6
Reliability is another feature that have other aspects such as availability, accuracy and
much more predictability. Availability of the system is a very key thing in understanding the best
system to use. The system should always be available to the patients. Another feature that should
be understood by Headspace Organization is the concept of accuracy, this will make the system
users to be loyal to the organization as they are no errors in the system. If Headspace
Organization migrate to cloud based solutions, it will be easy to predict and make judgments
based on the figures and facts that have been gathered with regards to stories they narrate.
Performance is another requirement that has such features such as scalability, throughput,
capacity, throughput and the consumption on the basis of resources. In addition speed and
efficiency follows in this category. The client will have to make sure that the migration to the
cloud based solutions will not lower the performance in terms of the speed and efficiency. The
speed can be measured by productivity level within a given time. Also the capacity will need to
be considered in all aspects, this is because in cloud computing it all about dealing with data
definition and manipulation.
Supportability is the last concept of FURPS. In this case it majors on the portability,
localizability, flexibility and the testability. If the system is not portable to another location then
the Headspace Organization should avoid implementing such systems no matter the cost given.
Understanding the concept of supportability, Headspace Organization must know that the system
should be flexible in that it can allow easy configurations without problems and thus easy to test
the performance at less cost at any time without fear of losing patients data.
Review on Strengths and Challenges of cloud-based solutions
There simply no uncertainty that Headspace Organization can receive lot of services from
the cloud-based solutions. In any case, there are various points of interests which indeed comes

SYSTEM ANALYSIS AND DESIGN 7
with various challenges. In this case, there is identification of some benefits and the weaknesses
of the cloud-based solutions with a major goal of identifying some of the goals that can help in
capitalization of the organization innovation strategies.
Strengths of Cloud-based Solutions
This will save on cost. In this case with regards to cloud-based solutions, the advantage is
that cost is saved as there is maintenance or purchasing the many equipment’s as those needed in
the physical storage in the company premises. Ideally regardless of the capacity and capability
needed by the company the company will only be needed to pay for the downplaying capital and
the cost of operations. (chang, 2010). Using the cloud-based solutions, Headspace Organization
can be able to save the expense of the in-house as it zero cost and thus a benefit to the
organization.
It is very much reliable. Ideally, in many cases, the cloud-based solutions are reliable and
any person can rely on them unlike the case in the physical storage on one’s premises (Janka,
2012). Most of the vendors of such services offers SLA which usually ensures the clients that
they have an accessibility of the system 24/7 at all-time giving a 99.99% assurance.
Easy to manage. Ideally, with cloud based solutions giving an improvement and
arranging the management and up keeping the capacities through the coordination and
organization of such assets and services overseeing the systems and the SLA sponsored
understandings.
Challenges of Cloud-Based solutions
There is a lot of downtime. In this case, as the cloud specialist are dealing with the
various patients daily, they can be able to move towards becoming empowered and thus facing

SYSTEM ANALYSIS AND DESIGN 8
specialized brownouts. Ideally, this may need the organization forms to be suspended
incidentally without comprimisation.
Security issues. Ideally, by use of the cloud computing one can be able to furnish the
specialist with access to important business information (Bisong, 2011).
The control of the application is limited on the side of the patient. The vendor has full
responsibility on the system and thus having the backend control sometimes this may give
Headspace Organization some worry though that is the way it is as they have an agreement
policy(Chang, 2010). Headspace Organization will only have control on the applications,
information that need processing and the management part on his side and not simply on the
backend side.
Advantages and Disadvantages of using the Adaptive SDLC
Advantages of Adaptive SDLC
This type of methodology usually allow the extensive stakeholders to be able to engage
before the project start, in progress and even after it has been implemented or finished
(Holcombe, 2012). In this case, the project will have a lot of collaboration within the
development team as it involves an interaction which is much more extensive between the
patients and the development team at each and every stage.
This approach allows transparency. The developers are able to work together in each
stage effectively (Beyer, 2010). The developers can be able to describe and give an explanation
with regards to the project status to the anticipated patients aged 17-25 before the project has
started, during the development and then after the development.
This approach can allow for an early delivery (Nocera, 2016). Ideally, the involvement is
extensive in the manner that they can make meaningful contributions prior the start of the

SYSTEM ANALYSIS AND DESIGN 9
project, during the project and after each step of the project development. The development will
be faster as it ushers the software developed early.
Demerits of Adaptive SDLC Approach
This methodology demands the patients to participate fully in all aspects and thus giving
them the set price and thus making sure that the system is developed according to their needs,
however this may take a lot of time which they could have been doing other things.
This methodology likewise incorporates a lot of requirements enhancement and
progression in the focus of what needed in the future expansions (Holcombe, 2008). Testing in
this methodology is joined all through the phases of the SDLC. Ideally, to perform testing in
each stage though it passes on the quality things it might be very costly and thus increasing the
budget as time goes on. The expansive testing, as demonstrated by concentrates done, passes on
various dares to dissatisfaction (Vohra and Krishnamurthy, 2012).
Merits and Demerits of Predictive SDLC Approach
Merits of Predictive SDLC
In this methodology, it will be easy to use this predictive approach. This is because this
approach usually follow the concepts of the initiation all the way to the software deployment. In
this case, there is laying down of the steps and providing all the preceding actions and thus it
makes it easy for the development team to be able to construct and implement a software with
good quality within the given timeframe within the given budget.
In case, Headspace Organization uses this approach also they can be able to predict easily
on the needed budget as well as the given timeframe. This is because the final product that is
expected can be virtualized at the initiation stage of the project. This makes it easy for the
organization to be able to estimate the expected budget of the given project.

SYSTEM ANALYSIS AND DESIGN 10
Another pros is that predictive SDLC are very much easy to manage. This is because
each predictive approach usually have specific deliverables and the given timeframes. Using the
above two aspects in this case of Headspace Organization cloud-based solutions, it will help one
to easily monitor and be able to handle the project development and the entire lifecycle.
Demerits of Predictive approach
Ideally, unlike in the Adaptive approach in the predictive SDLC there is no software
which is working can be produced until on the later phases of the development (El-Khatib,
2018). A running software will only be generated in the final phase of software development. In
this case, it is good to know that to test and review of the project can only be performed at the
final stages of the SDLC (Vohra and Krishnamurthi, 2012)
Lastly is that, Predictive approach is not advisable to be used on the complex projects
which are object-oriented. This approach is only used for projects which are smaller and the
requirements can be easily defined at the initial stage.
Best SDLC Approach
As seen in the case study, the best SDLC Approach to be used by Headspace
Organization is the adaptive SDLC. This is because this case study requires the system to be
used by various patients. This makes use of the extensive user involvement which is usually
employed in every stage of the development. Also the system required in the cloud-based
solutions will be based on completeness which can be only done on the adaptive approach unlike
in the predictive approach. In this project on the cloud-based solutions, Headspace Organization
will need several elements which might be object-oriented in nature and thus making the
Adaptive SDLC the best choice as Predictive Approach cannot support the new access system.

SYSTEM ANALYSIS AND DESIGN 11
List of References
Beyer, H. (2010). User-centered agile methods. Synthesis lectures on human-centered
informatics, 3(1), 1-71.
Bisong, A., & Rahman, M. (2011). An overview of the security concerns in enterprise cloud
computing. arXiv preprint arXiv:1101.5613.
Chang, V., Bacigalupo, D., Wills, G., & De Roure, D. (2010, May). A categorisation of cloud
computing business models. In Proceedings of the 2010 10th ieee/acm international
conference on cluster, cloud and grid computing (pp. 509-512). IEEE Computer Society.
Chang, V., Wills, G., & De Roure, D. (2010, July). A review of cloud business models and
sustainability. In 2010 IEEE 3rd International Conference on Cloud Computing (pp. 43-
50). IEEE.
El-Khatib, A. (2018). Educating interior design & architecture clients about sustainable design:
issues, perceptions, and expectations.
Holcombe, W. M. L. (2012). Running an agile software development project (No. Sirsi)
i9780470136690). Wiley.
Islam, K. A. (2013). Agile methodology for developing & measuring learning: Training
development for today’s world. AuthorHouse.
Janka, R. S. (2012). Specification and design methodology for real-time embedded systems.
Springer Science & Business Media.
Laskowski, J. (2011). Agile IT security implementation methodology. Packt Publishing Ltd.
Lewis, J. (2014). SDLC 100 Success Secrets-Software Development Life Cycle (SDLC) 100 Most
asked Questions, SDLC Methodologies, Tools, Process and Business Models. Emereo Pty
Ltd.

SYSTEM ANALYSIS AND DESIGN 12
Nocera, F. (2016, April). Fuzzy ontology-driven web-based framework for supporting
architectural design: student research abstract. In Proceedings of the 31st Annual ACM
Symposium on Applied Computing (pp. 1361-1362). ACM.
Srivyshnavi, P. (2013). Modeling For Software Quality Assurance. Saarbrücken: LAP
LAMBERT Academic Publishing.
Vohra, R. V., & Krishnamurthi, L. (2012). Principles of pricing: an analytical approach.
Cambridge University Press.