On the Effects of Continuous Delivery on Code Quality: A Case Study in Industry

2021 ◽  
pp. 103588
Author(s):  
Maluane Rubert ◽  
Kleinner Farias
Keyword(s):  
Continuous Delivery ◽  
Code Quality

scholarly journals Towards Regulatory-Compliant MLOps: Orazivio’s Journey from a Machine Learning Experiment to a Deployed Certified Medical Product

2021 ◽  
Vol 2 (5) ◽  
Author(s):  
Tuomas Granlund ◽  
Vlad Stirbu ◽  
Tommi Mikkonen
Keyword(s):  
Machine Learning ◽  
Joint Replacement ◽  
Medical Product ◽  
Medical Software ◽  
Continuous Delivery ◽  
Development Approach ◽  
Responding To Change ◽  
Agile Software ◽  
Engineering Practices

AbstractAgile software development embraces change and manifests working software over comprehensive documentation and responding to change over following a plan. The ability to continuously release software has enabled a development approach where experimental features are put to use, and, if they stand the test of real use, they remain in production. Examples of such features include machine learning (ML) models, which are usually pre-trained, but can still evolve in production. However, many domains require more plan-driven approach to avoid hazard to environment and humans, and to mitigate risks in the process. In this paper, we start by presenting continuous software engineering practices in a regulated context, and then apply the results to the emerging practice of MLOps, or continuous delivery of ML features. Furthermore, as a practical contribution, we present a case study regarding Oravizio, first CE-certified medical software for assessing the risks of joint replacement surgeries. Towards the end of the paper, we also reflect the Oravizio experiences to MLOps in regulatory context.

scholarly journals The Relation of Test-Related Factors to Software Quality: A Case Study on Apache Systems

2021 ◽  
Vol 26 (2) ◽  
Author(s):  
Fabiano Pecorelli ◽  
Fabio Palomba ◽  
Andrea De Lucia
Keyword(s):  
Software Quality ◽  
Compelling Evidence ◽  
Related Factors ◽  
Code Coverage ◽  
Production Code ◽  
Software Code ◽  
Class Test ◽  
Code Quality ◽  
Lack Of Knowledge

AbstractTesting represents a crucial activity to ensure software quality. Recent studies have shown that test-related factors (e.g., code coverage) can be reliable predictors of software code quality, as measured by post-release defects. While these studies provided initial compelling evidence on the relation between tests and post-release defects, they considered different test-related factors separately: as a consequence, there is still a lack of knowledge of whether these factors are still good predictors when considering all together. In this paper, we propose a comprehensive case study on how test-related factors relate to production code quality in Apache systems. We first investigated how the presence of tests relates to post-release defects; then, we analyzed the role played by the test-related factors previously shown as significantly related to post-release defects. The key findings of the study show that, when controlling for other metrics (e.g., size of the production class), test-related factors have a limited connection to post-release defects.

An Empirical Study on the Effect of Testing on Code Quality Using Topic Models: A Case Study on Software Development Systems

2017 ◽  
Vol 66 (3) ◽  
pp. 806-824 ◽  
Author(s):  
Tse-Hsun Chen ◽  
Stephen W. Thomas ◽  
Hadi Hemmati ◽  
Meiyappan Nagappan ◽  
Ahmed E. Hassan
Keyword(s):  
Empirical Study ◽  
Software Development ◽  
Topic Models ◽  
Code Quality

Android Applications based on software repository analysis

2019 ◽  
Vol 1 (2) ◽  
pp. 6-13
Author(s):  
Tayse Virgulino Ribeiro
Keyword(s):  
Development Process ◽  
Software Evolution ◽  
Quality Criteria ◽  
Quality Factors ◽  
Software Repositories ◽  
Software Refactoring ◽  
Related Quality ◽  
Android Applications ◽  
Code Quality

Context: Software repositories have been a source for studies about software evolution and its relation to software defects. In addition, the context of repositories has also been used for the purpose of analyzing refactoring practiced by programmers throughout the development process. Objective: Our objective is based on android projects stored in software repositories, to determine what types of transformations, that is, which refactorings are used, seeking to relate them to quality and security factors. Method: This research uses as an approach an exploratory study of a qualitative character, based on a systematic review of the literature, which will be carried out between the period from 2015 to 2019, as well as the application of research and quality criteria regarding the work context. In addition, develop a case study with projects for Android, relating refactoring quality criteria to non-aggregated projects in software repositories, glimpsing comparative and resulting factors. Expected results: It is expected with this review analysis and a summary of existing literature on Code Quality in the process of Software Refactoring for Android projects. Conclusions: The research is guided by this approach in identifying the types of refactorings practiced and extracting the related quality factors in the development process. We believe that our results will benefit in the updating and summary of the literature in the context of refactoring, glimpsing comparative factors.

scholarly journals Analysis on Relationship between Code Quality and Code Coverage in an XP Environment: A Case Study on the SWURV Project

2021 ◽  
Author(s):  
Hua Li
Keyword(s):  
Defect Density ◽  
Extreme Programming ◽  
Acceptance Testing ◽  
Code Coverage ◽  
Software Products ◽  
Root Cause ◽  
Residual Defect ◽  
Software Product ◽  
Code Quality

The thesis used hypothesis testing and correlation analysis methods to explore the relationship between structural code coverage and the quality of software developed in an eXtreme Programming (XP) environment, via a case study of a commercial software product. We find that improving code coverage is helpful to detect residual defects, but it is not enough, and we also need other testing, like acceptance testing, in the process of XP software development to provide good quality software products. In addition, in order to investigate why the strength of association between code coverage and residual defect density is not as strong as that presented in prior work, a detailed defect root cause analysis is performed, showing that over 96% of bugs cannot be detected by improving code coverage. Based on the defect categories and distribution of defect root cause, six improvement actions are proposed for future XP projects.

Sign in / Sign up

Export Citation Format

Share Document