System Analysis for Headspace: Cloud Solutions and SDLC Approaches

This report provides a system analysis for the Headspace project, focusing on both functional and non-functional requirements. It delves into key aspects such as functionality, usability, reliability, performance, and supportability, providing a comprehensive overview of the system's needs. The report also explores various cloud solutions, including public, private, and hybrid cloud models, evaluating their suitability for the project. It highlights the advantages and disadvantages of each cloud type, with a recommendation for a private cloud due to its enhanced security features, which are crucial for handling sensitive patient data. Furthermore, the report compares predictive and adaptive SDLC methodologies, recommending the adaptive SDLC approach for its flexibility and ability to incorporate changes throughout the development process. The analysis concludes with a discussion on the benefits of the adaptive SDLC approach, emphasizing its adaptability to changing project requirements and its iterative development cycles.

1
Running Head: SYSTEM ANALYSIS
System Analysis
Student’s Name
Institution

2
SYSTEM ANALYSIS
System Analysis
Question 1
The key non-functional system requirements for the Headspace project include functionality,
usability, reliability, performance, and supportability. Functionality is the range of operations
that can be run by an IT system. It comprises of several aspects including security, capability,
and reusability (Chung, 2012). The IT solution required by the organization should have the
general features that serve its needs, is compatible with other systems, is easily portable, and has
various security features that mitigate the risks of exploitation or safety threats. A system with
high functionality is secure against various security threats, connects with necessary external
systems, and offers features that aligned with the organization needs.
Usability is ease of use of a human-designed object such as a device, website, etc. In system
development, usability implies the extent to which the system is used by target audience to
achieve specific goals with efficiency and satisfaction. Usability involves several factors which
include human factors, aesthetics, responsiveness, and consistency (Albert, 2013). Balancing
these aspects is key to achieving high usability which is significant for the Headspace project. A
highly usable system is essential in the foundation to ensure it can be effectively used by the staff
to provide patient-centered care.
Reliability is the probability of a system performing a specific operation under specified
conditions without failure within a given timeframe (Lyu, 2007). System reliability is an
important requirement that has to be considered when implementing a new system. It is defined
by several aspects which include availability, failure extent, predictability, and accuracy.
Reliability of the proposed solution is essential to the Headspace foundation as it carries out

3
SYSTEM ANALYSIS
sensitive tasks that require real-time information. High system reliability enhances the
effectiveness and efficiency of the organization in providing care.
Performance is a key non-functional requirement for any system. Firms running systems seek
high performance which quick execution of tasks. Performance involves the speed, capacity,
efficiency, throughput, resource consumption, and scalability (Liu, 2011). The organization
needs a system with high performance which rapidly processes information and produces the
expected output. A system with high performance has high speed, scales operations based on
need, effectively uses resources available, and enhances the efficiency of operations. With a
system that has high performance, Headspace can easily access information and utilize the
system to provide care to the patients.
Supportability refers to the ease of installing, configuring, and monitoring a system, identifying
errors, debugging, and providing maintenance to restore the system into service (Pecht, 2009).
Any firm wants a system that is easy to install and maintain. A highly supportable system can be
easily set up, configured as per the organization’s needs, and can be easily debugged to identify
and resolve faults. Such a system is vital for Headspace foundation as it needs a system that can
be easily maintained to support healthcare operations at the organization.
Some of the key functional system requirements include business rules, administrative functions,
user authentication, access levels, data analysis, and reporting. In contrast to the non-functional
system requirements defined, these requirements specify a function that the system should
execute (Pohl, 2010). For example, the system is expected to generate medical reports for each
patient. On the other hand, non-functional system requirements specific criteria for assessing
system operations (Glinz, 2007). For example, system performance defines how to determine
how quickly the system executes a specific task.

4
SYSTEM ANALYSIS
Question 2
Some of the types of cloud solutions suitable for Headspace project are public, private, and
hybrid cloud. Public cloud is simply the internet. Cloud providers use the internet to avail
computing resources such as applications and storage to the users. Examples of public cloud
solutions include Blue cloud, Windows Azure, Amazon Elastic Compute Cloud, etc. The
providers offer convenience as it’s easy to set up and use. Many developers prefer the public
cloud due to its ease of access. Typically, public cloud has fast speed and attracts enterprises. It
operates on a cost-effective pay-per-use model hence users only pay for the resources they use.
Public cloud is flexible as it allows users to increase or reduce capacity and can be accessed from
any device that is connected to the internet.
The public cloud has various risks which undermine its effectiveness in some situations. It is
operated by a third party implies that it isn’t specific to any business and is designed to have
shared resources. Public cloud outages are common which can affect operations. Outages may
adversely affect Headspace which relies on the cloud solution for real-time information to
provide care. Also, public cloud has a lower level of security and can be vulnerable to attacks
(Ren, 2012). This is a major threat to Headspace which handles personal information that has to
be safeguarded as required by the law.
Private cloud is a data architecture owned and managed by a single enterprise. The private cloud
aims to gain benefits of cloud computing while maintaining control of the data center. It is
appropriate for the Headspace as it is concerned about the data it stores and wants to have
complete control and access to the cloud. As a healthcare organization, Headspace is subject to
various data privacy regulations and legislation. Private cloud may be the best position for the
organization as it fits its security and data needs.

5
SYSTEM ANALYSIS
Private cloud is organization-specific implying that is developed specifically for Headspace
needs and is not shared among many users. With a private cloud, a business has more control
over the cloud services and infrastructure (Dillon, 2010). Private cloud allows robust service
level agreements which enhances reliability. Additionally, an IT team can customize the cloud
components to ensure the cloud service is the right fit for the organization.
The private cloud has various drawbacks which can limit is adoption especially by cash-strapped
organizations. It is more costly than public cloud computing. It increases costs due to increased
management responsibilities (Grossman, 2009). Hence, it is important for businesses to weight
the risks and costs of the solution. The private cloud also requires an IT team with experience in
cloud computing. Firms without the infrastructure to build a private cloud incur a lot of costs in
outsourcing the work to IT experts. Also, firms need IT professionals to maintain the private
cloud.
Hybrid cloud supports a mixed approach whereby businesses can pick some elements of either
public or private cloud or combine both in a manner that aligns with their needs (Li, 2015). For
example, a retail company can deploy its e-commerce website on a private cloud but can also
host its non-sensitive information on the public cloud. Hybrid cloud balances security and
convenience. This has led to the rise in the number of businesses adopting hybrid cloud services.
Since hybrid cloud incorporates both private and public cloud elements, businesses can mix the
components that offer them a balance between security and cost. Hybrid cloud services are also
cost-effective as enterprises enjoy the cheap costs of public cloud and the security offered by the
private cloud.
Despite its apparent benefits, hybrid cloud also has several drawbacks that limit its
implementation. It requires tools and skills to build and manage hybrid cloud solution. Not every

6
SYSTEM ANALYSIS
enterprise has the capital and expertise to adopt the solution. Often, it might be necessary for a
company to outsource the cloud installation process to outside talent. Furthermore, the IT team
implementing the solution has to undergo additional training which incurs costs.
While public cloud is relatively flexible and low-cost, building a private cloud can incur a lot of
costs due to the hardware required. Heavy use of public cloud may lead to high usage bills.
Compatibility is another challenges when executing a hybrid cloud strategy. Given that a
company runs a private cloud that it controls and public cloud run by third-party owners, the two
may have different stacks that are incompatible. Also, integration of data and applications is a
challenge when developing a hybrid cloud. The two depend on each other so when they are
stored in different cloud architectures, they may raise technical issues.
Private cloud is the most suitable cloud solution for Headspace foundation. While it is costly to
implement, it offers a high level of security. Since the foundation deals with sensitive personal
health information, it requires a secure solution that can safeguard the privacy and confidentiality
of its patients’ information. The private cloud can secure this information in a manner that aligns
with legislation protecting user information.
Question 3
Predictive SDLC
Predictive SDLC is a traditional approach to system development that involves several stages
which include project planning, analysis, design, implementation, and support (Sakul-Ung,
2017). In project planning, a project is initiated, a feasibility study is conducted, the project
schedule is created, and project approval is obtained. In the analysis phase, the stakeholders
assess the project to gain an insight into business needs. The design phase focuses on defining

7
SYSTEM ANALYSIS
the solution based on the requirements identified in the previous phase. In the implementation
phase, the system is developed and tested, and users are trained. Support is the last phase which
involves providing user and system support to keep the system functioning as expected and
improve its efficiency.
The key advantage of predictive SDLC is having a clear plan before implementing the project.
Since the approach requires extensive planning, developers can estimate schedule and budget
accurately. The approach also tends to be secure as it is plan-centered hence a software can be
easily created. However, predictive SDLC is rigid and flexible which creates challenges when
change arises during the project. Changing the project at any stage is nearly impossible.
Adaptive SDLC
Adaptive SDLC is based on the spiral model. Under this model, there are project cycles in which
development activities are done over and over until the project is completed (Qureshi, 2008). At
the end of each cycle, a prototype is developed. In each cycle, emphasis is placed on mitigating
risk. Iterations are a key component of this approach. Work activities are repeated with emphasis
placed on refining the previous prototype in each iteration. The approach assumes that the
system cannot be developed right for the first time hence there are several mini-projects in each
iteration aimed at improving the prototype until stakeholders are satisfied with the deliverable.
Adaptive SDLC is an incredibly flexible system development approach which supports changes
throughout the system development life cycle (Naderuzzaman, 2011). Customer feedback that
occurs during the project progress can be incorporated in the development process. Thus, the
prototype is refined to respond to changing requirements. It is beneficial in situations where
projects requirements can change. However, while it is highly flexible, it is hard to predict the

8
SYSTEM ANALYSIS
project schedule and budget. Also, adaptive SLC requires intense collaboration which can be
problematic.
Headspace Foundation should adopt adaptive SDLC when developing the proposed solution.
Adaptive SDLC is more appropriate than predictive SDLC as it is flexible and focuses on
refining a prototype until the requirements are met. With this approach, the organization can
incorporate new requirements that arise into the system development process.

9
SYSTEM ANALYSIS
References
Albert, W., & Tullis, T. (2013). Measuring the user experience: collecting, analyzing, and
presenting usability metrics. Newnes.
Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2012). Non-functional requirements in
software engineering (Vol. 5). Springer Science & Business Media.
Dillon, T., Wu, C., & Chang, E. (2010, April). Cloud computing: issues and challenges.
In Advanced Information Networking and Applications (AINA), 2010 24th IEEE
International Conference on(pp. 27-33). Ieee.
Glinz, M. (2007, October). On non-functional requirements. In Requirements Engineering
Conference, 2007. RE'07. 15th IEEE International (pp. 21-26). IEEE.
Grossman, R. L. (2009). The case for cloud computing. IT professional, 11(2), 23-27.
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.
Liu, H. H. (2011). Software performance and scalability: a quantitative approach (Vol. 7). John
Wiley & Sons.
Lyu, M. R. (2007, May). Software reliability engineering: A roadmap. In 2007 Future of
Software Engineering (pp. 153-170). IEEE Computer Society.
Naderuzzaman, M., Rabbi, F., & Beg, A. H. (2011). An improved & adaptive software
development methodology. Computer Engineering and Intelligent Systems, 2(3), 35-40.

10
SYSTEM ANALYSIS
Pecht, M. (Ed.). (2009). Product reliability, maintainability, and supportability handbook. CRC
Press.
Pohl, K. (2010). Requirements engineering: fundamentals, principles, and techniques. Springer
Publishing Company, Incorporated.
Ren, K., Wang, C., & Wang, Q. (2012). Security challenges for the public cloud. IEEE Internet
Computing, 16(1), 69-73.
Sakul-Ung, P., & Chutimaskul, W. (2017, February). A predictive model for successful software
development projects with information technology strategic alignment. In Proceedings of
the 6th International Conference on Software and Computer Applications (pp. 39-45).
ACM.
Qureshi, M. R. J., & Hussain, S. A. (2008). An adaptive software development process
model. Advances in Engineering Software, 39(8), 654-658.