A systematic mapping study of infrastructure as code research

Morris, 2016

Parnin, 2017, The top 10 adages in continuous deployment, IEEE Softw., 34, 86, 10.1109/MS.2017.86

P. Labs, Puppet Documentation, 2017, (https://docs.puppet.com/). [Online; accessed 10-October-2017].

Jiang, 2015, Co-evolution of infrastructure and source code: An empirical study, 45

Sharma, 2016, Does your configuration code smell?, 189

Petersen, 2008, Systematic mapping studies in software engineering, 68

Kitchenham, 2011, Using mapping studies as the basis for further research a participant-observer case study, Inf. Softw. Technol., 53, 638, 10.1016/j.infsof.2010.12.011

Li, 2015, A systematic mapping study on technical debt and its management, J. Syst. Softw., 101, 193, 10.1016/j.jss.2014.12.027

Yusifolu, 2015, Software test-code engineering: a systematic mapping, Inf. Softw. Technol., 58, 123, 10.1016/j.infsof.2014.06.009

Elberzhager, 2012, Reducing test effort: a systematic mapping study on existing approaches, Inf. Softw. Technol., 54, 1092, 10.1016/j.infsof.2012.04.007

Seriai, 2014, Validation of software visualization tools: a systematic mapping study, 60

Kitchenham, 2007, Guidelines for performing Systematic Literature Reviews in Software Engineering

Kitchenham, 2013, Trends in the quality of human-centric software engineering experiments–a quasi-experiment, IEEE Trans. Softw. Eng., 39, 1002, 10.1109/TSE.2012.76

Saldana, 2015

Humble, 2010

Shambaugh, 2016, Rehearsal: a configuration verification tool for puppet, SIGPLAN Not., 51, 416, 10.1145/2980983.2908083

da Silva, 2010, A critical appraisal of systematic reviews in software engineering from the perspective of the research questions asked in the reviews, 33:1

Hanappi, 2016, Asserting reliable convergence for configuration management scripts, SIGPLAN Not., 51, 328, 10.1145/3022671.2984000

Ikeshita, 2017, Test suite reduction in idempotence testing of infrastructure as code, 98

Weiss, 2017, Tortoise: interactive system configuration repair, 625

Hummer, 2013, Automated testing of chef automation scripts, 4:1

Kosar, 2016, Domain-specific languages: a systematic mapping study, Inf. Softw. Technol., 71, 77, 10.1016/j.infsof.2015.11.001

Novais, 2013, Software evolution visualization: a systematic mapping study, Inf. Softw. Technol., 55, 1860, 10.1016/j.infsof.2013.05.008

Jalali, 2010, Agile practices in global software engineering - a systematic map, 45

Kitchenham, 2010, What’S up with software metrics? - a preliminary mapping study, J. Syst. Softw., 83, 37, 10.1016/j.jss.2009.06.041

Condori-Fernandez, 2009, A systematic mapping study on empirical evaluation of software requirements specifications techniques, 502

Engstrom, 2011, Software product line testing - a systematic mapping study, Inf. Softw. Technol., 53, 2, 10.1016/j.infsof.2010.05.011

Paternoster, 2014, Software development in startup companies: a systematic mapping study, Inf. Softw. Technol., 56, 1200, 10.1016/j.infsof.2014.04.014

Riaz, 2015, How have we evaluated software pattern application? a systematic mapping study of research design practices, Inf. Softw. Technol., 65, 14, 10.1016/j.infsof.2015.04.002

Jabbari, 2016, What is devops?: A systematic mapping study on definitions and practices, 12:1

Pahl, 2016, Microservices: A systematic mapping study, 137

Rodriguez, 2017, Continuous deployment of software intensive products and services: a systematic mapping study, J. Syst. Softw., 123, 263, 10.1016/j.jss.2015.12.015

Alshuqayran, 2016, A systematic mapping study in microservice architecture, 44

Kuhrmann, 2017, On the pragmatic design of literature studies in software engineering: an experience-based guideline, Empirical Softw. Eng., 22, 2852, 10.1007/s10664-016-9492-y

Zhang, 2011, Identifying relevant studies in software engineering, Inf. Softw. Technol., 53, 625, 10.1016/j.infsof.2010.12.010

Wohlin, 2014, Guidelines for snowballing in systematic literature studies and a replication in software engineering, 38:1

Krum, 2013

Httermann, 2012

Cohen, 1960, A coefficient of agreement for nominal scales, Educ. Psychol. Meas., 20, 37, 10.1177/001316446002000104

Burcham, 2017, Characterizing scientific reporting in security literature: An analysis of acm ccs and ieee s&p papers, 13

Wohlin, 2012

Yang, 2009, A survey of coverage-based testing tools, Comput. J., 52, 589, 10.1093/comjnl/bxm021

Portillo-Rodriguez, 2012, Tools used in global software engineering: a systematic mapping review, Inf. Softw. Technol., 54, 663, 10.1016/j.infsof.2012.02.006

Landis, 1977, The measurement of observer agreement for categorical data, Biometrics, 33, 159, 10.2307/2529310

Kitchenham, 2002, Preliminary guidelines for empirical research in software engineering, IEEE Trans. Softw. Eng., 28, 721, 10.1109/TSE.2002.1027796

de Gouw, 2015, On the integration of automatic deployment into the abs modeling language, 49

Sandobalin, 2017, End-to-end automation in cloud infrastructure provisioning

Dolstra, 2013, Charon: Declarative provisioning and deployment, 17

Baset, 2017, Usable declarative configuration specification and validation for applications, systems, and cloud, 29

Wettinger, 2014, Devopslang - bridging the gap between development and operations, 108

Miglierina, 2017, Towards omnia: A monitoring factory for quality-aware devops, 145

Brown, 1998

Kissel, 2011

Rahman, 2016, Software security in devops: Synthesizing practitioners’ perceptions and practices, 70

McGraw, 2018

Rahman, 2015, Synthesizing continuous deployment practices used in software development, 1

Shaw, 2003, Writing good software engineering research papers: Minitutorial, 726

Stol, 2016, Grounded theory in software engineering research: A critical review and guidelines, 120