“…The identified gaps can potentially direct future research in that particular domain [8]. Researchers have conducted systematic mapping studies in numerous domains of software engineering, for example, in the domain of technical debt [9], testing [10] [11], and software visualization [12]. Despite growing interest in IaC, we observe limited evidence of systematic mapping studies that have been conducted in the domain of IaC.…”
Section: Introductionmentioning
confidence: 84%
“…Yusifoglu et al [10] studied 60 publications on software test code engineering and observed that the two leading avenues of research in the area of software test code engineering are tools and methods. Seriai et al [12] studied 87 publications related to validation of software visualization tools and observed the lack of maturity in validation of software visualization tools. Riaz et al [29] studied 30 publication of software patterns and observed that software patterns in maintenance is the most commonly investigated domain in the research field of software patterns.…”
Section: Prior Research On Systematic Mapping Studiesmentioning
Context: Infrastructure as code (IaC) is the practice to automatically configure system dependencies and to provision local and remote instances. Practitioners consider IaC as a fundamental pillar to implement DevOps practices, which helps them to rapidly deliver software and services to end-users. Information technology (IT) organizations, such as Github, Mozilla, Facebook, Google and Netflix have adopted IaC. A systematic mapping study on existing IaC research can help researchers to identify potential research areas related to IaC, for example, the areas of defects and security flaws that may occur in IaC scripts.Objective: The objective of this paper is to help researchers identify research areas related to infrastructure as code (IaC) by conducting a systematic mapping study of IaC-related research.Methodology: We conduct our research study by searching six scholar databases.We collect a set of 33,887 publications by using seven search strings. By systematically applying inclusion and exclusion criteria, we identify 31 publications related to IaC. We identify topics addressed in these publications by applying qualitative analysis.
Results:We identify four topics studied in IaC-related publications: (i) framework/tool for infrastructure as code; (ii) use of infrastructure as code; (iii) em-pirical study related to infrastructure as code; and (iv) testing in infrastructure as code. According to our analysis, 52% of the studied 31 publications propose a framework or tool to implement the practice of IaC or extend the functionality of an existing IaC tool.Conclusion: Our findings suggest that framework or tools is a well-studied topic in IaC research. As defects and security flaws can have serious consequences for the deployment and development environments in DevOps, along with other topics, we observe the need for research studies that will study defects and security flaws for IaC.
“…The identified gaps can potentially direct future research in that particular domain [8]. Researchers have conducted systematic mapping studies in numerous domains of software engineering, for example, in the domain of technical debt [9], testing [10] [11], and software visualization [12]. Despite growing interest in IaC, we observe limited evidence of systematic mapping studies that have been conducted in the domain of IaC.…”
Section: Introductionmentioning
confidence: 84%
“…Yusifoglu et al [10] studied 60 publications on software test code engineering and observed that the two leading avenues of research in the area of software test code engineering are tools and methods. Seriai et al [12] studied 87 publications related to validation of software visualization tools and observed the lack of maturity in validation of software visualization tools. Riaz et al [29] studied 30 publication of software patterns and observed that software patterns in maintenance is the most commonly investigated domain in the research field of software patterns.…”
Section: Prior Research On Systematic Mapping Studiesmentioning
Context: Infrastructure as code (IaC) is the practice to automatically configure system dependencies and to provision local and remote instances. Practitioners consider IaC as a fundamental pillar to implement DevOps practices, which helps them to rapidly deliver software and services to end-users. Information technology (IT) organizations, such as Github, Mozilla, Facebook, Google and Netflix have adopted IaC. A systematic mapping study on existing IaC research can help researchers to identify potential research areas related to IaC, for example, the areas of defects and security flaws that may occur in IaC scripts.Objective: The objective of this paper is to help researchers identify research areas related to infrastructure as code (IaC) by conducting a systematic mapping study of IaC-related research.Methodology: We conduct our research study by searching six scholar databases.We collect a set of 33,887 publications by using seven search strings. By systematically applying inclusion and exclusion criteria, we identify 31 publications related to IaC. We identify topics addressed in these publications by applying qualitative analysis.
Results:We identify four topics studied in IaC-related publications: (i) framework/tool for infrastructure as code; (ii) use of infrastructure as code; (iii) em-pirical study related to infrastructure as code; and (iv) testing in infrastructure as code. According to our analysis, 52% of the studied 31 publications propose a framework or tool to implement the practice of IaC or extend the functionality of an existing IaC tool.Conclusion: Our findings suggest that framework or tools is a well-studied topic in IaC research. As defects and security flaws can have serious consequences for the deployment and development environments in DevOps, along with other topics, we observe the need for research studies that will study defects and security flaws for IaC.
“…For gathering the terms for visualization, we selected them from 7 surveys and studies in the area of visualization. [38][39][40][41][42][43][44] Again, none of these works relate to SPLE.…”
Section: Conduct Search For Primary Sourcesmentioning
confidence: 99%
“…Seriai et al performed an SMS on the validation of visualization tools. 39 Their main finding was that despite the increasing research and application of visualization techniques, their evaluation lacks rigor. Novais et al performed an SMS in software evolution visualization.…”
Software product lines (SPLs) are families of related systems whose members are distinguished by the set of features they provide. Over 2 decades of research and practice can attest to the substantial benefits of applying SPL practices such as better customization, improved software reuse, and faster time to market. Software product line engineering (SPLE) refers to the paradigm of developing SPLs. Typical SPLE efforts involve a large number of features that are combined to form also large numbers of products, implemented using multiple and different types of software artifacts. Because of the sheer amount of information and its complexity, visualization techniques have been used for different SPLE activities. In this paper, we present an extended systematic mapping study on this subject. Our research questions aim to gather information regarding the techniques that have been applied, at what SPLE activities, how they were implemented, the publication fora used, the methods of empirical evaluation, and the provenance of the evaluation examples. Our driving goal is to identify common trends, gaps, and opportunities for further research and application.
“…Unfortunately, not many of them have been empirically evaluated, which indicates 202 Enfoque UTE, V.7-Sup. 1, Feb.2017, pp.201 -216 that the systematic, disciplined, and controlled method for evaluating visualization techniques provided by experimentation has hardly been used (Wettel et al, 2011;Shahin et al, 2014;Seriai et al, 2014). As a consequence, several studies have highlighted the need for an objective evaluation of the proposed visualization techniques that allows researchers and practitioners to identify the pros and cons of applying them for performing typical software engineering activities.…”
Muchos investigadores han señalado la falta de estudios empíricos que sistemáticamente examinen las ventajas y desventajas del uso de técnicas de visualización para soportar la comprensión del software. Estos estudios son indispensables para recolectar y analizar evidencia objetiva y cuantificable acerca de la utilidad de las técnicas de visualización y herramientas propuestas, y más aún, para servir como guía de la investigación en visualización de software. En este estudio, 6 tareas típicas de comprensión de software fueron realizadas por 20 estudiantes de un curso de ingeniería de software. Se midió el tiempo de respuesta y se calificó la exactitud en las respuestas de los participantes. Los resultados indican que, por una parte, el uso de la técnica de visualización basada en grafos mejoró la exactitud en las respuestas de los estudiantes (21.45% en promedio); por otra parte, no se encontró evidencia significativa de reducción en el tiempo gastado por los estudiantes para resolver las tareas de comprensión de software.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.