System Analysis: Cloud Solutions & SDLC Approach for Headspace

This report provides a system analysis for the Headspace NewAccess project, focusing on non-functional requirements using the FURPS+ model (Usability, Reliability, Performance, and Security). It reviews the strengths and weaknesses of cloud-based solutions, considering data security, ownership, and other relevant aspects. The report also compares predictive and adaptive SDLC approaches, recommending the adaptive approach for its flexibility in accommodating changes during the development process. The analysis concludes that considering non-functional requirements, leveraging cloud solutions, and adopting an adaptive SDLC methodology are crucial for the successful development and deployment of the Headspace NewAccess system. Desklib offers a wide range of study resources, including past papers and solved assignments, to support students in their academic endeavors.

Running Head: SYSTEM ANALYSIS
SYSTEM ANALYSIS
Insert Your Name Here
Insert Your Tutor’s Name Here
Institution Affiliation
Date

SYSTEM ANALYSIS
Introduction
In every system development, there is need for system analysis. There are various steps that are
involved in every project. The steps include: understanding the system requirement. There are
two types of requirements. Functional and non-functional requirements. Other steps include:
system analysis and design, implementation, testing, go-live and maintenance of a system.
Non-Functional Requirements
The Headspace NewAccess project have to meet the non-functional requirements. In system
development the considering the testing of the non-functional requirements is one of the most
important steps. The non-functional requirements involve system attributes such as performance,
reliability, usability, security, maintainability and scalability of the system (Cleland-Huang,
Settimi, Zou & Solc, 2007). The non-functional requirements tend to ensure that the system is
efficient and effective. If any system could fail to meet any of the non-functional requirement,
the system could fail to satisfy the business needs, the Emergency department needs, the medical
profession needs and the young people could also fail to get the right medical attention. In most
case the non-functional requirements are persistent compared to the functional requirements
(Mahmoud & Williams, 2016).
The performance of the system need in Headspace has to be fulfil also the system user needs.
Once, the youth fill in the details about him or her, the information should be easily accesses by
the headspace workers, the emergency department or any psychiatrists. The system should all the
youth with mental health process give all the information by breaking it down into various
questions. Then it is that information that will be useful to the departments involved to handle
the case of the youth. The system should have the support mechanisms to help the youth provide
relevant data about their problems. In this case the youth does not have to keep re-telling their
stories. The information accesses by the Headspace case worker, the staff in the emergency
department, general practitioner, psychiatrist or the psychologist should enable them deliver the
right services to the youth having mental problems.
The reliability of a system is an important aspect for every system. A system is reliable when it
accomplishes the tasks it is intended for without collapsing in various conditions such as lack of
electricity or a system breakdown. The system should accomplish the function defined despite

SYSTEM ANALYSIS
harsh environmental conditions such as attacks. The system does have backup in case of any data
loss experienced. The system should have frequent testing and monitoring to check if the data in
the system is accurate and up-to-date. The user interface should be well designed. The user
interface to implement factors such as a simple interface, consistence and use of common user
interface elements, have a purposeful page layout and the color use of the system should
direction attention. The user interface should be kept simple and use labels and messaging. The
user interface should have use common UI elements such as login buttons, the alerts buttons,
navigation bars and other elements. The user interface should have a purposeful page layout. The
placement of items in the system could help draw more attention (Customisable model
transformations based on non-functional requirements, n.d.). Finally, the color uses in the
system should be in a position to redirect attention. The system interaction with the user should
be efficient. For, example once a youth has submitted some information. The system should
display that the information has been submitted and prompt the youth to answer the next
solution.
The system should be secure. The confidential data inserted into the system should be secure
from any attacks. One of the main threats is data loss. This means the database should be secured
and protected from unauthenticated access. Data loss can be caused by hardware failures or
human error. The data should be protected from unauthorized access. The confidential data
should only be accessible to authorized users. The system should have antivirus programs to
remove all malware and virus in the system and detect any malwares. The use of firewall is
another way to enhance security in the system used by Headspace NewAccess. The firewall will
filter out the unwanted intrusion in to the system. The passwords used to log in the systems
should be kept secret and the system should restrict on the use of strong passwords. Finally, the
data should be encrypted to keep it safe. Encryption of data will keep it safe from
unauthenticated users (Esposito, Castiglione & Choo, 2016). The data is kept unreadable from
users without the decryption key.
The system ensure scalability. In case the NewSpace grows it should accommodate the new
users. Also, when the youth with mental problems increase, the system should also be in a
position to accommodate the entire information in the system. The different users of the system
should only access the right information. The system maintenance is also important to check on

SYSTEM ANALYSIS
the defaults that may have occurred and solve them and also to upgrade the system for higher
efficiency.
Cloud based solution
Cloud computing involves storing data, files and programs in the network. This is the one of the
emerging technologies involved in most business. Cloud computing has many advantages and
disadvantages to companies such as Headspace and NewAccess. Cloud will bring some
advantages to NewSpace such as cost savings, reliability, accessibility and flexibility in growth
(Padmavathi, 2016). The cloud solution will help the organization reduce their annual operating
cost by using cloud storage which is cheaper compared to an organization buying the hardware
requirement to store the data. Buying the server require much internal power and power backup
which may be more expensive. Cloud storage one just need to buy space which is more cost
effective (Jun & Jun, 2011).
Cloud solution helps in the reliability of data. The users of the system can access the system from
anywhere and anytime to access the information. The users have to be connected via the internet.
In case the hosting server fails, the system and data can be transited to another server and the
system will be available to the users. This will also enable disaster recovery. The system will
also be accessible to the users.
Cloud will also enhance flexibility in growth. In case there is need for more space where data has
almost reached capacity, NewSpace can pay for an expansion allocated for their system. This
will enable the organization to accommodate the growth as it comes with years. The software
being used will also be uploaded to cloud. This will able users to download the application and
install the program in their devices (Hussain & Abdulsalam, 2012).
Apart from the advantages that will be experienced in the use of cloud based solution, the
organization can face some disadvantages. First, the system owners will no longer be in control
of the system. The data and information is controlled by the cloud operators. The issues of data
security is implemented by them. The organization just need to pay for the services they want
done and the services will be done ("IEEE Cloud Computing Special Issue on Cloud Security",
2015). Also, cloud provides may not provide all the features as required by the organization.
Therefore, they have to uses the services provided by the cloud providers. The organization may

SYSTEM ANALYSIS
also experience some downtime incase where one server fails and data and being transferred to
another server. This results to the business process temporarily suspended. Also in cases where
the users do not have access to the internet, they cannot access the cloud services. Another
disadvantage is the bandwidth allowed by the cloud providers. The cloud storage provides offers
a specified bandwidth allowance. Thais may limit some services by using the cloud based
solution ("Non Functional Requirements - Requirements.com", 2018).
Despite the challenges experienced the advantages of using cloud services are better compared to
using a local server and local backup.
SDLC Approach
The SDLC approach has six phases that are involved in the entire process. First, requirement
gathering is the first stage that involves the understanding the needs of the people who needs a
system (Architects, Architects & Architects, 2018). In this case the information gathering will
involve people such as the emergency department workers, psychiatrists, psychologists among
other people who will require the system. Information requirements include: Why do they need
the system? How do they intend to use the system? What is the input data in the system? The
questions will help get to understand the requirement. After gathering the requirements the
results are analyzed for validity. Secondly, design of the system is done to help define the entire
system architecture. The implementation stage involve the actual development and coding of the
system designed. Once the design is complete various test are done to ensure the system is
solving the problems as intended. There are various types of tests done during these phase. Each
and every test is important. After the system has been testing and the errors solved. The system is
then deployed for live hosting for use by Head Space NewAccess team. During production the
users may require some changes made to the system and the developers should be available for
maintainability of the developed system.
The adaptive approach includes the agile methodology and the predictive approach involves the
waterfall methodologies ("Project Management: Adaptive Vs. Predictive - SSI", 2018). Agile
methodologies are flexible. Agile is the modern type of management strategy. In case the
customer requirements change the development team responds to the change. The adaptive

SYSTEM ANALYSIS
SDLC tends to allow transparency. The communication between the customers and the
developers help both parties share view about the system required and thus gaining the client
trust. Adaptive SDLC enhance early delivery of a system as the client is involved in every step of
the product. The final systems is of high quality as it meets the clients’ requirements. There are
some disadvantages involved with the adaptive SDLC. The approach involves intensive user
involvement. This may be time consuming. Also, this adaptive SDLC approach involves a lot of
requirement therefore taking more time to deliver the final product (Gupta, Ahlawat & Sagar,
2017).
Predictive SDLC approach tends to utilize the specific steps in the control process. The approach
may result to an early delivery of the software as it follows a control process. The approach may
fail in case there are changes made in the system. Customer modification are not allowed in the
system (SambhajiGawade & Bhagwan Hanchate, 2014).
From a look between the two SDLC approaches, adaptive approaches is the best for developing
software ("1.Predictive and Adaptive Lifecycle - Effective Project Management Consultancy",
2018). This is because in every project done, there are changes that are likely to be done and the
system need to accommodate the changes made. The changes made are best fit to satisfy the
customer requirements. The methodology is faster compare to the predictive SDLC approach as
the timeline is not strict and the approach provides room for change. The Headspace NewAccess
project should be developed using the adaptive SDLC approach.
Conclusion
Based on system analysis the above factors have to be considered in order to have a successful
system. The non-functional requirements are necessary as they are the key factors. Without
understanding the non-functional requirements the project will give the wrong solution to the
users. Cloud solution is important as data is available to the users everywhere and anytime with
access to the internet. For a successful project the SDLC methodology is necessary in the
development process. The adaptive approach is better compared to the predictive approach. The
adaptive approach can accommodate the changes made in the development process.

SYSTEM ANALYSIS
References
Mahmoud, A., & Williams, G. (2016). Detecting, classifying, and tracing non-functional
software requirements. Requirements Engineering, 21(3), 357-381. doi: 10.1007/s00766-
016-0252-8
Non Functional Requirements - Requirements.com. (2018). Retrieved from
http://www.requirements.com/Glossary/NonFunctionalRequirements/tabid/91/
Default.aspx
Cleland-Huang, J., Settimi, R., Zou, X., & Solc, P. (2007). Automated classification of non-
functional requirements. Requirements Engineering, 12(2), 103-120. doi:
10.1007/s00766-007-0045-1
IEEE Computer Society. Customisable model transformations based on non-functional
requirements.
IEEE Cloud Computing Special Issue on Cloud Security. (2015). IEEE Cloud Computing, 2(5),
c2-c2. doi: 10.1109/mcc.2015.88
Hussain, M., & Abdulsalam, H. (2012). Software quality in the clouds: a cloud-based solution.
Cluster Computing, 17(2), 389-402. doi: 10.1007/s10586-012-0233-8
Jun, L., & Jun, W. (2011). Cloud Computing Based Solution to Decision Making. Procedia
Engineering, 15, 1822-1826. doi: 10.1016/j.proeng.2011.08.339
Esposito, C., Castiglione, A., & Choo, K. (2016). Encryption-Based Solution for Data
Sovereignty in Federated Clouds. IEEE Cloud Computing, 3(1), 12-17. doi:
10.1109/mcc.2016.18
Padmavathi, B. (2016). Implementation of IOT Based Health Care Solution Based on Cloud
Computing. International Journal Of Engineering And Computer Science. doi:
10.18535/ijecs/v5i9.23
Architects, I., Architects, I., & Architects, I. (2018). SDLC Models & Methodologies
[COMPLETE GUIDE]. Retrieved from

SYSTEM ANALYSIS
https://www.innovativearchitects.com/KnowledgeCenter/basic-IT-systems/8-SDLC-
models.aspx
Project Management: Adaptive Vs. Predictive - SSI. (2018). Retrieved from
https://www.ssipeople.com/2015/10/13/project-management-adaptive-vs-predictive/
1.Predictive and Adaptive Lifecycle - Effective Project Management Consultancy. (2018).
Retrieved from http://www.effectivepmc.com/blog/scrum/predictive-and-adaptive-
lifecycle
SambhajiGawade, J., & Bhagwan Hanchate, D. (2014). Prediction of Software Defects in SDLC
using BN. International Journal Of Computer Applications, 99(4), 1-7. doi:
10.5120/17358-7885
Gupta, D., Ahlawat, A., & Sagar, K. (2017). Usability Prediction & Ranking of SDLC Models
Using Fuzzy Hierarchical Usability Model. Open Engineering, 7(1). doi: 10.1515/eng-
2017-0021