Adapting Agile Practices During the Evolution of a Healthcare Software Product

2022 ◽  
pp. 777-791
Author(s):  
Danilo F. S. Santos ◽  
André Felipe A. Rodrigues ◽  
Walter O. Guerra Filho ◽  
Marcos Fábio Pereira

Agile Software Development (ASD) can be considered the mainstream development method of choice worldwide. ASD are used due to features such as easy management and embrace of changes, where change in requirements should be taken as a positive feature. However, some domain verticals, such as medical-healthcare, are classified as critical-safety system, which usually requires traditional methods. This chapter presents a practical use case describing the evolution of a software product that was conceived as a wellness software for end-users in mobile platforms to a medical-healthcare product restricted to regulatory standard recommendations. It presents the challenges and how the ASD is compatible to standards such as ISO/IEC 82304-1.

Author(s):  
Danilo F. S. Santos ◽  
André Felipe A. Rodrigues ◽  
Walter O. Guerra Filho ◽  
Marcos Fábio Pereira

Agile Software Development (ASD) can be considered the mainstream development method of choice worldwide. ASD are used due to features such as easy management and embrace of changes, where change in requirements should be taken as a positive feature. However, some domain verticals, such as medical-healthcare, are classified as critical-safety system, which usually requires traditional methods. This chapter presents a practical use case describing the evolution of a software product that was conceived as a wellness software for end-users in mobile platforms to a medical-healthcare product restricted to regulatory standard recommendations. It presents the challenges and how the ASD is compatible to standards such as ISO/IEC 82304-1.


Author(s):  
Muhammad Aminu Umar ◽  
Sheidu Salami Tenuche ◽  
Sahabi Ali Yusuf ◽  
Aminu Onimisi Abdulsalami ◽  
Aliyu Muhammad Kufena

As the popularity and acceptance of agile software development methodologies increases, the need to integrate usability engineering in the design and development processes is imperative. While, agile the focus is on technical and functional requirements not on end-user interaction, usability is usually only dealt with on the side. Combining this two in practice will go a long way in development of better product. Since the success and acceptance of software product depends not only on the technologies used but how well it integrates user-oriented methods. Therefore, this chapter puts together works on how usability engineering has been integrated with agile processes.


2020 ◽  
Vol 6 (2) ◽  
pp. 155-176
Author(s):  
Nobuhiko Seki ◽  
Youji Kohda

A new service concept meets some resistance from those who face it prior to adoption. If the resistance cannot be overcome, the new service will not be diffused. There have been many studies of business-to-consumer (B2C) contexts on adoption and rejection of product and service innovation. The question remains, what barriers should be overcome in the diffusion process of new services in the business-to-business (B2B) contexts? For example, if you implement a new service concept to your organization to create new value with your customers, what barriers does your organization need to overcome? Few studies to date have revealed the issue. To identify barriers for adoption, this study focuses on the diffusion process of the Agile software development method in Japanese organizations, which is still in progress, and attempts to approach the adoption barriers for service innovation in the B2B context to understand the barriers and leverage point for overcoming them. The Agile software development method is an innovation of software development. But there is a possibility that its diffusion will be stopped due to the resistance of project managers involved in a software development. This may lead service systems to value co-destruction as well.


SISFOTENIKA ◽  
2017 ◽  
Vol 7 (1) ◽  
Author(s):  
Gusti Syarifudin ◽  
I Dewa Ayu Eka Yuliani

Penelitian ini bertujuan untuk membangun aplikasi kinerja salesman yang menggunakan mobile device dengan framework JQuery mobile yang mempermudah proses pencatatan orderan, pengecekan stok dan mengontrol sistem kinerja salesman. Penelitian ini, menggunakan metode research and development sebagai bentuk penelitian. Teknik pengumpulan data yang digunakan dalam penelitian ini adalah wawancara, observasi, serta studi dokumentasi. Pemodelan sistem menggunakan unified modeling language, sedangkan metode perancangan aplikasi menggunakan agile software development method dengan pendekatan extreme programming. Untuk membangun web mobile menggunakan bahasa pemrograman PHP (hypertext preprocessor) dengan framework JQuery mobile dan database MySQL. Penelitian ini menghasilkan fitur login salesman, fitur indent, fitur pengontrol kinerja salesman dan menampilkan laporan penjualan secara periode tertentu yang dapat diakses dari perangkat mobile salesman.


JAMIA Open ◽  
2021 ◽  
Vol 4 (4) ◽  
Author(s):  
Andrew R Post ◽  
Jared Luther ◽  
J Maxwell Loveless ◽  
Melanie Ward ◽  
Shirleen Hewitt

Abstract Objective The Huntsman Cancer Institute Research Informatics Shared Resource (RISR), a software and database development core facility, sought to address a lack of published operational best practices for research informatics cores. It aimed to use those insights to enhance effectiveness after an increase in team size from 20 to 31 full-time equivalents coincided with a reduction in user satisfaction. Materials and Methods RISR migrated from a water-scrum-fall model of software development to agile software development practices, which emphasize iteration and collaboration. RISR’s agile implementation emphasizes the product owner role, which is responsible for user engagement and may be particularly valuable in software development that requires close engagement with users like in science. Results All RISR’s software development teams implemented agile practices in early 2020. All project teams are led by a product owner who serves as the voice of the user on the development team. Annual user survey scores for service quality and turnaround time recorded 9 months after implementation increased by 17% and 11%, respectively. Discussion RISR is illustrative of the increasing size of research informatics cores and the need to identify best practices for maintaining high effectiveness. Agile practices may address concerns about the fit of software engineering practices in science. The study had one time point after implementing agile practices and one site, limiting its generalizability. Conclusions Agile software development may substantially increase a research informatics core facility’s effectiveness and should be studied further as a potential best practice for how such cores are operated.


Author(s):  
Iwona Dubielewicz ◽  
Bogumila Hnatkowska ◽  
Zbigniew Huzar ◽  
Lech Tuzinkiewicz

Agile methodologies have become very popular. They are defined in terms of best practices, which aim at developing good quality software faster and cheaper. Unfortunately, agile methodologies do not refer explicitly to quality assurance, which is understood as a planned set of activities performed to provide adequate confidence that a product conforms to established requirements, and which is performed to evaluate the process by which products are developed. The chapter considers the relations of agile practices with software life cycle processes, especially those connected to quality assurance, and tries to answer the question of which agile practices ensure software quality. Next, agile practices associated with quality assurance are assessed from different perspectives and some recommendations for their usage are given. It is observed that modeling has a particular impact on quality assurance.


2020 ◽  
Vol 25 (2) ◽  
pp. 105-116
Author(s):  
Oksana Ņikiforova ◽  
Kristaps Babris ◽  
Jānis Kristapsons

AbstractSoftware development method, which does not have any faults or gaps in project implementation, has not been elaborated so far. Due to this reason, the authors have decided to perform this study to make it easier for the companies, which use one of the agile development methods, to better foresee potential risks and to deal with their consequences. The aim of the research is to identify and classify risks in agile software development methods and the related projects based on the obtained survey data. To achieve the goal, the authors have developed evaluation criteria, as well as implemented practical questionnaire in various software development companies. From the obtained survey data, the risks are classified according to various factors, i.e., the changing highest and lowest priorities and needs in various projects. Thus, the obtained research results can be applied in various areas of project development, changing the order of priority factors.


Author(s):  
Muthu Ramachandran

The demands of SE imply a growing need for using AI to support all aspects of the software development process. This chapter provides insights into the application of knowledge based approaches to the development of agile software development, software product line, software components and architecture. In particular, it presents three research systems that demonstrate the potential benefits of utilising knowledge based approaches to support agile methods. The first system, called SoBA, supports the use of a story card for agile software development; the second system, called .NET designer, provides design rationale for choosing appropriate architectural solutions, and the third system, called RAIS, provides reuse assessment and improvement for designing reusable software components.


Author(s):  
Saikat Gochhait ◽  
Shariq Aziz Butt ◽  
Tauseef Jamal ◽  
Arshad Ali

The software industries follow some patterns (i.e., process model to develop any software product). Agile methodology is the most famous and used process model. It is a trend to develop efficient software products with high client satisfaction. In this chapter, the authors discuss agile methodology and its components, benefits, and drawbacks while using the cloud computing in agile software development, existing frameworks for agile-cloud combination, and some security measures.


Sign in / Sign up

Export Citation Format

Share Document