SLE 2012

Took place in Dresden, Germany
Co-located with GPCE
Hosted a “SL(E)BOK 2.0” workshop
Recovered conference website
86 abstracts, 62 full submissions, 19 papers: 17 full papers and 2 tools, acceptance rate 31%
Call for Papers
List of Papers
Organisers
Tags requested:
- T1A T1B T1D T2A T2B T2D T2E T3A T3B T3C T3D T3E T3F T4A T4B T4C T4E T4F T5A T5B T5C T5D T5E T5H T6A T6B T6D
Tags received:
- T1A T1B T1C T1D T1E T2B T2C T3A T3B T3C T3E T3F T4A T4B T4C T4D T4F T4G T5B T5C T5D T5F T5H T6B T6D T6G

Call for Papers (source, 103 taggings)

The 5th International Conference on Software Language Engineering (SLE 2012) is devoted to topics related to artificial languages in software engineering. SLE’s foremost mission is to encourage and organize communication among communities that have traditionally looked at software languages from different and yet complementary perspectives. Thus, of particular relevance to SLE are technologies, methods, experimentsT5E, and case studiesT6A on software languages from modelwareT6D, grammarwareT6D and ontologywareT3E perspectives.

TYPES OF SUBMISSIONS

We solicit the following types of papers:

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 20 pages.
IndustrialT6B experience papersT6A: These papers discuss practical applicationsT6B of SLE technology with an emphasis on the advantages and disadvantages of the method, techniques, or tools used. These papers must not exceed 10 pages.
Tool demonstration papers: Because of SLE’s ample interest in tools, we seek papers that present software tools related to the field of SLE. These papers will accompany a tool demonstration to be given at the conference. These papers must not exceed 10 pages. The selection criteria include the originality of the tool, its innovative aspects, the relevance of the tool to SLE, and the maturity of the tool.

Submitted articles must not have been previously published or currently be submitted for publication elsewhere.

SCOPE

The term “software language” refers to artificial languages used in software development including general-purpose programming languagesT3D, domain-specific languagesT3C, modeling and meta-modeling languagesT3A, data models, and ontologiesT3E. Examples include general purpose modeling languagesT3D such as UML, but also domain-specific modeling languagesT3C for business process modeling, such as BPMN, or embedded systems, such as SimulinkT4E or Modelica, and specialized XML-based and OWL-based languages and vocabularies. The term “software language” also comprises APIsT3F and collections of design patterns that define a language implicitly.

Software language engineering is the application of systematic, disciplined, and quantifiable approaches to the development (designT1A, implementation, testingT5C, deploymentT2D), use, and maintenanceT2B (evolutionT2B, recoveryT2A, and retirementT2A) of these languages. Of special interest are (1) formal descriptions of languagesT3A that are used to designT1A or generate language-based tools and (2) methods and tools for managing such descriptions, including modularizationT1D, refactoringT4B, refinementT4C, compositionT1D, versioningT2B, co-evolutionT2B, recoveryT2A, and analysisT5B.

TOPICS OF INTEREST

We solicit high-quality contributions in the area of SLE ranging from theoretical and conceptual contributions to tools, techniques, and frameworks that support the aforementioned lifecycleT2A activities. The topics of interest include, but are not limited to the following:

FormalismsT5D used in designing and specifying languages and tools that analyze language descriptions: Examples are formalisms for grammarsT3A, schemas, ontologiesT3E, and metamodels; tools that detect inconsistencies in metamodelsT5B or analyze grammars to build a parserT4C; and formal logics and proof assistants that verify propertiesT5D of language specificationsT3A.
Language implementation techniquesT4A: These include advances in traditional compiler generator tools such as parser/scanner generatorsT4C, attribute grammar systemsT3A, term-rewriting systemsT4B, functional-programming-based combinator libraries; also of interest are metamodel-based and ontologyT3E tools implementing constraint, rule, view, transformationT3B, and query formalismsT5D and engines.
Program and model transformation toolsT4B: Examples include tools that support program refinement and refactoringT4B, model-based developmentT4C, aspect and model weaving, model extraction, metamodeling, model transformationsT4B, round-trip engineeringT4B, and runtime system transformation.
Composition, integrationT1D, and mapping toolsT4B for managing different aspects of software languages or different manifestations of given language: Examples are tools for mappingT4B between the concrete and abstract syntax of a language and for managing textual and graphical concrete syntax for the same or closely related languages.
TransformationsT4B and transformation languagesT3B between languages and models: transformationT4B descriptions and tools or XML/RDF/ontologyT3E/object/relational mappingsT4B; also, reasoning for and aboutT5D transformationsT4B.
Language evolutionT2B: Included are extensible languagesT1D and type systemsT1B and their supporting tools and language conversionT4B tools. OntologiesT3E and APIsT3F, when considered as languages, are subject to evolutionT2B; thus tools and techniques that assist developers in using a new versionT2B of an ontologyT3E or an APIT3F or a competing implementation in a program are also of interest.
Approaches to the elicitationT5A, specificationT5A, and verificationT5D of requirements for software languagesT5A: Examples include the use of requirements engineering techniquesT5A in domain engineering and in the development of domain-specific languagesT3C and the application of logic-based formalismsT5D for verifyingT5D language and domain requirementsT5A.
Language development frameworksT4A, methodologies, techniques, best practices, and tools for the broader language lifecycleT2A covering phases such as analysis, testingT5C, and documentationT2E. For example, frameworks for advanced type or reasoning systemsT1B, constraint mechanisms, tools for metrics collection and language usage analysis, assessing language usabilityT5H, documentationT2E generatorsT4C, visualization backendsT4F, generation of testsT5C for language-based tools, knowledge and process management approaches, as well as IDE supportT4A for many of these activities are of interest.
Design challengesT1A in SLE: Example challenges include finding a balance between specificity and generality in designing domain-specific languagesT3C, between strong static typing and weaker yet more flexible type systemsT1B, or between deep and shallow embeddingT1D approaches, as, for example, in the context of adding type-safe XML and database programming support to general purpose programming languagesT3D.
Applications of languages including innovative domain-specific languagesT3C or “little” languagesT3C: Examples include policy languages for security or service oriented architectures, web-engineering with schema-based generatorsT4C or ontology-based annotationsT3E. Of specific interest are the engineering aspects of domain-specific languageT3C support in all of these cases.

The program committee chairs encourage potential contributors to contact them with questions about the scope and topics of interest of SLE.

List of Papers (2+19+2, source)

Organisers

The page is maintained by Dr. Vadim Zaytsev a.k.a. @grammarware. Last updated: June 2026.