106 lines
4.7 KiB
Markdown
106 lines
4.7 KiB
Markdown
file:: [sle23-paper89_1692364405788_0.pdf](../assets/sle23-paper89_1692364405788_0.pdf)
|
||
file-path:: ../assets/sle23-paper89_1692364405788_0.pdf
|
||
|
||
- hose rationales are based on good practices and lessons learned while developing a language workbench for modeling languages.
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64e08663-5b98-4dd1-8362-e3251488c840
|
||
- We also discuss alternative approaches Obeo considered
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64e0867b-4036-47b9-887d-bc800a9ae5c7
|
||
- domain experts and their engineering problems
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64e0868e-753e-4abd-906d-6edfb77b33fa
|
||
- [8] Ana Pescador, Antonio Garmendia, Esther Guerra, Jesús Sánchez Cuadrado, and Juan de Lara. 2015. Pattern-based development of domain-specific modelling languages. In 2015 ACM/IEEE 18th International Conference on Model Driven Engineering Languages and Systems(MODELS). IEEE, 166–175.[9] Jesús Sánchez-Cuadrado, Juan De Lara, and Esther Guerra. 2012. Bottom-up meta-modelling: An interactive approach. In Model Driven Engineering Languages and Systems: 15th International Conference, MODELS 2012, Innsbruck, Austria, September 30–October 5, 2012. Proceedings 15. Springer, 3–19
|
||
ls-type:: annotation
|
||
hl-page:: 6
|
||
hl-color:: green
|
||
id:: 64e086a5-1160-4222-ad9d-bb2c1cfc80bd
|
||
- Language workbenches, such as Sirius Desktop and Sirius Web, aim to simplify the process of creating such environments by providing an environment in which language designers can create their own modeling environment.
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64e08cda-8cf2-4c3c-ace0-be2607394876
|
||
- This paper discusses the main Sirius Web rationales based on lessons learned from the development of multiple industrial modeling workbenches using Sirius Desktop.
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64e08cee-4a7f-43b6-9f16-e42b805f4c0c
|
||
- features and usability,
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: purple
|
||
id:: 64e08d0f-c31a-498f-aadb-75a0cde33fb2
|
||
- i) helping language workbench developers in making design choices
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: purple
|
||
id:: 64e08d2c-8bd0-408a-b8e6-4b862fbd6206
|
||
hl-stamp:: 1692437818726
|
||
- ii) identify open questions for the software language engineering research community.
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: purple
|
||
id:: 64e08d32-9230-4e8e-8337-e80cd82dc8ec
|
||
hl-stamp:: 1692437821531
|
||
- language designer
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64e08d73-8f28-4c4a-9641-43af2e5aadc6
|
||
- end-use
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64e08d79-eeb7-432e-9371-9db4d3d88ea4
|
||
- three
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: red
|
||
id:: 64e08d80-8f89-4155-83d9-30256f811baa
|
||
hl-stamp:: 1692437919596
|
||
- We define a modeling workbench as the combination of one or more modeling languages with the representation(s) that end-users can use to visualize and edit models
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64e08def-17d0-41a7-bc21-29b15dd22f51
|
||
- Domain DSL
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64e08dfe-638e-4564-b90b-bc3d8f030d11
|
||
- View DSL
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64e08e01-67ed-4c63-9fdf-171db0038ead
|
||
- With the View DSL, the language designer can choose one or several representation types and design from the representation type specific elements (e.g., node or edge for diagrams) the concrete syntax.
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: red
|
||
id:: 64e08e22-4b2f-4915-9c09-77b40f1f3f5e
|
||
- : the style of the graphical elements (e.g., node color, arrow type); the tools used to interact with the model through the associated concrete syntax elements, using pre-defined operations (e.g., instantiate/delete a model element, set a value for an attribute of a model element).
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: red
|
||
id:: 64e08e51-bbf5-4fef-bad4-ba031b563448
|
||
- Using the Java API, the language designer can contribute to extend the higher levels, for instance the low-code level. For instance, from the Java-based API a language designer can add new representation types to be configured later on.
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: yellow
|
||
id:: 64e08f6d-48f9-47ea-9e60-cc0d492c069c
|
||
- Rationale 1: Proposing different level of development interfaces to create a modeling workbench
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: yellow
|
||
id:: 64e08fb9-0828-46e8-a6b4-e07ef2a7f925
|
||
- Sirius Web, the development of the abstract syntax and concrete syntax are two different activities with their own lifecycle.
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64e090be-3814-454f-9eb6-b5c895e50dff |