Comparing Predictive and Adaptive SDLC

This assignment delves into a comparative analysis of two prominent software development methodologies: Predictive and Adaptive SDLC. It examines the strengths and weaknesses of each approach, highlighting their suitability for different project requirements. The discussion encompasses factors such as time management, client satisfaction, adaptability to change, and technological considerations.

Report

Contents
Introduction......................................................................................................................................1
Non-Functional Requirements.........................................................................................................1
System Interface..........................................................................................................................3
User Interface...............................................................................................................................3
Constraints...................................................................................................................................3
Solution for the cloud......................................................................................................................4
SDLC Approach..............................................................................................................................4
Pros of ‘Predictive’ SDLC...........................................................................................................4
Cons of Predictive’ SDLC...........................................................................................................5
Pros of Adaptive SDLC...............................................................................................................5
Cons of Adaptive SDLC..............................................................................................................6
Recommendations............................................................................................................................6
References........................................................................................................................................7

Introduction
The focus of the report is based on handling the cloud based solutions with the different aspects
of data security. It includes the data ownership and how Headspace can match with the different
aspects of cloud solution. The sets of the critical system qualities and the system interfaces works
over the usability, reliability and performance. The aim is mainly to handle the changes related to
the e-health records with proper creating, testing and handling the deployment of the information
system. The system configuration patterns are related to the forms where SDLC approach
includes the components like the input from the user as well as uploading the different inputs as
well. In this, the focus is on the functional aspects as well as the other forms of the non-learning
sides which works over the usability, reliability (Krausz et al., 2016). The Mental Health
Professionals are hired for the same where a proper carrying and working on the project will help
in looking forward towards the development of the work in Headspace. It also includes the
travelling back with setting up different locations as well as handling the consumption of time.
Here, the forms are related to the cloud computing with the focus over the alleviation of the
problems.
Non-Functional Requirements
It includes the operations where the possibilities are depending upon the behavioural changes
and the non-functional requirements. The project is based on the quality which depends on the
usability, access and the availability patterns. This also includes the performance and the security
development which comes with:
a. The Usability where the project development is depending upon how the applications or
the websites can work on the needs of the person (Russell, 2015). The websites need to

be properly addressed so that the usability of the e-health records could be done in a
proper manner.
b. The accessibility is based on the different records where the user works over the
maintenance of the records and then working over the check-up and the system updates
as well.
c. The availability formats work on the health records which includes the forms related to
the online format. The check is over the records to handle the doctor sitting and work on
it over the click of button.
d. The reliability is based on working for the health records which includes the availability
to handle the system loading. The forms are set to define the methods of recovery with
handling and loading the records where the concurrency is set for the different people.
e. The performance standards are mainly to handle the accessibility of the records which are
mainly for application or the website. They can easily load faster without any faster
delays in the system. Here, it is seen that there is a need of the lower response time as
well.
f. The security standards are set with the encryption of the data and the protection of the
same (Dowling et al, 2013). The project is mainly related to the storage of information of
the different personal records. Along with this, the importance is about handling the
security with the 2-step authentication process where the users can handle the data
security and keep it secured as well.
g. “+” is mainly to work towards the handling of non-invasive factors. Here, the patients’
needs to take care of the UI and their exact requirements which are related to colour
coded schemes and the support of the multi-language system etc.

System Interface
The forms of the data are based on handling the applications, server and the storage. This is
important and considered depending upon the proper management where the enterprise
management works over the computing of the capabilities and then processing the data
depending upon privately owned cloud. This will also lead to the minimisation of the up-front
structure and then handling the organisation to work over the core business structure. The
improved management and the capacity networks are related to the business demands where the
“pay-as-you-go” infrastructure model is to work over the high capacity networks with easy
working over the hardware virtualisation (Griffiths et al., 2007).
User Interface
This is based on working over interaction through the different UI interface. Along with this, the
check is on handling the optimisation programs with the better user experience. This includes the
forms related to the strong interface and the setup of the program development.
Constraints
As per the analysis, there are possibilities where the internet can handle the vulnerability to
attack with major limitations over the controlled management, application, data and the services.
It is important to focus over the different solutions which works over the security system as well
as the other privacy standards.
Solution for the cloud
This works over the reports that are related to the technology development and how the
government can work over the non-profitable technology. The work is set over the business
systems in the cloud and how the benefits are set when compared to the other running parts.

This is based on working towards the headspace nature where the need to is cooperate with the
different forums and the organisations (Liacos et al., 2014). This differs with the IaaS that is
integrated through allowing the services as well as the high-level development. There are certain
issues related to the high level of flexibility where the forms are related to work over the tailored
solutions. The organisation need to focus on sharing the stories which are related to deployment
of the solutions and working over the mass application patterns.
With the different solutions for the Headspace, PaaS and IaaS focus on working towards the
collaboration and the higher flexibility in the system. Here, the information is being shared
across in the different forms which is relative to handle the lower levels of the tailored solutions.
There are different features which needs to be accommodated with the working over the
distributed nature, where the exchange in the information is related to set for systems.
SDLC Approach
Pros of ‘Predictive’ SDLC
A stabilised requirement is based on working over the risks analysis with the predictive SDLC. It
works over the speedy delivery of the system towards the development process and the
predictive growth (Rickwood, 2012). It has been seen that the predictive analysis is based on
risks analysis depending upon the future development along with taking hold of the minimised
changes to the requirements. Along with this, the identification of the system requirements is
long with the documented requirements, where the product is also stable and the technology is
well-understood.

Cons of Predictive’ SDLC
The time factor is the major issue to meet the requirements of the client. Here, the limited
reusability forms of requirements need to work over providing and working over the
development system. Along with this, development by the clients and the designing patterns
need to be specific before the programming begins. With this, all the important requirements
which are missed, expensive post-implementation programming also needs to be analysed. This
will help in bringing the change to the emergence of response with the increased complexity
requirements and handling the technological environments (Child et al., 2015). The limited scope
processes are constraints that need to be handled through the implementation over the tight
system budget.
Pros of Adaptive SDLC
It is important to focus on the client satisfaction where the adaptive approach works over
satisfying the demands that is customer focused. The support does not fit the iteration project
model but the support phase is treated to follow on the projects where there is a complete revert
to the predictive model which becomes to be the major support phase. This will help in the
maintenance of the system, enhancement and the support of the users. The methodology is based
on the guidelines and the procedures where one way is to support the users to provide the help
desk type of capability.
Cons of Adaptive SDLC
The standards are set to meet the requirements based on the development of the project. Along
with this, the focus is on the use of adaptive approach where the new person cannot easily have a

trust till he becomes the experienced user (Russell, 2015). There are certain forms of the unclear
requirements which needs to be handled based on how customers adapt to the clear requirements.
Recommendations
The use of the SDLC adaptive approach is important which is agile approach based on the robust
changes. Here, there is a major scope of improvement which includes the organisation and how
the government not only works over the unplanned projects but try to work over the
implementation towards the growth of the project.