Continuous practices and devops: beyond the buzz, what does it all mean?

DevOps and continuous practices are attracting steadily growing attention by both practitioners and researchers in the software engineering community. The terms are often used inconsistently, interchangeably and with unclear meaning, however. Taking the position that this ambiguity and miscommunication renders the community great harm, in that it impedes our ability to critically appraise these practices, their effects and interplay between them, we analyze how published literature on both continuous practices and DevOps treat the terms. Based on this analysis, along with statements by often cited sources in the community as well as personal experience from researching and practicing these concepts, we propose guidelines to help authors reduce ambiguity in their publications. Additionally, definitions designed to reflect mainstream interpretation while disentangling the terms from one another are presented.

[1]  Lianping Chen Towards Architecting for Continuous Delivery , 2015, 2015 12th Working IEEE/IFIP Conference on Software Architecture.

[2]  Gianluigi Zavattaro,et al.  Declarative Elasticity in ABS , 2016, ESOCC.

[3]  Jan Bosch,et al.  The continuity of continuous integration: Correlations and consequences , 2017, J. Syst. Softw..

[4]  Jan Bosch,et al.  Achieving traceability in large scale continuous integration and delivery deployment, usage and validation of the eiffel framework , 2016, Empirical Software Engineering.

[5]  Thomas A. Mikalsen,et al.  Continuous Delivery of Composite Solutions: A Case for Collaborative Software Defined PaaS Environments , 2015, BigSystem@HPDC.

[6]  Frank Leymann,et al.  Enabling DevOps Collaboration and Continuous Delivery Using Diverse Application Environments , 2015, OTM Conferences.

[7]  Steven A. Wright,et al.  Open source and standards: The role of open source in the dialogue between research and standardization , 2014, 2014 IEEE Globecom Workshops (GC Wkshps).

[8]  Liming Zhu,et al.  POD-Diagnosis: Error Diagnosis of Sporadic Operations on Cloud Applications , 2014, 2014 44th Annual IEEE/IFIP International Conference on Dependable Systems and Networks.

[9]  Grady Booch,et al.  Object-oriented analysis and design with applications (2nd ed.) , 1993 .

[10]  Jez Humble,et al.  Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation , 2010 .

[11]  Carl Adams Managing crowdsourcing assignments , 2011 .

[12]  Klaas-Jan Stol,et al.  Continuous software engineering: A roadmap and agenda , 2017, J. Syst. Softw..

[13]  Matt Callanan,et al.  DevOps: Making It Easy to Do the Right Thing , 2016, IEEE Software.

[14]  Kari Systä,et al.  ICDO: Integrated cloud-based development tool for DevOps , 2015, SPLST.

[15]  Frank Leymann,et al.  Dyn Tail - Dynamically Tailored Deployment Engines for Cloud Applications , 2015, 2015 IEEE 8th International Conference on Cloud Computing.

[16]  Brian Fitzgerald,et al.  Continuous software engineering and beyond: trends and challenges , 2014, RCoSE 2014.

[17]  Kai Petersen,et al.  Systematic Mapping Studies in Software Engineering , 2008, EASE.

[18]  Mitesh Soni,et al.  End to End Automation on Cloud with Build Pipeline: The Case for DevOps in Insurance Industry, Continuous Integration, Continuous Testing, and Continuous Delivery , 2015, 2015 IEEE International Conference on Cloud Computing in Emerging Markets (CCEM).

[19]  Marina Waldén,et al.  DevOps meets formal modelling in high-criticality complex systems , 2015, QUDOS@SIGSOFT FSE.

[20]  Hong Zhu,et al.  CIDE: An Integrated Development Environment for Microservices , 2016, 2016 IEEE International Conference on Services Computing (SCC).

[21]  Jan Bosch,et al.  Modeling continuous integration practice differences in industry software development , 2014, J. Syst. Softw..

[22]  Pasi Kuvaja,et al.  Dimensions of DevOps , 2015, XP.

[23]  Manish Virmani,et al.  Understanding DevOps & bridging the gap from continuous integration to continuous delivery , 2015, Fifth International Conference on the Innovative Computing Technology (INTECH 2015).

[24]  Panu Somervuo,et al.  Self-organizing maps of symbol strings , 1998, Neurocomputing.

[25]  Lianping Chen,et al.  The Journal of Systems and Software , 2022 .

[26]  Stephan Krusche,et al.  Introduction of continuous delivery in multi-customer project courses , 2014, ICSE Companion.

[27]  Liming Zhu,et al.  DevOps and Its Practices , 2016, IEEE Softw..

[28]  Lianping Chen,et al.  Continuous Delivery: Huge Benefits, but Challenges Too , 2015, IEEE Software.

[29]  Frank Leymann,et al.  DevOpSlang - Bridging the Gap between Development and Operations , 2014, ESOCC.

[30]  Liming Zhu,et al.  Securing a Deployment Pipeline , 2015, 2015 IEEE/ACM 3rd International Workshop on Release Engineering.

[31]  Mojtaba Shahin Architecting for DevOps and Continuous Deployment , 2015, ASWEC.

[32]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[33]  Jan Bosch,et al.  Industry Application of Continuous Integration Modeling: A Multiple-Case Study , 2016, 2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C).

[34]  Liming Zhu,et al.  Achieving Reliable High-Frequency Releases in Cloud Environments , 2015, IEEE Software.

[35]  Maya Daneva,et al.  Cooperation between information system development and operations: a literature review , 2014, ESEM '14.

[36]  Hans-Peter Fröschle DevOps , 2017, HMD Praxis der Wirtschaftsinformatik.

[37]  Frank Leymann,et al.  Compensation-Based vs. Convergent Deployment Automation for Services Operated in the Cloud , 2014, ICSOC.

[38]  Pasi Kuvaja,et al.  Continuous deployment of software intensive products and services: A systematic mapping study , 2017, J. Syst. Softw..