Towards DevOps in the Embedded Systems Domain: Why is It So Hard?

Lwakatare, Lucy Ellen; Karvonen, Teemu; Sauvola, Tanja; Kuvaja, Pasi; Olsson, Helena Holmström; Bosch, Jan; Oivo, Markku

doi:10.1109/hicss.2016.671

Cited by 77 publications

(49 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Embedded systems and IoT devices: deployment on embedded systems can be hard, especially when only the customer owns and controls the hardware platform [31]. Therefore, engineers must customize the updating mechanisms for embedded systems and IoT devices.…”

Section: Implications For Engineersmentioning

confidence: 99%

A Survey of DevOps Concepts and Challenges

Leite¹,

Rocha

Kon³

et al. 2019

ACM Comput. Surv.

299

183

View full text Add to dashboard Cite

DevOps is a collaborative and multidisciplinary organizational effort to automate continuous delivery of new software updates while guaranteeing their correctness and reliability. The present survey investigates and discusses DevOps challenges from the perspective of engineers, managers, and researchers. We review the literature and develop a DevOps conceptual map, correlating the DevOps automation tools with these concepts. We then discuss their practical implications for engineers, managers, and researchers. Finally, we critically explore some of the most relevant DevOps challenges reported by the literature.

show abstract

Section: Implications For Engineersmentioning

confidence: 99%

A Survey of DevOps Concepts and Challenges

Leite¹,

Rocha

Kon³

et al. 2019

ACM Comput. Surv.

299

183

View full text Add to dashboard Cite

show abstract

“…practices rely on the foundations of agile and lean software development, including continuous integration practices [2]. In other words, both DevOps/CD and Scrum have an emphasis on continuous integration, testing, and delivery of working software.…”

Section: Scrum Support For Devops/cd: Devops/cdmentioning

confidence: 99%

“…DevOps is the integration of development and operations, with a key goal of shortening the feedback loop and the development cycle through collaboration, automation and frequent software releases [1,2]. A related term, Continuous Delivery (CD), is a set of practices and principles to enable the release software faster and more frequently [1].…”

Section: Introductionmentioning

confidence: 99%

SKI: A New Agile Framework that Supports DevOps, Continuous Delivery, and Lean Hypothesis Testing

Saltz¹,

Sutherland²

2020

Proceedings of the Annual Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

This paper explores the need for a new process framework that can effectively support DevOps and Continuous Delivery teams. It then defines a new framework, which adheres to the lean Kanban philosophy but augments Kanban by providing a structured iteration process. This new Structured Kanban Iteration (SKI) framework defines capabilitybased iterations (as opposed to Kanban-like no iterations or Scrum-like time-based sprints) as well as roles, meetings and artifacts. This structure enables a team to adopt a well-defined process that can be consistently used across groups and organizations. While many of SKI's concepts are similar to those in found in Scrum, SKI's capability-based iterations can support the demands of product development as well as operational support efforts, and hence, is well suited for DevOps and Continuous Delivery. SKI also supports lean hypothesis testing as well as more traditional software development teams where capability-based iterations are deemed more appropriate than timebased sprints.

show abstract

“…2) Multiple environment incompatibilities leading to specialized teams 12,13 3) Capability to self-organize 14 4) Loss of global vision of the project and knowledge of application due to automation 7 5) Confinement of knowledge sharing to hierarchical organisational structure and process 'red tape' 7 6) Limited sharing when parts of development or operations are outsourced 15 Moving from DevOps to large-scale DevOps amplifies the challenges linked to DevOps, i.e. coordination and collaboration improvement, dependency management, knowledge development and sharing.…”

Section: Introductionmentioning

confidence: 99%

Innovative Practices for Knowledge Sharing in Large-Scale DevOps

et al. 2020

View full text Add to dashboard Cite

Agile development methods and DevOps require adaptation during implementation to meet the needs of a constantly changing software development environment. The emergence of knowledge-sharing practices for large-scale DevOps has not been the subject of much research. Our in-depth case study, comprising 106 interviews at a large multinational company operating in a DevOps at scale environment, identified a number of innovative practices which had emerged, principally to resolve knowledge-sharing challenges. These practices seem to be more likely to emerge in large-scale DevOps environments. While similar results might have been achieved due to the large-scale nature of the projects, it is difficult to determine definitively whether the main causal factor is project size or DevOps. We believe that self-organization and continuous improvement over a long period of time are also critical influencing factors.

show abstract

Towards DevOps in the Embedded Systems Domain: Why is It So Hard?

Cited by 77 publications

References 16 publications

A Survey of DevOps Concepts and Challenges

A Survey of DevOps Concepts and Challenges

SKI: A New Agile Framework that Supports DevOps, Continuous Delivery, and Lean Hypothesis Testing

Innovative Practices for Knowledge Sharing in Large-Scale DevOps

Contact Info

Product

Resources

About