Containers in Software Development: A Systematic Mapping Study

Koskinen, Mikael; Mikkonen, Tommi; Abrahamsson, Pekka

doi:10.1007/978-3-030-35333-9_13

Cited by 9 publications

(3 citation statements)

References 70 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Nonetheless, we have also used methods of the SLR guidelines of Kitchenham and Charters for conducting systematic literature reviews [24]. This combined approach (for conducting systematic literature reviews and systematic mapping studies) has already been chosen by several authors in the past (e.g., [12,26]). To increase the traceability and transparency of our systematic mapping study, this approach appears to be useful.…”

Section: Methodsmentioning

confidence: 99%

The Integrated List of Agile Practices -- A Tertiary Study

Neumann¹

2021

Preprint

View full text Add to dashboard Cite

Context: Companies adapt agile methods, practices or artifacts for their use in practice since more than two decades. This adaptions result in a wide variety of described agile practices. For instance, the Agile Alliance lists 75 different practices in its Agile Glossary. This situation may lead to misunderstandings, as agile practices with similar names can be interpreted and used differently. Objective: This paper synthesize an integrated list of agile practices, both from primary and secondary sources. Method: We performed a tertiary study to identify existing overviews and lists of agile practices in the literature. We identified 876 studies, of which 37 were included. Results: The results of our paper show that certain agile practices are listed and used more often in existing studies. Our integrated list of agile practices comprises 38 entries structured in five categories. Contribution: The high number of agile practices and thus, the wide variety increased steadily over the past decades due to the adaption of agile methods. Based on our findings, we present a comprehensive overview of agile practices. The research community benefits from our integrated list of agile practices as a potential basis for future research. Also, practitioners benefit from our findings, as the structured overview of agile practices provides the opportunity to select or adapt practices for their specific needs.

show abstract

Section: Methodsmentioning

confidence: 99%

The Integrated List of Agile Practices -- A Tertiary Study

Neumann¹

2021

Preprint

View full text Add to dashboard Cite

show abstract

“…Software containers are lightweight computational environments containing all necessary elements (code, dependencies, data, configuration, etc.) to execute a certain process [62]. For example, a software container used for research can be a simple Linux environment containing only a specific Python version installed together with analysis packages such as Tensorflow [63].…”

Section: Reusability Tip 7: Provide a Reproducible Computational Envi...mentioning

confidence: 99%

Ten quick tips for building FAIR workflows

de Visser,

Johansson,

Kulkarni

et al. 2023

PLoS Comput Biol

View full text Add to dashboard Cite

Research data is accumulating rapidly and with it the challenge of fully reproducible science. As a consequence, implementation of high-quality management of scientific data has become a global priority. The FAIR (Findable, Accesible, Interoperable and Reusable) principles provide practical guidelines for maximizing the value of research data; however, processing data using workflows—systematic executions of a series of computational tools—is equally important for good data management. The FAIR principles have recently been adapted to Research Software (FAIR4RS Principles) to promote the reproducibility and reusability of any type of research software. Here, we propose a set of 10 quick tips, drafted by experienced workflow developers that will help researchers to apply FAIR4RS principles to workflows. The tips have been arranged according to the FAIR acronym, clarifying the purpose of each tip with respect to the FAIR4RS principles. Altogether, these tips can be seen as practical guidelines for workflow developers who aim to contribute to more reproducible and sustainable computational science, aiming to positively impact the open science and FAIR community.

show abstract

“…Virtual machines allow running the same software on different hardware (Goldberg, 1974). Containers enable bundling together pieces of software that implement a coherent whole that can be deployed independently (Koskinen et al, 2019). Microservice architecture (Nadareishvili et al, 2016) provides instructions how such containers should be best used, to flexibly introduce new configurations, and so on.…”

Section: Software Solutions For Supporting Software Evolutionmentioning

confidence: 99%

Constant Software Updates vs. Public Software Acquisition

Mikkonen

2023

aasf

View full text Add to dashboard Cite

Software industry has widely adopted agile software development model, where it is accepted that change is constant. Indeed, as the environment in which the software is run changes – be it changes in jurisdiction, language, user expectations, reinterpretation or requirements, or something else – the software needs to be modified to satisfy end-user needs. At the same time, many organizations, especially those that operate in the public sector, rely on tendering and detailed requirements documentation when acquiring software, with an assumption that once deployed, the software would continue to serve the end users unaltered or with minor changes covered by a maintenance contract. In this article, we will consider this fundamental mismatch from the viewpoint of what we know about software evolution in general, and then propose ways forward to design and implement public sector software that can be adapted to new, emergent needs.

show abstract

Containers in Software Development: A Systematic Mapping Study

Cited by 9 publications

References 70 publications

The Integrated List of Agile Practices -- A Tertiary Study

The Integrated List of Agile Practices -- A Tertiary Study

Ten quick tips for building FAIR workflows

Constant Software Updates vs. Public Software Acquisition

Contact Info

Product

Resources

About