## 2 Related Work
### General Model-Driven IoT Studies
IoTMoF supports platform-independent modeling with the ReqMIoT environment, covering use-case modeling and creating IoTARM-compliant domain models. The use-case model addresses exceptional behaviors alongside processing functionality. Cloud and fog computing concepts are commonly utilized in IoT systems, playing a crucial role in determining the computational placement within IoT architectures. Moreover, these systems facilitate abstraction levels and diminish hardware dependencies. Model-driven approaches have been proposed for both cloud systems [61; 62; 63] and fog systems [64] to address these requirements. Furthermore, various model-driven IoT studies are conducted across different domains. These include rapid prototyping [65], smart home applications [66], civil healthcare [67], real-time operating systems (RTOS) [68], smartphone alarms [69], smart city solutions [70; 71], door access control systems [72], and automotive systems [73]. Additionally, developments in complex event processing (CEP) programs [74], machine learning [75], personal data privacy [76], flexible communication using MQTT [77], fleet management with numerous devices [78], edge device computation systems [79], reactive approaches [80], and distributed smart applications [81] are also available in the literature. Studies utilizing high-level modeling tools such as Papyrus [82], and SysML and Capella [83] for the model-driven IoT systems also exist. Table 1 lists all above-mentioned general studies for model-driven development of IoT applications. As can be seen, although they provide various noteworthy approaches for modeling IoT, they do not address the problems inherent in modeling IoT-based public transportation systems and primarily offer MDE methods and/or tools only applicable to the domains other than public transportation. In addition, many of them do not provide an evaluation of their languages/tools/approaches, and the use of the supported features is mostly exemplified just with case studies. \begin{table}
\begin{tabular}{c c c c c} \hline \hline
**Study** & **Target Domain** & **IDE/Tool Provided** & **Use Case Included** & **Evaluation** \\ \hline ThingML [24; 27] & General IoT Systems & Yes & Yes & No \\ CAPSml [28] & General IoT Systems & No & No & No \\ Vorto [10] & Digital Twins & Yes & Yes & No \\ MDE4 IoT [30] & General IoT Systems & Yes & Yes & No \\ MC-IoT [20] & Mission Critical IoT Systems & No & No & No \\ UMLItoT & Industrial IoT & Yes & Yes & Yes \\  & Production Systems & Yes & Yes & No \\ [PERSON] et al. [32] & Manufacturing & No & Yes & No \\ [PERSON] et al. [35] & Car Manufacturing & Yes & Yes & No \\ [PERSON] et al. [36] & Industrial IoT Systems & Yes & Yes & No \\ [PERSON] et al. [38] & Smart Gas Distribution & No & Yes & Yes \\ COMFIT [39] & General IoT Systems & Yes & Yes & Yes \\ CypridT [41] & IoT Networks & Yes & Yes & No \\ [PERSON] [42] & SOA for IoT & No & No & No \\ SoaML4 IoT [11; 12] & SOA for IoT & Yes & Yes & No \\ [PERSON] and [PERSON] [14] & General IoT Systems & Yes & Yes & Yes \\ [PERSON] et al. [44] & General IoT Systems & Yes & Yes & No \\ DSMLATinyOS [45] & Wireless Sensor Networks & Yes & Yes & Yes \\ [PERSON] and [PERSON] [46] & Wireless Sensor Networks & No & No & No \\ [PERSON] [47] & Wireless Sensor Networks & No & No & No \\ [PERSON] et al. [48] & Wireless Sensor Networks & Yes & Yes & No \\ [PERSON] et al. [49] & Firmware Development & Yes & Yes & No \\ GeneSIS [50; 52] & IoT System Management & Yes & No & No \\ [PERSON] et al. [54] & IoT System Management & No & Yes & No \\ [PERSON] et al. [51] & IoT System Management & Yes & Yes & No \\ CHESSIoT [55] & Multi-layered IoT Systems & Yes & Yes & Yes \\ \hline \hline \end{tabular}
\end{table} 
Table 1: General model-driven IoT studies.