Applying DevOps to Embedded Software Development: Challenges, Design, and Case Study

Overview Embedded systems are widely used due to high integration, stability, and low cost, but their software development must consider hardware compatibility. The article explores how DevOps, a culture and process that has succeeded in software development, can be applied to embedded product development, addressing challenges and offering solutions.

Keywords : DevOps, Embedded Systems, Embedded Software Development, Continuous Integration, Continuous Delivery

1. Introduction With the rapid growth of information technology, embedded systems have become indispensable in modern life. Traditional development methods can no longer meet the fast‑to‑market demands of increasingly complex embedded products. DevOps, which integrates development and operations, has been widely adopted in software development, but its best practices are mostly focused on internet and application software, limiting its use in embedded software.

2. DevOps Overview DevOps combines Development and Operations to remove barriers between teams and automate software development, deployment, and maintenance. Core practices include automation, continuous integration (CI), continuous delivery (CD), and monitoring/feedback.

3. Challenges in Embedded Software Development Embedded software faces hardware dependency, strict real‑time requirements, and limited resources, making traditional DevOps tools difficult to apply. Specific challenges include version management for tightly coupled hardware‑software, low test efficiency due to manual hardware‑software integration, and intellectual property protection for hardware‑specific code.

4. Embedded Software Development Model Design

4.1 Anti‑Fragile Organizational Construction A layered architecture (application, business logic, functional modules, driver, OS) promotes high cohesion and low coupling, facilitating requirement decomposition, clear team boundaries, and granular CI/CD pipelines. A Scrum‑of‑Scrums (SoS) approach organizes teams per layer with defined PO, SM, and regular coordination meetings.

4.2 CI/CD Design for Hardware‑Software Testing Introduce artifact management to protect IP, use virtual debugging tools to keep source code within secure domains, and adopt a Git‑based branching workflow (feature/bugfix → develop → main). Hot‑fix branches handle urgent issues before merging back.

5. DevOps Practice in a Domestic Intelligent CNC System The case study describes a CNC product comprising an industrial PC and HMI panel running an RTOS. After applying the proposed DevOps model for one month, value‑stream efficiency improved by ~30% and failure rate decreased by ~56%, with a goal of daily releases within a year.

6. Conclusion The article concludes that DevOps can be feasibly and effectively applied to embedded product development, offering higher efficiency, flexibility, and quality. Successful adoption requires coordinated effort between development and operations teams, gradual process improvement, and continuous tool enhancement.

References [1] 金泽锋, 张佑文, 叶文华, 等. 面向完整价值交付的文档 DevOps 应用研究[J]. 软件学报, 2019, 30(10):3127‑3147. [2] 童向杰, 郑武, 谢凤玲, 等. 企业数字化转型中的硬件 DevOps 实践[J/OL]. 价值工程, 2020, 39(1):1‑5. [3] 荣国平, 张贺, 邵栋, 等. 软件过程与管理方法综述[J]. 软件学报, 2019, 30(01):62‑79. [4] 黄铮, 周洁, 朱学海. 一种基于 Azure DevOps 的面向嵌入式软件的持续集成及自动测试环境[J]. 工业控制计算机, 2022, 35(09):17‑19+23.