Short answer

Integrate both continuous software testing and periodic hardware-in-the-loop testing into your CI/CD pipelines for CPS, and foster cross-disciplinary collaboration between hardware and software engineers.

Field
Modelling
Source
ACM Transactions on Software Engineering and Methodology (2022)
Method
Interview-based study with subsequent validation surveys.
Sample
10 organizations, 55 professional developers in validation survey.
Evidence
Moderate effect

Implementing Continuous Integration and Delivery (CI/CD) for Cyber-Physical Systems (CPS) requires a hybrid approach that integrates continuous and periodic builds, balancing Hardware-in-the-Loop (HIL) simulations with physical hardware testing. This modelling research insight is drawn from a 2022 study published in ACM Transactions on Software Engineering and Methodology. Using Interview-based study with subsequent validation surveys. with 10 organizations, 55 professional developers in validation survey., researchers explored how this design variable affects real-world outcomes. The key design takeaway: Integrate both continuous software testing and periodic hardware-in-the-loop testing into your CI/CD pipelines for CPS, and foster cross-disciplinary collaboration between hardware and software engineers.

Study
ModellingHigh ImpactModerate effect

Bridging Hardware and Software: CI/CD Pipelines for Cyber-Physical Systems

Implementing Continuous Integration and Delivery (CI/CD) for Cyber-Physical Systems (CPS) requires a hybrid approach that integrates continuous and periodic builds, balancing Hardware-in-the-Loop (HIL) simulations with physical hardware testing.

ACM Transactions on Software Engineering and Methodology · 2022

01

Key Findings

  • 01Need to combine continuous and periodic builds.
  • 02Balancing Hardware-in-the-Loop (HIL) and simulators is essential.
  • 03Difficulties in software deployment for CPS.
  • 04Accounting for differing behaviors between simulators and HIL.
  • 05Requirement for combined hardware/software expertise in development teams.
02

Application

Design takeaway

Integrate both continuous software testing and periodic hardware-in-the-loop testing into your CI/CD pipelines for CPS, and foster cross-disciplinary collaboration between hardware and software engineers.

How to apply

When designing or refining CI/CD processes for embedded systems or IoT devices, explicitly plan for stages that involve physical hardware interaction and testing, alongside traditional software builds.

Project actions

  • 01Consider how your design project could benefit from automated testing that includes simulated hardware interactions.
  • 02Think about how you would test your prototype with both software updates and physical component checks.
03

Method & Evidence

AimWhat are the challenges, barriers, and mitigation strategies when applying CI/CD practices to the development of Cyber-Physical Systems?
MethodInterview-based study with subsequent validation surveys.
ProcedureSemi-structured interviews were conducted with professionals in 10 organizations across eight domains developing CPS. An open card sorting procedure was used, followed by member-checking surveys within the same organizations. Results were further validated through a survey of 55 professional developers.
Sample10 organizations, 55 professional developers in validation survey.
ContextCyber-Physical Systems (CPS) development in various industrial domains.

Variables

IVApplication of CI/CD practices to CPS development.
DVChallenges, barriers, and mitigation strategies.
CVOrganizational domain, team composition, specific CI/CD tools used.
04

Strengths & Limitations

Strengths

  • +Empirical investigation through interviews and surveys provides real-world insights.
  • +Validation across multiple organizations and developers enhances robustness.

Limitations

The complexity of setting up hardware-in-the-loop testing can be a significant barrier for smaller design projects.

Reliability & validity

Reliability was addressed through member-checking surveys and a broader validation survey. Validity was supported by interviewing professionals across diverse domains.

Think critically

How might the increasing complexity of cyber-physical systems necessitate new forms of modelling and simulation within CI/CD pipelines?

05

Design Principles

"Hybrid testing strategies are essential for the iterative development of cyber-physical systems."

CPS development presents unique challenges due to the tight coupling of software and physical components. Effective CI/CD strategies are crucial for managing this complexity, enabling faster iteration cycles while ensuring the dependability and safety critical to these systems.

06

What This Means for Your Design

To build smart devices (like robots or smart cars) faster and better, you need to test the software continuously, but also test it on real hardware or realistic simulations regularly, and make sure your team knows both software and hardware.

How to use in your project

  • 1.Reference this study when discussing the challenges of testing complex systems that combine hardware and software components in your design project.
07

Add to My Project

08

Quick Cite

Paragraph starter

The development of cyber-physical systems necessitates advanced testing methodologies, such as those explored in CI/CD practices for these domains. Research indicates a need to integrate both continuous software builds and periodic hardware-in-the-loop testing, acknowledging potential discrepancies between simulators and physical hardware, and fostering interdisciplinary teams with expertise in both software and hardware interactions.

09

Source

ACM Transactions on Software Engineering and Methodology

Continuous Integration and Delivery Practices for Cyber-Physical Systems: An Interview-Based Study

journal · 2022

View source

Questions About This Research

What does the research say about bridging hardware and software: ci/cd pipelines for cyber-physical systems?
Integrate both continuous software testing and periodic hardware-in-the-loop testing into your CI/CD pipelines for CPS, and foster cross-disciplinary collaboration between hardware and software engineers. Evidence: ACM Transactions on Software Engineering and Methodology (2022).
Why does "Bridging Hardware and Software: CI/CD Pipelines for Cyber-Physical Systems" matter for design?
CPS development presents unique challenges due to the tight coupling of software and physical components. Effective CI/CD strategies are crucial for managing this complexity, enabling faster iteration cycles while ensuring the dependability and safety critical to these systems.
How can designers apply this research?
Integrate both continuous software testing and periodic hardware-in-the-loop testing into your CI/CD pipelines for CPS, and foster cross-disciplinary collaboration between hardware and software engineers.
What were the main findings?
Need to combine continuous and periodic builds.. Balancing Hardware-in-the-Loop (HIL) and simulators is essential.. Difficulties in software deployment for CPS.. Accounting for differing behaviors between simulators and HIL.
What research method was used?
Interview-based study with subsequent validation surveys. with 10 organizations, 55 professional developers in validation survey..
How strong is the evidence?
Evidence strength is rated Moderate effect, based on a 2022 journal from ACM Transactions on Software Engineering and Methodology.
What should I do differently in my next project?
When designing or refining CI/CD processes for embedded systems or IoT devices, explicitly plan for stages that involve physical hardware interaction and testing, alongside traditional software builds.
What are the limitations?
Findings are based on the specific practices and contexts of the interviewed organizations; generalizability may be limited to similar CPS development environments.