From Agile Development to DevOps: Going Towards Faster Releases at High Quality – Experiences from an Industrial Context

Elberzhager, Frank; Arif, Taslim; Naab, Matthias; Süß, Inge; Koban, Sener

doi:10.1007/978-3-319-49421-0_3

Cited by 27 publications

(37 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…they talk about architecture and CD/DevOps, but do not shed light on our RQs). Shahin et al, 2016;Elberzhager et al, 2017;Villamizar et al, 2015;Schermann et al, 2018;Stahl andBosch, 2018 RQ2. Characteristics Stutevant, 2017;Chen, 2015b;Shahin et al, 2016;Pahl et al, 2018;Berger et al, 2017;Chen et al, 2015RQ3.…”

Section: Resultsmentioning

confidence: 99%

“…Characteristics Stutevant, 2017;Chen, 2015b;Shahin et al, 2016;Pahl et al, 2018;Berger et al, 2017;Chen et al, 2015RQ3. Styles Shahin et al, 2016Elberzhager et al, 2017;Villamizar et al, 2015;Schermann et al, 2018;Pahl et al, 2018;Berger et al, 2017;Chen et al2015;Bass, 2017 As indicated in Table 1, there are papers that discuss potential software architectural issues of implementing CD/DevOps on existing systems in a meaningful way. Furthermore, 6 papers mention important software architectural characteristics, and 8 papers discuss some form of software architecture style, all in the context of CD/DevOps.…”

Section: Resultsmentioning

confidence: 99%

“…After the second selection round, there were 13 papers left, these finally represent the body of literature to be used in the final stage of Kitchenham's SLR method (2007): data extraction and monitoring, and data synthesis. The papers are: Stutevant, 2017; Chen, 2015b;Erder and Pureur, 2015;Woods, 2016;Shahin et al, 2016;Elberzhager et al, 2017;Villamizar et al, 2015;Schermann et al, 2018;Stahl and Bosch, 2018;Pahl et al, 2018;Berger et al, 2017;Chen et al, 2015;Bass, 2017.…”

Section: Review Protocolmentioning

confidence: 99%

See 2 more Smart Citations

Designing Software Architecture to Support Continuous Delivery and DevOps: A Systematic Literature Review

Bolscher

Daneva

2019

Proceedings of the 14th International Conference on Software Technologies

View full text Add to dashboard Cite

This paper presents a systematic literature review of software architecture approaches that support the implementation of Continuous Delivery (CD) and DevOps. Its goal is to provide an understanding of the stateof-the-art on the topic, which is informative for both researchers and practitioners. We found 17 characteristics of a software architecture that are beneficial for CD and DevOps adoption and identified ten potential software architecture obstacles in adopting CD and DevOps in the case of an existing software system. Moreover, our review indicated that micro-services are a dominant architectural style in this context. Our literature review has some implications: for researchers, it provides a map of the recent research efforts on software architecture in the CD and DevOps domain. For practitioners, it describes a set of software architecture principles that possibly can guide the process of creating or adapting software systems to fit in the CD and DevOps context.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Resultsmentioning

confidence: 99%

Section: Review Protocolmentioning

confidence: 99%

See 1 more Smart Citation

Designing Software Architecture to Support Continuous Delivery and DevOps: A Systematic Literature Review

Bolscher

Daneva

2019

Proceedings of the 14th International Conference on Software Technologies

View full text Add to dashboard Cite

show abstract

“…Example of social problems is ambiguity in the definition of DevOps which is called as one of the main failure reasons in DevOps adoption [40]. Elberzhager and Arif with the group of authors also emphasize the importance of common understanding of DevOps within the company [18]. Based on their studies they recommend starting with the small changes in a manageable context of a small project and define requirements for tools and processes to be utilized in the DevOps environment.…”

Section: Adoption Of Devopsmentioning

confidence: 99%

“…Deployment script triggers the pipelines of the "api-service", "files-processing-service" or "static-website" projects. The reason to create additional repository with the script to trigger pipelines of these projects is to store release and production AWS access keys in secure place and pass them through GitLab API 18 . All deployments are done with a help of Serverless Framework using 'sls deploy' command.…”

Section: And CD Pipelinementioning

confidence: 99%

Implementation of a DevOps Pipeline for Serverless Applications

Іванов¹,

Smolander

2018

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Serverless computing is a cloud computing execution model where server-side logic runs in the stateless compute containers that are event-triggered and usually fully managed by vendor hosts such as AWS Lambda. This approach is also called Function as a Service (FaaS). Applications that rely on this approach are called Serverless applications. Serverless usage promises infrastructure cost reduction and automatic scalability. One more important benefit of serverless is making the operations part of DevOps process simpler. It reduces the time on the management and maintenance of the servers and sometimes makes them even completely unnecessary. Despite this fact, applications using serverless computing model require a new look at DevOps automation practices since it is a new approach to software architecture design and software development workflow.

show abstract

Readiness model for DevOps implementation in software organizations

Rafi

Akbar

et al. 2020

J Software Evolu Process

View full text Add to dashboard Cite

DevOps is a new software engineering paradigm adopted by various software organizations to develop the quality software within time and budget. The implementation of DevOps practices is critical, and there are no guidelines to assess and improve the DevOps activities in software organizations. Hence, there is a need to develop a readiness model for DevOps (RMDevOps) with an aim to assist the practitioners for implementation of DevOps practices in software firms. To achieve the study objective, we conducted a systematic literature review (SLR) study to identify the critical challenges and associated best practices of DevOps. A total of 18 challenges and 73 best practices were identified from the 69 primary studies. The identified challenges and best practices were further evaluated by conducting a survey with industry practitioners. The RMDevOps was developed based on other well‐established models in software engineering domain, for example, software process improvement readiness model (SPIRM) and software outsourcing vendor readiness model (SOVRM). Finally, case studies were conducted with three different organizations with an aim to validate the developed model. The results show that the RMDevOps is effective to assess and improve the DevOps practices in software organizations.

show abstract

From Agile Development to DevOps: Going Towards Faster Releases at High Quality – Experiences from an Industrial Context

Cited by 27 publications

References 4 publications

Designing Software Architecture to Support Continuous Delivery and DevOps: A Systematic Literature Review

Designing Software Architecture to Support Continuous Delivery and DevOps: A Systematic Literature Review

Implementation of a DevOps Pipeline for Serverless Applications

Readiness model for DevOps implementation in software organizations

Contact Info

Product

Resources

About