89 lines
8.3 KiB
Markdown
89 lines
8.3 KiB
Markdown
tags:: [[#zotero]]
|
||
title:: @AI-Assisted Modeling: DSL-Driven AI Interactions
|
||
item-type:: [[journalArticle]]
|
||
original-title:: AI-Assisted Modeling: DSL-Driven AI Interactions
|
||
language:: en
|
||
library-catalog:: Zotero
|
||
links:: [Local library](zotero://select/library/items/LNN2PAY5), [Web library](https://www.zotero.org/users/1039502/items/LNN2PAY5)
|
||
|
||
- [[Abstract]]
|
||
- AI-assisted programming greatly increases software development performance. We enhance this potential by integrating transparency through domain-specific modeling techniques and providing instantaneous, graphical visualizations that accurately represent the semantics of AI-generated code. This approach facilitates visual inspection and formal verification, such as model checking.
|
||
- ### Attachments
|
||
- [PDF](https://icse2026-larc.hotcrp.com/doc/icse2026-larc-paper70.pdf) {{zotero-imported-file IJWV5JTZ, "AI-Assisted Modeling DSL-Driven AI Interactions.pdf"}}
|
||
- ### Notes
|
||
- I’m doing a review for a workshop paper and these are the notes that I took while reading the paper.
|
||
|
||
# Annotazioni
|
||
(7/12/2025, 15:56:09)
|
||
|
||
“We enhance this potential by integrating transparency through domain-specific modeling techniques and providing instantaneous, graphical visualizations that accurately represent the semantics of AI-generated code.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“visual inspection and formal verification, such as model checking.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“Visual Studio Code extension for the Lingua Franca language” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“This is achieved by adapting the code generator of the modeling language to produce structured prompt templates that allow LLMs to generate implementation code for dedicated purposes that is automatically integrated in the overall system.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“we enhance AI-assisted programming with domainspecific modeling techniques and providing instantaneous, graphical visualizations that accurately represent the semantics of AIgenerated code as a basis for visual inspection and formal verification, such as model checking.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“AI-assisted programming” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“Conceptually” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“Pragmatically” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“Background” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“it remains difficult to control and steer effectively.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“s. Moreover, classical modeling workflows frequently depend on graphical representations, which are not easily generated by current AI systems” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“We combine” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“(i) state-of-the-art DSL modeling techniques with instantaneous automatic visualizations,” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“(ii) AIassisted programming to enable iterative and interactive support for DSL development.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
|
||
|
||
“generating graphical models via AI is more technically demanding” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
|
||
|
||
“we propose increasing the number of observation and interaction points throughout the modeling process” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
|
||
|
||
“They allow modelers to inspect intermediate results, guide refinements, and provide feedbacksupporting more flexible, iterative workflows that move beyond rigid one-shot prompting” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
|
||
|
||
“we decompose the program/model refinement process into distinct stages, allowing for incremental progress and improved controllability during model development” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2) The authors should clarify if the approach is for supporting modeling activities first or code development. In some sentences it seems that the approach is for assisting modeling activities, in some other parts of the paper it seems that the goal of the proposed approach is for supporting the development activities and in parallel a graphical visualization of the code being generated is given. Both directions are indeed important, but it is necessary to be clear on what's the goal of the paper.
|
||
|
||
“Contribution” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
|
||
|
||
“visual verification tailored to DSL development” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2) What kind of verification do you support?
|
||
|
||
“reliability and controllability” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
|
||
|
||
“Finally, we outline how parts of this extension may themselves be generated via AI in the future, further streamlining the development process.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
|
||
|
||
“approach to AI-assisted modeling,” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
|
||
|
||
“Building on these developments, this work investigates how similar forms of assistance can be applied to domainspecific modeling, with the goal of enabling a more natural and interactive modeling experience” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
|
||
|
||
“Instead of treating model generation as a one-shot task, our approach introduces a dialog-driven workflow that facilitates clarification, program/model refinement, and visual feedback throughout the process.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
|
||
|
||
“The Concept.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
|
||
|
||
“Add a reactor named compute that multiplies the input by three and link them both.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 5) That's interesting, int the sense we need a way to define the abstraction of the model and understand the target artifact that will container what the prompt is asking. Here the multiplier function is in the code and not in the model, who decided that?
|
||
|
||
What if I change the final model source? Is this considered in the process? This manual intervention should be also used to update the model accordingly.
|
||
|
||
“From here create an alternative of the compute reactor that multiplies the input by five.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 5) Here there is the decision to where the new reactor should be connected to
|
||
|
||
“Figure 4:” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 5) It is important to clarify that this is the modeling phase, the "configuration" step is not shown in the example. The settings related to the definition of the Lingua Franca language is important and not shown in the Figure.
|
||
|
||
“Listing 2: Current timer definintion in the Lingua Franca grammar” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 6) The efforts required to define the API that is specific for the language at hand is not clear. I gues that for each language, corresponding tools need to be defined. This phases should be more elaborated i the paper in order to substantiate it also with respect to the complexity of the target modeling language.
|
||
|
||
“we explored how similar refinement workflows can be extended to the development of domain-specific languages” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 7) The process presented in this paper is more on the modeling phase and not on the modeling language definition.
|
||
|
||
Consider that the comments tagged with #5fb236 are just highlights, while those tagged with #e56eee and #a28ae5 are important sentences. Please pay attention instead to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows:
|
||
|
||
SUMMARY:
|
||
|
||
COMMENTS:
|
||
|
||
Please, avoid the typical ChatGPT dash character, and do not write in bullet points, |