Realization of a Model-Based DevOps Process for Industrial Safety Critical Cyber Physical Systems

Gautham, Smitha; Jayakumar, Athira Varma; Rajagopala, Abhi; Elks, Carl

doi:10.1109/icps49255.2021.9468213

Cited by 7 publications

(4 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As regards the former, O 10 develops prototypes requiring the interconnection of many diferent sub-components. This makes it diicult to determine the expected system behavior: łIt is quite hard to derive integration test cases due to the complex combination of all diferent parts.ž As regards the speciication of safety tests, in agreement to what indicated by Gautham et al [27], O 4 , O 5 , and O 8 pointed out the complexity to identify situations łthat could never happen. ž or łthat you do not expect to happen.…”

Section: O 5 (Automotive)supporting

confidence: 53%

“…Speciically, Törngren et al [74] investigated how CPSs' engineering deals with the complexity of CPS design, and of the environment in which CPSs operate. In this context, it is of paramount importance to perform run-time veriication of safety requirements [27], as well as testing encapsulating model-in-the-loop (MiL) [66], software-in-the-loop (SiL), and hardware-in-the-loop (HiL) [2]. With respect to previous studies, we investigate how CPS complexity impacts the setting of CI/CD pipelines, and how developers deal with such complexity.…”

Section: Development Of Cyber-physical Systemsmentioning

confidence: 99%

“…CPS-related development challenges [74] Environment complexity, co-designing hardware and software [27] Test generation/automation, veriication of safety requirements [2] Integration of MiL, SiL, and HiL [12,40] Where testing is performed (HiL vs. simulators) [25,29,50,62,67,86] Implementation of simulators [4,20,82] Simulator challenges/adequacy [52] Standards, long build, security, architecture, test environments of embedded systems [56] Digital twin adoption in manufacturing and related design challenges…”

Section: Refmentioning

confidence: 99%

See 2 more Smart Citations

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

Zampetti

Tamburri

Panichella

et al. 2023

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

Continuous Integration and Delivery (CI/CD) practices have shown several benefits for software development and operations, e.g., faster release cycles and early discovery of defects. For Cyber-Physical System (CPS) development, CI/CD can help achieving required goals, such as high dependability, yet it may be challenging to apply. This paper empirically investigates challenges, barriers, and their mitigation occurring when applying CI/CD practices to develop CPSs in 10 organizations working in 8 different domains. The study has been conducted through semi-structured interviews, by applying an open card sorting procedure together with a member-checking survey within the same organizations, and by validating the results through a further survey involving 55 professional developers. The study reveals several peculiarities in the application of CI/CD to CPSs. These include the need for (i) combining continuous and periodic builds, while balancing the use of Hardware-in-the-Loop (HiL) and simulators; (ii) coping with difficulties in software deployment (iii) accounting for simulators and HiL differing in their behavior; and (vi) combining hardware/software expertise in the development team. Our findings open the road towards recommenders aimed at supporting the setting and evolution of CI/CD pipelines, as well as university curricula requiring interdisciplinarity, such as knowledge about hardware, software, and their interplay.

show abstract

Section: O 5 (Automotive)supporting

confidence: 53%

Section: Development Of Cyber-physical Systemsmentioning

confidence: 99%

Section: Refmentioning

confidence: 99%

See 1 more Smart Citation

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

Zampetti

Tamburri

Panichella

et al. 2023

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

show abstract

“…C, C++, or HDL) that define the model to deploy it directly in a specific hardware platform [17]. Therefore, the use of this methodology not only implies a reduction of the development time, but also lowers costs and, by avoiding the use of real prototypes, also prevents physical damage, either material or human [18]. Some examples where MBD is used to develop complex systems can be found in [16], [18], and [19].…”

Section: A Model Based Designmentioning

confidence: 99%

A Generic Interface for x-in-the-Loop Simulations Based on Distributed Co-Simulation Protocol

Segura¹,

Poggi

Bárcena

2023

IEEE Access

View full text Add to dashboard Cite

Co-simulation is a key step in the development of today's complex cyber-physical systems (CPS), specially in the integration and validation activities. However, performing a co-simulation involving models developed in different environments and possibly deployed in different platforms with mixed real-time and non real-time constraints is a challenging engineering task. A promising technology that could help overcome communication and synchronisation difficulties is the non-proprietary standard Distributed Co-simulation Protocol (DCP). This standard defines an application-level communication protocol, independent of the platform and the communication medium, that regulates the exchange of information between the co-simulation entities. This paper presents a co-simulation interface based on the DCP standard. It offers a novel approach to apply the DCP standard. Instead of using it as a model encapsulation mechanism, having to develop an specific DCP slave for each application, it is proposed to use it as a generic co-simulation interface. To this end, a Simulink library has been developed, allowing to connect models developed in Simulink with the outside world in an standardised way. Moreover, by exploiting the code generation potential of Simulink, a wide variety of devices become accessible, thus enabling x-in-the-loop simulations, which are commonly used tests in the verification and validation process of CPSs. This library has been tested in a soft real-time co-simulation application between a Simulink instance and an application running on a Xilinx Zynq Ultrascale+ System-on-Chip. As an additional contribution, an analysis of DCP synchronisation problems when simulating closed-loop systems composed of two slaves is performed. Finding that the main causes are the occurrence of random delays and that the simulations of the two slaves start at an arbitrary time. A possible solution to this problem is also presented. INDEX TERMSControl systems, co-simulation interface, distributed co-simulation protocol, model-based design, model testing, simulink, x-in-the-loop.

show abstract

DevOps and Safety? SafeOps! Towards Ensuring Safety in Feature-Driven Development with Frequent Releases

Munk

Schweizer

2022

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Realization of a Model-Based DevOps Process for Industrial Safety Critical Cyber Physical Systems

Cited by 7 publications

References 12 publications

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

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

A Generic Interface for x-in-the-Loop Simulations Based on Distributed Co-Simulation Protocol

DevOps and Safety? SafeOps! Towards Ensuring Safety in Feature-Driven Development with Frequent Releases

Contact Info

Product

Resources

About