# Defining a Domain-Specific Language for Behavior Verification of Cyber–Physical Applications

## TL;DR

This paper introduces a domain-specific language to simplify behavior verification for complex IoT and cyber-physical systems, enabling non-experts to build and verify applications more efficiently.

## Contribution

A new domain-specific language and methodology for automating behavior verification in IoT and CPS development is proposed.

## Key findings

- The proposed DSL and methodology improve productivity and reduce errors in IoT and CPS application development.
- Scenario-based analysis and 43 use cases demonstrate the effectiveness of the approach in real-world applications.
- The methodology allows domain experts to focus on verification rather than technical implementation.

## Abstract

A common problem in the development of Internet-of-Things (IoT) and cyber–physical system (CPS) applications is the complexity of these domains, due to their hybrid and distributed nature at multiple layers (hardware, network, communication, frameworks, etc.). This complexity often leads to implementation errors, some of which result in undesired states of the application and/or the system. The current work focuses on low-code development of behavior verification processes for IoT and CPS applications, in order to raise productivity, minimize risks (due to errors) and enable access to a wider range of end-users to create and verify applications for state-of-the-art domains, such as smart home and smart industry. Model-Driven Development (MDD) approaches are employed for the implementation of a Domain-Specific Language (DSL) that enables the evaluation of IoT and CPS applications, among others. The proposed methodology automates the development of behavior verification processes, allowing domain experts to focus on the real problem, instead of struggling with technical and technological breaches. Through comparative scenario-based analysis and 43 detailed use cases, we illustrate how the proposed methodology automates the development of behavior verification processes, allowing end-users to focus on the verification definition, instead of technical and technological intricacies.