Software Language Engineering (SLE) is the application of systematic, disciplined, and measurable approaches to the development, use, deployment, and maintenance of software languages. The term “software language” is used broadly, and includes: general-purpose programming languages; domain-specific languages (e.g. BPMN, Simulink, Modelica); modeling and metamodeling languages (e.g. SysML and UML); data models and ontologies (e.g. XML-based and OWL-based languages and vocabularies).
Mon 31 Oct
|10:30 - 10:40|
|10:40 - 11:05|
Zirun ZhuNational University SOKENDAI, Japan, Yongzhe ZhangNational University SOKENDAI, Japan, Hsiang-Shang ‘Josh’ KoNational Institute of Informatics, Pedro MartinsUniversity of California at Irvine, USA, João SaraivaUniversity of Minho, Portugal, Zhenjiang HuNational University SOKENDAI, JapanDOI
|11:05 - 11:30|
Nicolas LaurentUniversité Catholique de Louvain, Belgium, Kim MensUniversité Catholique de Louvain, BelgiumDOI Pre-print
|11:30 - 11:45|
Juha-Pekka TolvanenMetaCase, FinlandDOI Pre-print Media Attached
|11:45 - 12:10|
Markus Völteritemis, Germany, Tamás Szabóitemis AG / TU Delft, Sascha Lissonitemis AG, Bernd Kolbitemis AG, Sebastian ErdwegDelft University of Technology, Netherlands, Thorsten BergerChalmers University of Technology, SwedenDOI Pre-print Media Attached
|13:30 - 13:55|
Daniel SeyboldUlm University, Germany, Jörg DomaschkaUlm University, Germany, Alessandro RossiniSINTEF, Norway, Christopher B. HauserUlm University, Germany, Frank GriesingerUlm University, Germany, Athanasios TsitsipasUlm University, GermanyDOI
|13:55 - 14:20|
Salvador MartínezOpen University of Catalonia, France, Jokin GarcíaIK4-IKERLAN Research Center, Spain, Jordi CabotOpen University of Catalonia, SpainDOI
|14:20 - 14:45|
|DOI Media Attached|
|14:45 - 15:00|
Erwan BousseTU Vienna, Austria, Thomas DegueuleInria, France, Didier VojtisekInria, France, Tanja MayerhoferTU Vienna, Austria, Julien DeAntoni, Benoit CombemaleUniversity of Rennes 1, FranceDOI Pre-print Media Attached File Attached
|15:40 - 16:05|
|DOI Media Attached|
|16:05 - 16:30|
BSML-mbeddr: Integrating Semantically Configurable State-Machine Models in a C Programming EnvironmentDOI Media Attached
|16:30 - 16:55|
Tanja MayerhoferTU Vienna, Austria, Manuel WimmerTU Vienna, Austria, Antonio VallecilloUniversity of Málaga, SpainDOI Media Attached
|16:55 - 17:10|
Thomas KühnTU Dresden, Germany, Kay BierzynskiTU Dresden, Germany, Sebastian RichlyTU Dresden, Germany, Uwe AßmannTU Dresden, GermanyDOI Media Attached
|17:10 - 17:20|
Tue 1 Nov
|08:30 - 10:00|
Robby FindlerNorthwestern UniversityLink to publication Media Attached
|10:30 - 10:55|
|DOI Pre-print Media Attached File Attached|
|10:55 - 11:20|
Sven KeidelDelft University of Technology, Netherlands, Wulf PfeifferTU Darmstadt, Germany, Sebastian ErdwegDelft University of Technology, NetherlandsDOI Media Attached File Attached
|11:20 - 11:45|
Luis Eduardo de Souza AmorimDelft University of Technology, Netherlands, Sebastian ErdwegDelft University of Technology, Netherlands, Guido WachsmuthDelft University of Technology, Netherlands, Eelco VisserDelft University of Technology, NetherlandsDOI Media Attached
|11:45 - 12:00|
Joel LindholmLund University, Sweden, Johan ThorsbergLund University, Sweden, Görel HedinLund University, SwedenDOI Media Attached
|13:30 - 13:55|
Bart MeyersUniversity of Antwerp, Belgium, Joachim DenilUniversity of Antwerp, Belgium, István DávidUniversity of Antwerp, Belgium, Hans VangheluweUniversity of Antwerp, CanadaDOI
|13:55 - 14:20|
Felipe Bañados SchwerterUniversity of British Columbia, CanadaDOI
|14:20 - 14:45|
Ahmad Salim Al-SibahiIT University of Copenhagen, Denmark, Aleksandar S. DimovskiIT University of Copenhagen, Denmark, Andrzej WąsowskiIT University of Copenhagen, DenmarkLink to publication DOI Pre-print Media Attached
|14:45 - 15:00|
Volodymyr BlagodarovRaincode, Belgium, Yves JaradinRaincode, Belgium, Vadim ZaytsevRaincode, BelgiumDOI
|15:40 - 16:05|
Amine Benelallam, Massimo TisiAtlanMod, France, Jesús Sánchez CuadradoAutonomous University of Madrid, Spain, Juan de LaraAutonomous University of Madrid, Spain, Jordi CabotOpen University of Catalonia, SpainDOI
|16:05 - 16:30|
Ralf LämmelUniversity of Koblenz-Landau, GermanyDOI Media Attached
|16:30 - 16:45|
André L. SantosUniversity Institute of Lisbon, Portugal, Eduardo GomesUniversity Institute of Lisbon, PortugalDOI
|16:45 - 17:00|
Call for Papers
SLE aims to be broad-minded and inclusive about relevance and scope. We solicit high-quality contributions in areas ranging from theoretical and conceptual contributions to tools, techniques, and frameworks in the domain of language engineering. Topics relevant to SLE cover generic aspects of software languages development rather than aspects of engineering a specific language. In particular, SLE is interested in principled engineering approaches and techniques in the following areas:
- Language Design and Implementation
- Approaches and methodologies for language design
- Static semantics (e.g., design rules, well-formedness constraints)
- Techniques for behavioral / executable semantics
- Generative approaches (incl. code synthesis, compilation)
- Meta-languages, meta-tools, language workbenches
- Language Validation
- Verification and formal methods for languages
- Testing techniques for languages
- Simulation techniques for languages
- Language Integration
- Coordination between of heterogeneous languages and tools
- Mappings between languages (incl. transformation languages)
- Traceability between languages
- Deployment of languages to different platforms
- Language Maintenance
- Software language reuse
- Language evolution
- Language families and variability
- Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance)
- Empirical evaluation and experience reports of language engineering tools
- User studies evaluating usability
- Performance benchmarks
- Industrial applications
Research papers: These should report a substantial research contribution to SLE or successful application of SLE techniques or both. Full paper submissions must not exceed 12 pages excluding bibliography (in ACM SIGPLAN conference style).
Tool papers: Because of SLE’s interest in tools, we seek papers that present software tools related to the field of SLE. Selection criteria include originality of the tool, its innovative aspects, and relevance to SLE. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must provide a tool description of 4 pages in SIGPLAN proceedings style (see above), with 1 optional additional page for bibliographic references, and a demonstration outline including screenshots of up to 4 pages. Tool demonstrations must have the keywords “Tool Demo” or “Tool Demonstration” in the title. The 4-page tool description will, if the demonstration is accepted, be published in the proceedings. The 4-page demonstration outline will be used by the program committee only for evaluating the submission.
Workshops: Workshops will be organized by SPLASH. Please inform us and contact the SPLASH organizers if you would like to organize a workshop of interest to the SLE audience.
All submitted papers will be reviewed by at least three members of the program committee. All accepted papers, including tool papers will be published in ACM Digital Library.
Authors of distinguished papers from the conference will be invited to revise and submit extended versions of their papers for a Journal special issue.
Distinguished paper. Award for most notable paper, as determined by the PC chairs based on the recommendations of the programme committee.
Distinguished reviewer. Award for distinguished reviewer, as determined by the PC chairs using feedback from the authors.
Distinguished artefact. Award for the artifact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artifact evaluation committee.
For additional information, clarification, or answers to questions please contact the Program Chair.
Instructions for Authors
For fairness reasons, all submitted papers should conform to the formatting instructions. Submissions that violate these instructions may be rejected without review, at the discretion of the Program Chair.
Please take a moment to read the instructions below before using the submission site. Note that camera ready versions will be collected by Conference Publishing Consulting.
Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLAN’s Republication Policy. Submitters should also be aware of ACM’s Policy and Procedures on Plagiarism.
Submissions should use the ACM SIGPLAN Conference Format, 10 point font, using the font family Times New Roman. All submissions should be in PDF format. If you use LaTeX or Word, please use the provided ACM SIGPLAN Templates provided here. Otherwise, follow the author instructions.
Note that by default the SIGPLAN Conference Format templates produce papers in 9 point font. If you are formatting your paper using LaTeX, you will need to set the 10pt option in the \documentclass command. If you are formatting your paper using Word, you may wish to use the provided Word template that supports this font size. Please include page numbers in your submission. Setting the preprint option in the LaTeX \documentclass command generates page numbers. Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible.
To ensure that papers stay focused on their core contributions, submissions of research papers should be no more than 12 pages, excluding bibliographic references. Tool papers are limited to 4 pages, excluding 1 optional page containing bibliographic references, and excluding 4 pages max. of demonstration outline.
AUTHORS TAKE NOTE: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work.
Keynote: Robby Findler
Redex is a programming language designed to support semantics engineers as they experiment with programming language models. To explore a model, an engineer writes down grammars, type systems, and operational semantics in a notation inspired by the programming languages literature. Redex breathes life into the model, building typing derivations, running example expressions, and using random generation to falsify claims about the model.
This talk gives an overview of Redex, motivating its design choices and giving a sense of how it feels to program in Redex. Then the talk dives into some of the techniques that Redex uses to generate random expressions.
This year, SLE introduces an evaluation process for assessing the quality of the artifacts on which papers are based, treating them as first-class citizens and fostering the culture of experimental reproducibility. Authors of accepted papers are invited to submit artifacts.
Artifacts (tools, grammars, datasets, proofs, links, models, videos, visualizations) that live up to the expectations created by the paper will receive a badge of approval from the Artifact Evaluation Committee (AEC). They will be invited for inclusion as freely downloadable supplementary material, ensuring permanent and durable storage. There is no obligation for authors of accepted papers to participate in this process, but we strongly encourage authors to consider this possibility as availability will greatly benefit readers and increase the impact of their work.
The submission most significantly exceeding expectations, will receive the Distinguished Artefact award, sponsored by Raincode.
In a nutshell, a good artifact is:
(1) consistent with the paper
(2) as complete as possible
(4) easy to (re)use
The artifact evaluation process of SLE borrows heavily from processes described at artifact-eval.org, ECOOP 2016 and ICSME 2016. We have an open reviewing model in which artifacts will be submitted to a GitHub repository, and reviewing/discussion will be conducted through GitHub issues.