Metrics for Software Reliability: a Systematic Mapping Study

Ronchieri, Elisabetta; Canaparo, Marco

doi:10.3233/jid-2018-0008

Cited by 12 publications

(5 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The primary focus of work in a community like Debian is on configuring and testing packages for interoperability, rather than making changes to internal code design. In applying our method to Debian for this study, we follow a series of authors who have argued for a focus on a community's effectiveness at resolving the inevitable issues that arise instead of artifact-focused measures [4,11,53,54,55,56]. Specifically, our measure of quality is the speed at which bugs are resolved.…”

Section: B Step 2: Identify a Measure Of Qualitymentioning

confidence: 99%

Underproduction: An Approach for Measuring Risk in Open Source Software

Champion¹,

Hill²

2021

Preprint

View full text Add to dashboard Cite

The widespread adoption of Free/Libre and Open Source Software (FLOSS) means that the ongoing maintenance of many widely used software components relies on the collaborative effort of volunteers who set their own priorities and choose their own tasks. We argue that this has created a new form of risk that we call 'underproduction' which occurs when the supply of software engineering labor becomes out of alignment with the demand of people who rely on the software produced. We present a conceptual framework for identifying relative underproduction in software as well as a statistical method for applying our framework to a comprehensive dataset from the Debian GNU/Linux distribution that includes 21,902 source packages and the full history of 461,656 bugs. We draw on this application to present two experiments: (1) a demonstration of how our technique can be used to identify at-risk software packages in a large FLOSS repository and (2) a validation of these results using an alternate indicator of package risk. Our analysis demonstrates both the utility of our approach and reveals the existence of widespread underproduction in a range of widelyinstalled software components in Debian.

show abstract

Section: B Step 2: Identify a Measure Of Qualitymentioning

confidence: 99%

Underproduction: An Approach for Measuring Risk in Open Source Software

Champion¹,

Hill²

2021

Preprint

View full text Add to dashboard Cite

show abstract

“…Esta se construyó usando los criterios PICOC que son una excelente forma de estructurar conceptos de manera ordenada, metodológica y abarcando todos los temas que se desean encontrar (Souza et al, 2018). Las bases bibliográficas utilizadas fueron: ACM Digital Library, EBSCO Information Services, IEEE Digital Library y ScienceDirect, que son aptas para realizar búsquedas sistemáticas en el contexto de la ingeniería de software (Ronchieri and Canaparo, 2019). Además, se añadió Scopus pues se considera la mayor base de datos bibliográfica de artículos científicos y de investigación.…”

Section: Estrategia De Búsquedaunclassified

Reutilización de software en la robótica industrial: un mapeo sistemático

Solís

Hurtado

2020

Rev. iberoam. autom. inform. ind.

View full text Add to dashboard Cite

<p>Existe una tendencia a utilizar los enfoques de reutilización de software en el dominio de los sistemas robóticos industriales, con el fin de acelerar su desarrollo. Aunque algunos estudios muestran los beneficios de desarrollar usando diferentes enfoques de reutilización, estas prácticas no se han incorporado masivamente en la industria, principalmente, debido al desarrollo de software propietario por parte de los fabricantes y a la diversidad del hardware subyacente. Sin embargo, estos estudios han sido de gran valor para avanzar en su adopción. A través de un mapeo sistemático de la literatura, se muestra la adopción de los diferentes enfoques de reutilización, dentro de los cuales se analizan los más utilizados como la ingeniería dirigida por modelos MDE (Model-Driven Engineering), el desarrollo basado en componentes CBSE (Component-based Software Engineering) y la arquitectura basada en servicios (SOA). Por otro lado, se analizan los marcos de trabajo por ser las soluciones más utilizados y en términos de herramientas, se enfatiza en ROS (Robot Operating System) como una plataforma de referencia para el desarrollo rápido de aplicaciones. El principal reto identificado en esta área de estudio es definir estrategias combinadas y prácticas de los enfoques de reutilización MDE, CBSE y SOA, con el fin de aprovechar las diferentes ventajas de reutilización que cada uno ofrece.</p>

show abstract

“…It can be difficult to predict the effect of a change on software quality, as evidenced by the extensive research on e.g. defect prediction [2,3] or software reliability estimation [4]. Moreover, there are cases in which it is not feasible to test for all necessary scenarios, e.g.…”

Section: Introductionmentioning

confidence: 99%

Controlled Experimentation in Continuous Experimentation: Knowledge and Challenges

Auer¹,

Ros²,

Kaltenbrunner³

et al. 2021

Preprint

View full text Add to dashboard Cite

Context: Continuous experimentation and A/B testing is an established industry practice that has been researched for more than 10 years. Our aim is to synthesize the conducted research.Objective: We wanted to find the core constituents of a framework for continuous experimentation and the solutions that are applied within the field. Finally, we were interested in the challenges and benefits reported of continuous experimentation.Method: We applied forward snowballing on a known set of papers and identified a total of 128 relevant papers. Based on this set of papers we performed two qualitative narrative syntheses and a thematic synthesis to answer the research questions.Results: The framework constituents for continuous experimentation include experimentation processes as well as supportive technical and organizational infrastructure. The solutions found in the literature were synthesized to nine themes, e.g. experiment design, automated experiments, or metric specification. Concerning the challenges of continuous experimentation, the analysis identified cultural, organizational, business, technical, statistical, ethical, and domain-specific challenges. Further, the study concludes that the benefits of experimentation are mostly implicit in the studies.Conclusions: The research on continuous experimentation has yielded a large body of knowledge on experimentation. The synthesis of published research presented within include recommended infrastructure and experimentation process models, guidelines to mitigate the identified challenges, and what problems the various published solutions solve.

show abstract

Metrics for Software Reliability: a Systematic Mapping Study

Cited by 12 publications

References 0 publications

Underproduction: An Approach for Measuring Risk in Open Source Software

Underproduction: An Approach for Measuring Risk in Open Source Software

Reutilización de software en la robótica industrial: un mapeo sistemático

Controlled Experimentation in Continuous Experimentation: Knowledge and Challenges

Contact Info

Product

Resources

About