Healthcare Application Development Models

The assignment delves into the application of Software Development Life Cycle (SDLC) models in developing healthcare applications. It focuses on comparing two models: Predictive SDLC and Adaptive SDLC. The analysis discusses the pros and cons of each model, emphasizing the relevance of the adaptive approach due to its flexibility in handling evolving client requirements and unplanned project changes. The assignment concludes with a recommendation favoring the adaptive SDLC for healthcare application development, considering its robustness and adaptability to the dynamic nature of the industry.

report

Contents
Introduction......................................................................................................................................1
Non- Functional Requirements........................................................................................................1
System Interface..........................................................................................................................3
User Interface...............................................................................................................................3
System constraints.......................................................................................................................3
Cloud Solution.................................................................................................................................3
SDLC Approach..............................................................................................................................4
Pros of ‘Predictive’ SDLC...........................................................................................................4
Cons of Predictive SDLC............................................................................................................4
Pros of Adaptive SDLC...............................................................................................................5
Cons of Adaptive SDLC..............................................................................................................5
Recommendation.............................................................................................................................5
References........................................................................................................................................7

Introduction
The focus of the report is on the discussion of Headspace company which includes the discussion
of how the cloud based solutions are important to work on the different security standards of the
data. With this, the major aim is to bring the change in the e-health records and then work over
the testing, deployment and the proper configuration of the information system. The concepts are
related to work over the adaptive and the predictive SDLC technology where the entire process is
mainly for the usability, reliability, and handling the non-functional standards. This includes the
use of the user inputs and the constraints of the system interface, user interface. It is important
for the Headspace to work over the time consumption patterns with the alleviation of the
problems related to how the non-functional requirements can operate the system behaviour.
Non- Functional Requirements
Here, the forms are set to relate with the system behaviour and how the non-functional
requirements can meet the project scope and the e-health records of the system. Here, the aspects
are related to the usability, availability, performance and the proper security standards which
needs to focus on the requirement standards:
Usability: This is mainly to focus on how the projects can handle the applications with the
website setup that is important for the person. The addressing of different issues and then
determining the different forms of the backgrounds is important for the proper ethical and the
cultural development. (Gai et al., 2016).
Accessibility: The access is depending upon maintaining the system records and then improving
the quality to check over the system patterns and then update the requirements of the system.

Availability: It works on the forms where the health records need to be checked properly with
the focus on how the people can make use of the data that is stored in the online format. Along
with this, there is a proper check over the system patterns about whether the doctor is available
and whether the updates are done in the timely manner. (Hwang, 2017).
Reliability: This is related to the forms where reliability and the other health records are set to
determine about the system loading and how it is easy it is to work on the different records with
the multiple concurrency.
Performance: It is mainly depending upon the forms where there is a need to access the system
functions along with working over the performance standards to check whether the app or the
website works in a proper manner, and can handle the loading of the system in a faster process
where there are no major delays. Along with this, there is a need to check on the response time as
well.
Security: The security standards are related to the protection of the data and the encryption
forms where the project relates to work on handling the different personal records and the other
forms of the different users who can work over the confidentiality and the system integrity. The
proper implementation is important depending upon the end-to-end encryption where the
security is set with the 2-step authentication process. It is mainly to make sure that the data is
secured. (Zhang et al., 2016).
“+” works on the designing and the integration with the factors where the UI needs to meet the
requirements and the different forms of the colour schemes. They are important for handling the
Multilanguage support as well as the other tempting information which are important for
analysing the patients.

System Interface
The forms are related to work on the applications and properly storing the information. For this,
the users can work over the privately-owned network and the cloud computing system. Here, the
forms also work over the IT infrastructure which leads to the minimisation of the infrastructure
forms with the proper management that is important to meet the model of the “pay-as-you-go”.
(Rittinghouse et al., 2016). This works over the capacity networks and how the adoption can
match with the different forms of the hardware systems.
User Interface
Here, the interface is set to work on the different information formats. This includes the forms
where there is a proper interaction of the information through the improvement of the UI
experience. It also includes how Headspace can work on the system optimisation process with
the user experience that is important for the better user experience.
System constraints
The forms are also set to define how internet connection and the attacking vulnerability is set to
check over the customer requirements with the control over the different applications and the
data services. There are different policies which focus over the improvement of system and then
work over the vulnerability maintenance. (Subramanyam et al., 2017).
Cloud Solution
With the improvement of the system, the technology needs to focus on the cloud computing and
then making use of the firewall and the IDS system which is important to handle the different
running parts. For Headspace, it is important to focus on the deployment models of IaaS, PaaS
and SaaS which can work with the higher flexibility of the system. Along with it, there is a

possibility to check on the operating systems and then provide a proper support to work over the
different updates and the instructions. The organisation works over the sharing of the stories and
then working over how the people can make use of different technologies. The support is
depending upon the deployment where the solutions are related to the integrated forms with the
different types of the system.
The solution of the Headspace works over the system tailoring which includes the locations and
the forms of information which are mainly to accommodate and then work over the distributed
nature of the service centre. This works over the handling of the user input data and then
processing the information which is related to the Headspace. The lower levels or the different
tailored solutions also include the sharing through the different forms of the system formats.
SDLC Approach
Pros of ‘Predictive’ SDLC
The stability requirements are based mainly on the analysis of the risks and then work on the
development of the proper application and the website. For this, there is a need to focus on the
speedy delivery which is important for the proper development process. It includes the SDLC
project that works over the shorter span of time with the progress that is important to take hold of
the different specifications of the steps. (Chag et al., 2016). The changes are depending upon the
needs which need to be actualised without any major alteration framework in the system.
Cons of Predictive SDLC
This works over the time factor where the requirements are important to be met. Along with this,
there is a need to focus on the reusability patterns as well as the restrictions which could lead to
the different development stages in the system. Here, the forms are related to the increased

development which is set up by the clients. Along with this, there is a limited form of the process
and the alteration that leads to the change in the technologies with the increased change in the
budget.
Pros of Adaptive SDLC
The pros are mainly related to whether the client is satisfied with the output. For the application,
it is important to focus on whether all the requirements of the hospital are fulfilled. With this,
there is a central focus where the approach is set related to the effective results about the
changing requirements of the customers. Here, it is important to cooperate with the employees
and then work over the system processes and approaches depending upon the different
requirements of the organisation. It works over the system changes and development which leads
to the effective end results. (Beloglazov et al., 2016).
Cons of Adaptive SDLC
The forms are related to the experiences where the professionals must work over the
development and focus on the working with the experienced standards. There are certain
requirements which are based on the forms to specify about whether the customers require them
or not. Hence, the project is based on the adaptive approach so that the development could be
mainly as per the demands of the customer.
Recommendation
It has been seen that there is a need to make use of the adaptive SDLC approach for the health
application. This is important as it will bring the change in the agile methodology which is robust
along with working over the improvement of the scope of system. Along with it, the focus will
be on handling the unplanned projects and the implementation of the project in public.

References
Beloglazov, A., & Buyya, R. (2016). U.S. Patent No. 9,363,190. Washington, DC: U.S. Patent and
Trademark Office.
Chang, V., Kuo, Y. H., & Ramachandran, M. (2016). Cloud computing adoption framework: A security
framework for business clouds. Future Generation Computer Systems, 57, 24-41.
Gai, K., Qiu, M., Zhao, H., Tao, L., & Zong, Z. (2016). Dynamic energy-aware cloudlet-based mobile cloud
computing model for green computing. Journal of Network and Computer Applications, 59, 46-54.
Hwang, K. (2017). Cloud and Cognitive Computing: Principles, Architecture, Programming. MIT Press.
Rittinghouse, J. W., & Ransome, J. F. (2016). Cloud computing: implementation, management, and
security. CRC press.
Subramanyam, G., & Raju, T. N. (2017). A Categorized Multiuser Data Share Environment In A Mobile
Cloud Computing Model. IJSEAT, 5(5), 404-407.
Zhang, H., Jiang, H., Li, B., Liu, F., Vasilakos, A. V., & Liu, J. (2016). A framework for truthful online
auctions in cloud computing with heterogeneous user demands. IEEE Transactions on
Computers, 65(3), 805-818.