System Analysis and Design: Headspace NewAccess Project

This report discusses the non-functional requirements, FURPS, cloud-based solutions, and SDLC approach for Headspace NewAccess Project. It also provides recommendations for the project. The report emphasizes the importance of user interface, system qualities, system constraints, and system interfaces. It also discusses the strengths and weaknesses of cloud-based solutions and the environment in which they are deployed. Finally, the report compares predictive and adaptive SDLC approaches and recommends the latter for the project.

Running Head: SYSTEM ANALYSIS AND DESIGN
Headspace NewAccess Project
Name of the student:
Name of the university:
Author note:

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Introduction......................................................................................................................................2
Non-functional requirements (Part 1)..............................................................................................2
Critical system qualities...............................................................................................................2
System interfaces.........................................................................................................................3
Requirements for user interface...................................................................................................3
System constraints.......................................................................................................................4
Non-functional requirement (Part 2)...............................................................................................5
FURPS.........................................................................................................................................5
Functionality................................................................................................................................5
Usability.......................................................................................................................................5
Reliability....................................................................................................................................6
Performance.................................................................................................................................6
Security........................................................................................................................................6
Review of cloud based.....................................................................................................................6
Strengths of cloud based solution................................................................................................7
Weaknesses of cloud based solution............................................................................................7
Environment in which cloud based solution is deployed............................................................7
SDLC Approach..............................................................................................................................8
Advantages and disadvantages of Predictive SDLC...................................................................8
Advantages and disadvantages of Adaptive SDLC.....................................................................8
Recommendation.......................................................................................................................10
Conclusion.....................................................................................................................................10
References......................................................................................................................................11

2SYSTEM ANALYSIS AND DESIGN
Introduction:
This report will enlighten on Headspace NewAccess Project that is aimed at recovering
mentally ill youth. Headspace is a health organisation that takes care of youth mental health.
Along with help of government, Headspace operates nationally with a number of centres spread
in various places. Young people of ages between 12 to 25 years who are facing trouble in
physical, mental and drug addiction are assisted and supported by headspace centres (McGorry,
Bates & Birchwood, 2013). Face-to-face communication helps centres to communicate
information to troubled youth. Story told by young patients was previously recorded and sent to
general physicians in different fields and psychologists so that it eliminates inconvenience of
repeating the story every time (Child & Expert, 2015). However, a cloud based solution is being
thought of that would replace previous technology. As a result, benefits of cloud based solution
needs to be considered.
The following paragraphs will mainly focus on non-functional requirements including
user interfaces, system qualities, system constraints and interfaces. Additionally, FURPS will be
discussed in depth followed by a brief discussion on predictive and adaptive SDLC and their
usage in Headspace.
Non-functional requirements (Part 1):
Critical system qualities:
User experience, design and run-time behaviour of a system is influenced by system
qualities. System qualities or factors that are essential for a good system are inoperability,
manageability, scalability, conceptual integrity and reusability (Alrawashdeh, Muhairat &
Althunibat, 2013). Inoperability is defined as the quality of a system to cooperate and interact

3SYSTEM ANALYSIS AND DESIGN
with other peripheral systems. Manageability is the quality of a system to be managed easily that
takes into consideration the efficiency and performance of a system. Scalability is a function of a
system that has capability to deal with increased load however not affecting performance of a
system. Conceptual integrity includes stability of the complete design and coding style of a
system. Reusability is the quality of a system that allows it to be reused in other systems.
System interfaces:
It is defined as a platform to interact with users (in this case patients and professionals). It
is a combination of inputs and outputs of a system. In other words, system interface is referred to
operating system (Suman & Rohtak, 2014). System interface will help user to display detailed
and specific patient reports, update notification, schedule reminder that will help them to send
reminder to young patients and doctor in-charge, and format data structures of patients with help
of HTML and XML tags.
Requirements for user interface:
Professionals and patients will control the Headspace application. As a result, user
interface should be user friendly so that the patients and professionals do not face any problem
while interacting with the application (Singh, 2013). The ways by which Headspace can make
the application user interface more friendly are by strategical use of colour and textures that
would grab user attention, maintaining simplicity in the application and enabling shortcuts for
boosting user process. Furthermore, the opening page should be formatted and designed by
carefully placing items in the page.

4SYSTEM ANALYSIS AND DESIGN
Figure 1: Factors needed for a good user interface
(Source: Memmel, 2018)
System constraints:
System constraints include restrictions on design, implementation, interface and
hardware. In case of Headspace, design constraints will be applied on database design such that
it can be maintained easily. Implementation constraints applies to coding and construction
standards. Headspace should address to implementation language as some young teens in
regional NSW speaks and understands only native language. In Headspace situation, director of
public health office apart from professionals and patients might want patient key information.

5SYSTEM ANALYSIS AND DESIGN
There lies interface constraints. Physical constraints affect hardware that is used to store the
system. It is the physical requirements that the application used by Headspace should possess.
Non-functional requirement (Part 2):
FURPS: It is the acronym of functionality, usability, reliability, performance and security.
Figure 2: FURPS
(Source: Campos, 2018)
Functionality: It represents functional requirements of the system that should include technical
aspects like reporting, printing, auditing and localisation. It is referred as the product structures
of solution being established within business province.
Usability: The end users determine usability of a system. In this case, end users are patients and
professionals. Patients might be a beginner, an intermediate or advanced. Therefore, Headspace

6SYSTEM ANALYSIS AND DESIGN
application should be developed in such a way that they prove to be friendly to all types of
patients. The looks, presents and aesthetics all are part of usability checks.
Reliability: The factors that needs to be considered for reliability are accuracy, availability and
recoverability. The application of Headspace should be reliable as important information of
young people are stored in it. They cannot risk their personal information at a young age.
Performance: System performance is emphasised. To deliver satisfying service to patients,
Headspace will consider non-functional requirements. Performance of a system will be measured
by system response time, start time and retrieval time. Headspace should consider performance
of application as the application directly interacts with young patients. To gain high performance
the foundation should regular monitor the individual monitoring of the system.
Security: It signifies the high level security that is required in a system. Weak security to
Headspace application might lead to breach. This might affect personal information of patients
stored in database. Therefore, strong security controls should be imposed on Headspace
application.
Review of cloud based:
Cloud based solution includes computer networks, storage, resources and applications
that can be retrieved with the help of internet. The cloud service providers provides the
infrastructure for implementing cloud based solutions (Duan, Faker, Fesak & Stuart, 2013). In
headspace situation, the application runs through mobile phones or computers and therefore it
appeared appropriate to implement cloud based solution. After implementing cloud based
solution, patients and professionals will always be able to access, store and share information.

7SYSTEM ANALYSIS AND DESIGN
Strengths of cloud based solution:
Cloud based systems have proven to reduce IT expenses. It eliminates the cost of
traditional desktop software along with licensing fees for multiple users. Therefore, cloud based
systems are more cost efficient (Apostu et al., 2013). Additionally, it provides flexibility to
access. Information can be accessed from anywhere. This feature allows the user to travel from
one geographic location to another, yet able to access key information. Backup and recovery
from cloud becomes significantly easy that is not possible through physical hardware.
Weaknesses of cloud based solution:
One of the main weakness of cloud based system is threats to security. Headspace and
other similar organisation are handing key information of the patients to a third party (Patel et al.,
2013). Threat to security lies here. Information stored in cloud are at great risk of being
compromised. As a result, Headspace cloud based system is prone to external attacks and threats.
It also provides poor customer service. Headspace is a foundation that will receive several
responses from professionals and patients. It will become difficult to add the increasing technical
aspects to cloud.
Environment in which cloud based solution is deployed:
Cloud based systems successfully operates in reliable and fast internet connection
environment. They also work well with strong bandwidth internet service (Modi et al., 2013).
However, internet service in regional NSW is poor and unstable. As a result, young individuals
faces problem while accessing the network. Therefore, Headspace should give priority to this
issue before launching the application. Lack of proper internet environment might lead to
product failure. If cloud based solution is launched, the people will not have access to various

8SYSTEM ANALYSIS AND DESIGN
hardware such as wireless router, smartphones and PC. Therefore, Headspace should investigate
the environment prior to the launch of cloud based system.
SDLC Approach:
It is defined as a set of activities that are divided into several phases of planning, testing
and implementing. The phases are combined and named as System Development Life Cycle
(Dora & Dubey, 2015). There are two types of SDLC approach: predictive SDLC and adaptive
SDLC.
Advantages and disadvantages of Predictive SDLC:
Predictive SDLC uses a chronological method of software development actions. Also
known as, the waterfall approach, predictive SDLC reduces the risk aspects of project (Jawale &
Bhole, 2015). Some of the advantages are predictive SDLC has clear objectives before the start
of project, requirements of the project is fixed, progress of the project can be measured at any
point of time and the approach is plan oriented.
However, the approach faces some disadvantages. They are predictive SDLC is time
consuming, rigid and inflexible. Each step of the project needs to be completed to proceed
further and previous steps cannot be accessed once the step is completed. Additionally, the
approach also has the disadvantage of minimum client interaction.
Advantages and disadvantages of Adaptive SDLC:
The main advantage of adaptive SDLC is flexibility. Features can be added and deleted at
any point of the project life cycle. It has the unique ability to adapt to changes according to

9SYSTEM ANALYSIS AND DESIGN
demand of the project (Stoica, Mircea & Ghilic-Micu, 2013). Also known as, agile method,
adaptive SDLC has proven to consume less time unlike predictive SDLC (Bajwa & Kaur, 2017).
It also facilitates communication between various stakeholders and clients. This helps the
stakeholders to manage the project effectively.
However, some disadvantages prevail in adaptive SDLC. They are lack of planning and it
is the key disadvantage of adaptive SDLC, unnecessary changes by clients and risk of failure.
Unnecessary changes in the project requirements increases the duration of project and
complicates the task.
Figure 3: Predictive SDLC vs Adaptive SDLC

10SYSTEM ANALYSIS AND DESIGN
(Source: "Agile versus Waterfall for CRM Implementation Success | CustomerThink", 2018)
Recommendation:
Predictive SDLC tells clients what to expect however, flexibility of adding features
throughout the project life cycle gives an edge to adaptive SDLC. It provides the feature to
obtain an up to date product at the end of the life cycle of project. It also eliminates all the faults
in design by frequent testing of each component with progress of project. The product will be
launched without the risk of failure. Therefore, Adaptive SDLC is a better option than predictive
SDLC.
Conclusion:
From the above discussions, it can be concluded that non-functional requirements are
crucial for a system design. The report has also explained the function of FURPS in describing
and building a product. There are various strengths and weaknesses of the cloud based system.
However, considering several strengths cloud based systems can be adopted by Headspace to
store, share and access patient information anytime and from anywhere. Finally, both adaptive
and predictive SDLC was studied however, due to several advantages of adaptive SDLC it is
decided that adaptive SDLC is superior to predictive SDLC.

11SYSTEM ANALYSIS AND DESIGN
References:
Abolfazli, S., Sanaei, Z., Ahmed, E., Gani, A., & Buyya, R. (2014). Cloud-based augmentation
for mobile devices: motivation, taxonomies, and open challenges. IEEE Communications
Surveys & Tutorials, 16(1), 337-368.
Agile versus Waterfall for CRM Implementation Success | CustomerThink. (2018). Retrieved
from http://customerthink.com/agile-versus-waterfall-for-crm-implementation-success/
Alrawashdeh, T. A., Muhairat, M., & Althunibat, A. (2013). Evaluating the quality of software in
ERP systems using the ISO 9126 model. International Journal of Ambient Systems and
Applications (IJASA), 1(1), 1-9.
Apostu, A., Puican, F., Ularu, G., Suciu, G., & Todoran, G. (2013). Study on advantages and
disadvantages of Cloud Computing–the advantages of Telemetry Applications in the
Cloud. Recent Advances in Applied Computer Science and Digital Services, 118-123.
Bajwa, J. K., & Kaur, R. (2017). An Adaptive Approach For Test Case Prioritization In
Regression Testing Using Improved Genetic Algorithm.
Campos, F. (2018). FURPS+. Retrieved from
https://qualidadebr.wordpress.com/2008/07/10/furps/
Child, A., & Expert, E. C. I. (2015). Representation and submissions. Migration.

12SYSTEM ANALYSIS AND DESIGN
Dora, S. K., & Dubey, P. (2015). Software Development Life Cycle (SDLC) Analytical
Comparison and Survey on Traditional and Agile Methodology. National Monthly
Referred Journal of Research Science and Technology, 2(8).
Duan, J., Faker, P., Fesak, A., & Stuart, T. (2013). Benefits and drawbacks of cloud-based versus
traditional ERP systems. Proceedings of the 2012-13 course on Advanced Resource
Planning.
Jawale, B., & Bhole, A. T. (2015). Adaptive fuzzy hierarchical cumulative voting: a novel
approach toward requirement prioritization. International Journal of Research in
Engineering and Technology, 4(05).
McGorry, P., Bates, T., & Birchwood, M. (2013). Designing youth mental health services for the
21st century: examples from Australia, Ireland and the UK. The British Journal of
Psychiatry, 202(s54), s30-s35.
Memmel. (2018). Tool-Support for Interdisciplinary and Collaborative User Interface S….
Retrieved from https://de.slideshare.net/memmel/toolsupport-for-interdisciplinary-and-
collaborative-user-interface-specification
Modi, C., Patel, D., Borisaniya, B., Patel, H., Patel, A., & Rajarajan, M. (2013). A survey of
intrusion detection techniques in cloud. Journal of network and computer applications,
36(1), 42-57.

13SYSTEM ANALYSIS AND DESIGN
Patel, A., Taghavi, M., Bakhtiyari, K., & JúNior, J. C. (2013). An intrusion detection and
prevention system in cloud computing: A systematic review. Journal of network and
computer applications, 36(1), 25-41.
Singh, I. (2013). Different Software Quality Model. International Journal on Recent and
Innovation Trands in Computing and Communication, 1(5), 438-442.
Stoica, M., Mircea, M., & Ghilic-Micu, B. (2013). Software Development: Agile vs. Traditional.
Informatica Economica, 17(4).
Suman, M. W., & Rohtak, M. D. U. (2014). A comparative study of software quality models.
International Journal of Computer Science and Information Technologies, 5(4), 5634-
5638.