Description

Domain-Specific Modeling (DSM) provides a modern solution to demands for higher productivity by constricting the gap between problem and solution modeling. In the past, productivity gains have been sought through new programming languages. Today, domain-specific modeling languages provide a viable solution for continuing to raise the level of abstraction beyond coding, making development faster and easier.

In DSM, the models are constructed using concepts that represent things in the problem domain, not concepts of a given programming language. The modeling language follows the domain abstractions and semantics, allowing developers to perceive themselves as working directly with domain concepts. The models represent simultaneously the design, implementation and documentation of the system, which can be generated directly from them. In a number of cases the final products can be automatically generated from these high-level specifications with domain-specific code generators. This automation is possible because of domain-specificity: both the modeling language and code generators fit the requirements of a narrowly-defined domain, usually inside a single organization.

The workshop welcomes submissions that address Domain-Specific Modeling on practical or theoretical levels. Our main focus is on graphical domain-specific languages but we will also consider submissions on textual or other DSLs. Some of the issues that we would like to see addressed in this workshop are:

- Industry/academic experience reports describing success/failure in implementing and using DSM languages/tools
- Approaches to identify constructs for DSM languages
- Novel features in language workbenches / tools to support DSM
- Approaches to implement metamodel-based modeling languages
- Metamodeling frameworks and languages
- Modularization technologies for DSM languages and models
- Novel approaches for code generation from domain-specific models
- Issues of support/maintenance for systems built with DSM
- Evolution of languages along with their domain
- Organizational and process issues in DSM adoption and use
- Demonstrations of working DSM solutions (languages, generators, frameworks, tools)
- Identification of domains where DSM can be most productive in the future (e.g. embedded systems, product families, systems with multiple implementation platforms)