logseq/pages/SOSYM-25-00005106.md

type:: [[REVIEWS]]
tags:: 
year:: 2025
venue:: [[SOSYM]] 
full-title::DEVS as a Language for Design of Adaptive IoT Systems
date-start:: [[03-04-2025]] - 15:17
date-submitted::
external-links::
status:: [[DONE]] 
deadline-submission:: 
file:: [[@SOSYM-25-00005106_Proof_hi]] 
parent::
todoist:: https://app.todoist.com/app/task/manuscript-id-sosym-25-00005106-now-in-your-reviewer-center-software-and-systems-6XP5HgcvWrQm5888

	- ### [[Highlights]]
		- # Annotazioni  
		  
		  (3/4/2025, 15:16:58)
		- “IoT Design lang” ([“SOSYM-25-00005106_Proof_hi”, p. 1](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=2&annotation=X92P8FA9)) #5fb236
		- “DEVS as a Language for Design of Adaptive IoT Systems” ([“SOSYM-25-00005106_Proof_hi”, p. 1](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=2&annotation=QBUFGQBR)) #5fb236
		- “Complex adaptive concepts implemented in IoT-enabled systems are still emerging” ([“SOSYM-25-00005106_Proof_hi”, p. 1](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=2&annotation=PA8S68XP)) #5fb236
		- “applicability” ([“SOSYM-25-00005106_Proof_hi”, p. 2](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=3&annotation=DFEV84D5)) #5fb236
		- “Complex Adaptive System (CAS) concepts have existed for some time” ([“SOSYM-25-00005106_Proof_hi”, p. 2](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=3&annotation=A49IM9X3)) #5fb236
		- “dynamically adapt the behaviors of components in a dynamic execution environment.” ([“SOSYM-25-00005106_Proof_hi”, p. 2](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=3&annotation=UQ3YCLQR)) #a28ae5
		- “model expressiveness and model continuity for all stages of the process including design, simulation, and implementation” ([“SOSYM-25-00005106_Proof_hi”, p. 2](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=3&annotation=SPP46QCT)) #a28ae5
		- “transition the ”same” description from stage to stage in the development process, where by ”same”, we mean that little or no modification is needed in such transitions.” ([“SOSYM-25-00005106_Proof_hi”, p. 2](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=3&annotation=ZFPZWBKG)) #a28ae5
		- “IoT Design language” ([“SOSYM-25-00005106_Proof_hi”, p. 2](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=3&annotation=H36R5IWD)) #5fb236
		- “We will illustrate with several examples” ([“SOSYM-25-00005106_Proof_hi”, p. 2](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=3&annotation=JBQ52M34)) #5fb236
		- “(SES)” ([“SOSYM-25-00005106_Proof_hi”, p. 2](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=3&annotation=N6ECRZGS)) #ffd400  
		  
		  *what is it? is it part of the contribution of this paper?*
		- “Fig. 1” ([“SOSYM-25-00005106_Proof_hi”, p. 2](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=3&annotation=R2X6ZSQC)) #ffd400  
		  
		  *The resolution of the figure needs to be improved.*
		- “DEVS model expressiveness is manifested in its support of hierarchical and modular model construction” ([“SOSYM-25-00005106_Proof_hi”, p. 3](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=4&annotation=SMJD2363)) #ffd400  
		  
		  *Why are you focusing on these characteristincs when referring to "model expressiveness"?*
		- “DEVS supports model continuity in which only the simulator needs to be changed to run from abstract time to real-time [11, 12] while the model remains substantially the same” ([“SOSYM-25-00005106_Proof_hi”, p. 3](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=4&annotation=576V8GCG)) #5fb236
		- “Closure under coupling of DEVS models” ([“SOSYM-25-00005106_Proof_hi”, p. 4](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=5&annotation=JV3XTXFH)) #ffd400  
		  
		  *Concepts are suddenly mentioned without proper introduction or being motivated.*
		- “Aspect” ([“SOSYM-25-00005106_Proof_hi”, p. 4](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=5&annotation=PICP7MRZ)) #2ea8e5
		- “This results in several Pruned Entity Structures (PES), which can then be automatically converted to simulatable DEVS models, thus enabling comparison of alternative architectures” ([“SOSYM-25-00005106_Proof_hi”, p. 5](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=6&annotation=98KDI2HF)) #ffd400  
		  
		  *What are the "Pruned Entity Structures"? Again, concepts/terms are used without proper introduction.*
		- “Fig. 3” ([“SOSYM-25-00005106_Proof_hi”, p. 5](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=6&annotation=6WC7XHG6)) #ffd400  
		  
		  *It is necessary to describe the metaclasses/kinds of modeling constructs, which are used to define the shown model.*
		- “DEVS Universality” ([“SOSYM-25-00005106_Proof_hi”, p. 5](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=6&annotation=D9P9CGT2)) #2ea8e5
		- “ECA (Event-Condition-Action)” ([“SOSYM-25-00005106_Proof_hi”, p. 5](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=6&annotation=BS2U68P7)) #5fb236
		- “Heterogeneity” ([“SOSYM-25-00005106_Proof_hi”, p. 6](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=7&annotation=S7YNQ62X)) #2ea8e5
		- “The DEVS Universality simplify the specification of this specific description. Due to the DEVS universality these description formalisms can be reduced to DEVS.” ([“SOSYM-25-00005106_Proof_hi”, p. 6](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=7&annotation=EGL4LP2G)) #ffd400  
		  
		  *Sentences like these need to be supported with a clear evidence!*
		- “identified traits” ([“SOSYM-25-00005106_Proof_hi”, p. 6](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=7&annotation=BVZF2H65)) #ffd400  
		  
		  *Where are identified?*
		- “Real-Time” ([“SOSYM-25-00005106_Proof_hi”, p. 6](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=7&annotation=T4HXR26U)) #2ea8e5
		- “Concurrency a” ([“SOSYM-25-00005106_Proof_hi”, p. 6](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=7&annotation=5ANFZFFM)) #2ea8e5
		- “Adaptability” ([“SOSYM-25-00005106_Proof_hi”, p. 6](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=7&annotation=7AY7QGAG)) #2ea8e5
		- “Scalability” ([“SOSYM-25-00005106_Proof_hi”, p. 6](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=7&annotation=XFQQEFAJ)) #2ea8e5
		- “Model-to-Execution Continuity” ([“SOSYM-25-00005106_Proof_hi”, p. 6](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=7&annotation=4DHXIYC9)) #ffd400  
		  
		  *This has nothing to do with the characteristics of IoT systems as those previously listed. This is more related to the tools/environments  supporting the development analysis and deployment of IoT systems!*
		- “they lack the comprehensive support for concurrency, event-driven behavior, and model continuity that DEVS offers. Thus, DEVS provides a robust and minimal set of traits that make it an ideal candidate for IoT system design and simulation” ([“SOSYM-25-00005106_Proof_hi”, p. 7](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=8&annotation=N9CXLIFK)) #ffd400  
		  
		  *It is necessary to expand the discussion of such limitations and highlight their evidence.*
		- “Additionally, IoT systems must be adaptive to changing conditions, such as device failures or network disruptions, and DEVS supports dynamic model structures that allow for this flexibility.” ([“SOSYM-25-00005106_Proof_hi”, p. 7](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=8&annotation=FDZMB4KR)) #5fb236
		- “DEVS” ([“SOSYM-25-00005106_Proof_hi”, p. 7](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=8&annotation=MLB4SWXG)) #ffd400  
		  
		  *Mentioned so many tims but never presented properly.*
		- “his continuity is crucial for ensuring that IoT systems perform as intended when deploye” ([“SOSYM-25-00005106_Proof_hi”, p. 7](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=8&annotation=AUCBRAFW)) #5fb236
		- “Practical Examples” ([“SOSYM-25-00005106_Proof_hi”, p. 7](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=8&annotation=ALQHBWSR)) #ffd400  
		  
		  *Is showing such examples the goal of the paper? What's the goal? What are the criteria used to select such examples? There are many tools and approaches supporting the speficiation, development and analysis of IoT systems. How are they related to the works overviewed in this paper?*
		- “This is achieved via DEVS model continuity first using a DEVS simulator to verify the correctness of the models prior to their deployment and then transforming the models and the associated DEVS simulator to real-time implementation.” ([“SOSYM-25-00005106_Proof_hi”, p. 7](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=8&annotation=HXWJ9WI9)) #5fb236
		- “We note that all of these models had identical C++ code for both deployment on the device and simulation, except that the message broker model was replaced with an actual commercial off-the-shelf implementation and the client models were slightly modified to make them suitable for deployment on the hardware” ([“SOSYM-25-00005106_Proof_hi”, p. 8](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=9&annotation=RWFWZSID)) #ffd400  
		  
		  *This is possible also without using DEVS. If the system is properly designed, replacing a simulated MQTT client with a real MQTT compatible sensor or actual does not require changing the code of the system.*
		- “The key advantage of using DEVS lies in its flexibility to define multiple strategies through distinct DEVS model specifications.” ([“SOSYM-25-00005106_Proof_hi”, p. 8](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=9&annotation=NPN5CPBF)) #ffd400  
		  
		  *Reviewers that are not aware of such formalism is supposed to read this kind of sentences without any supporting evidence.*
		- “typically involves” ([“SOSYM-25-00005106_Proof_hi”, p. 8](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=9&annotation=8XASWYGM)) #ffd400  
		  
		  *This is not always the case. As previously said, coupling specification can be just refining the configuration of the the IoT system at hand.*
		- “The system can manage multiple sensor farms and simultaneously improve predictive models in real-time by adapting and re-training models to keep forecasts accurate and updated.” ([“SOSYM-25-00005106_Proof_hi”, p. 9](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=10&annotation=M87Y5IBY)) #a28ae5
		- “Model expressiveness:” ([“SOSYM-25-00005106_Proof_hi”, p. 9](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=10&annotation=ZNBGUITV)) #ffd400  
		  
		  *Again, there are many approaches that provide such modeling constructs. What's the novelty?*
		- “IoT conflict” ([“SOSYM-25-00005106_Proof_hi”, p. 10](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=11&annotation=UBF7D2RW)) #ffd400  
		  
		  *What do you mean? It is necessary to properly give a definition for "IoT conflict"*
		- “Challenges intensify as smart applications increasingly control shared IoT devices, particularly actuators that translate commands into physical effects.” ([“SOSYM-25-00005106_Proof_hi”, p. 10](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=11&annotation=2NUCW3SX)) #ffd400
		- “M&S approach” ([“SOSYM-25-00005106_Proof_hi”, p. 10](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=11&annotation=GWFINQTW)) #ffd400
		- “Logical ACM Design” ([“SOSYM-25-00005106_Proof_hi”, p. 11](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=12&annotation=8EV2EE55)) #2ea8e5
		- “Model Validation” ([“SOSYM-25-00005106_Proof_hi”, p. 11](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=12&annotation=5Q4GCX4D)) #2ea8e5
		- “Model Deployment:” ([“SOSYM-25-00005106_Proof_hi”, p. 11](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=12&annotation=RAA6C4RX)) #2ea8e5
		- “The proposed approach” ([“SOSYM-25-00005106_Proof_hi”, p. 11](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=12&annotation=D5VSL8GZ)) #ffd400  
		  
		  *Where? In this paper?*
		- “The proposed simulation-based approach” ([“SOSYM-25-00005106_Proof_hi”, p. 12](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=13&annotation=68YWCEMM)) #ffd400  
		  
		  *This is another instance of the same problem occurring many times in the paper. It is not clearly defined the main contribution of this paper vs what is an overview of concepts presented alsewhere. In the end, it is not clear the technical contribution of this paper.*
		- “Fig. 12” ([“SOSYM-25-00005106_Proof_hi”, p. 17](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=18&annotation=JFHZ7ZZV)) #ffd400  
		  
		  *The quality of this figure is very bad. The resolution is bad and it is not even readable some text.*
		- “for its validity as an IoT design language based on its model expressiveness and continuity.” ([“SOSYM-25-00005106_Proof_hi”, p. 20](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=21&annotation=MPSCVRWH)) #5fb236
		- “Let’s explore how some of these popular formalisms compare to DEVS in terms of expressiveness” ([“SOSYM-25-00005106_Proof_hi”, p. 23](zotero://select/library/items/FPETYHVL)) ([pdf](zotero://open-pdf/library/items/6WGP7UD7?page=24&annotation=9IEDFGXQ)) #ffd400  
		  
		  *To support such claim it is necessary to perform a fair comparison by showing on a same system specification fragments or aspects that cannot be modeled or supported with existing technologies and that instead are possible with DEVS.*
	- ### [[Comments]]
		- SUMMARY: The paper discusses the applicability of DEVS (Discrete Event System Specification) as a modeling language for designing and simulating adaptive IoT systems. To this end, different examples are presented to illustrate how DEVS addresses IoT challenges.
		- COMMENTS: The paper is about an important problem. IoT systems are pervasive nowadays; consequently, there is an increasing need for techniques and tools supporting their development and management. However, I have different concerns about the paper, which are mainly related to the limited discussion of the paper's core contribution in comparison to existing approaches specifically devised for IoT systems.
		- Statements regarding DEVS advantages and comparisons with existing approaches require evidence and justification. In particular,
		- Claims about DEVS universality simplifying specifications (p. 6) and offering superior traits (p. 7) need clear, evidence-based support.
		- The advantage of using DEVS for model continuity (p. 7) is presented without acknowledging that similar outcomes can be achieved using other properly designed systems. For instance, if systems are properly designed, replacing a simulated MQTT client with a real MQTT-compatible sensor or actuator does not require changing the system code.
		- Comparisons made in terms of model expressiveness (p. 23) require a fair and structured comparison, explicitly showing modeling scenarios where DEVS provides unique advantages over existing formalisms.
		- Several concepts and terminologies are suddenly introduced, for instance:
			- "Closure under coupling of DEVS models" on p. 4 lacks introductory context and motivation;
			- "Pruned Entity Structures (PES)" on p. 5 are referenced without explanation;
			- The term "IoT conflict" on p. 10 is used without definition or context.
			- The concept "SES" is mentioned without a proper introduction.
		- Figures need substantial improvement, in particular:
			- Fig. 1 and Fig. 12 suffer from poor resolution. Fig. 12, in particular, is unreadable.
			- Fig. 3 requires a description of the metaclasses or types of modeling constructs used, ensuring readers understand the shown model clearly.
		- Clarifications needed on the paper's objective and contributions. The goal of including practical examples (p. 7) is not explicitly stated. Clarify the selection criteria for these examples and how they directly support the claimed contributions.