1 / 11

An Exercise in Iterative Domain-Specific Language Design

This exercise explores the iterative design of domain-specific languages (DSLs) across various platforms. It discusses the context of concurrent objects, controllers, and communication methods, addressing model transformations and language evolution. The analysis identifies three main influences on DSL evolution: problem domain, target platforms, and model quality aspirations. It outlines the transformation strategies, verification methods, and simulation approaches used in evolving DSLs. Future work may involve studying fine-grained transformations, enhancing graphical editors, and evolving extended syntax for model checking.

geri
Télécharger la présentation

An Exercise in Iterative Domain-Specific Language Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An Exercise in Iterative Domain-Specific Language Design Marcel van Amstel Mark van den Brand Luc Engelen

  2. Outline Context Domain-Specific Language Platforms Model Transformations Language Evolution Conclusions Future Work

  3. Context

  4. Context • Concurrent objects • Controllers • Hardware • Conveyors • Motors • Sensors • Communication • Wireless • Wired

  5. Domain-Specific Language

  6. Domain-Specific Language

  7. Platforms • Simulation • POOSL • Execution • NQC • Verification • PROMELA/SPIN

  8. Model Transformations • DSL • DSL(Asynchronous) • DSL(Lossless • Communication) • DSL(Limited number of objects) • Verification • Simulation • Execution T1 T2’ T3 V T1’ E V S T2 T3’

  9. Language Evolution • Platforms were added one by one • With each step, the DSL evolved • Variable scoping • Initial values for variables • Conditional message reception • Bugfixes • … • With each step, the transformations evolved • Transformation strategy • More fine-grained

  10. Conclusions • Three main influences on DSL evolution: • problem domain, • target platforms, • aspiration to uphold model quality • Attributes of model quality may be conflicting • Adding target platforms makes the DSL more specific

  11. Future Work Study the effects of more fine-grained model transformations Graphical model editor Constraining the language Correctness proofs Extending the syntax to simplify the process of model checking Research the evolution of a more extensive DSL

More Related