Call for research papers

Home / Call for Papers / Call for research papers


The International Systems and Software Product Line Conference (SPLC) is the leading conference on variability and configuration of hardware and software. Researchers, practitioners, and educators present and discuss most recent ideas, trends, experiences, challenges, and solutions to advance the state-of-the-art. In the 23rd edition of the conference, we aim to continue the success of previous years by inviting high quality submissions for the research track.

Even though SPLC started more than two decades ago with a focus on software product lines, it has become an event for numerous closely related areas, such as configurable systems, product configuration, and software variability. The need for extensive exchange between those areas can be illustrated by the following example: There is a fast growing market for 3D printers. The market demands for advances in hardware and software so frequently that efficient configuration techniques are required for both. At the same time, all stakeholders, including managers, marketers, makers, programmers, and customers, want to explore the configuration space and understand the consequences of their decisions. In the context of mass customization, an interdisciplinary research effort is required that unifies researchers from numerous areas.


Abstract submission: March 12, 2019
Paper submission: March 19, 2019
Notification: May 14, 2019
Artifact submission: May 28, 2019
Artifact notification:
June 18, 2019
Camera-ready papers: June 25, 2019
Conference: September 9-13, 2019


The following list of topics aims to summarize those areas in more detail, whereas we also invite submissions to related topics. If in doubt, feel free to ask the track chairs (see below).

  • Business process management, economics, and organizational issues of product-line engineering
  • Development process models for variation (e.g., proactive, reactive, extractive, and agile development)
  • Domain analysis, requirements engineering, and feature traceability
  • Variability management and variability modeling (e.g., feature models, decision models)
  • Architecture, design, and visualization of product lines
  • Specification and modeling of product lines (e.g., domain-specific modeling, model-driven engineering, model transformations, generative modeling)
  • Realization and implementation techniques for reuse (e.g., domain-specific languages, modules, components, cloud services, platforms, frameworks, plug-ins, apps, preprocessors, feature toggles, version control systems, variation control systems)
  • Programming languages, model-driven engineering, and domain-specific languages for variation
  • Testing of configurable systems (e.g., product sampling, test-case selection and prioritization, model-based testing, coverage, mutations, debugging, automatic repair, A/B testing)
  • Static quality assurance techniques for product lines (e.g., formal methods, program analysis, model checking, consistency checking, validation, verification)
  • Modeling, analysis, and optimization of non-functional properties (e.g., performance, energy efficiency, interoperability, adaptability, maintainability, dependability, reuse, scalability, reliability)
  • Security, safety, and synthesis of product lines
  • Configuration management and automated deployment
  • Evolution, maintenance, and continuous integration for product lines (e.g., DevOps)
  • Reverse engineering, variability mining, and refactoring of variability (e.g., migration from clone-and-own, design patterns)
  • Multi product lines, software ecosystems, program families, product lines of product lines, systems of systems
  • Knowledge-based and rule-based configuration
  • Configurability for cyber-physical systems and applications to big data
  • (Self-)adaptive systems, reconfigurable systems, and dynamic software product lines
  • Green and sustainable technologies for variation
  • Human and social aspects of product lines (e.g., collaborative modeling and development, cooperative configuration processes, program comprehension)
  • Recommendation systems and artificial intelligence for configurators and feature models (e.g., SAT solvers, BDD, CSP solvers, SMT solvers, answer set programming, explanations)
  • Genetic algorithms, neural networks, and machine learning for product lines
  • Education of product lines and configurators (e.g., teaching, training, dissemination)
  • Methods, tools, and data sets targeting variation
  • Empirical evaluations of all topics above (user studies, case studies, controlled experiments, surveys, rigorous measurements)


The research track is open to submissions in two categories:

  • Full papers describing original results of conceptual, theoretical, empirical, and experimental research. The papers in this category must rely on theoretical or empirical evaluation.
  • Short papers describing emerging ideas and outstanding challenges along with possible approaches for resolving them.Each submission will be carefully reviewed by at least three members of the research track program committee. The page limit is 12 pages for full papers and 7 pages for short papers, whereas the last two pages may only be used for references. Submissions must follow the 2017 ACM Master Article Template:

Latex users are indicated to use the “sigconf” option, so they are recommended to use the template that can be found in “sample-sigconf.tex”. In this way, the following latex code can be placed at the start of the latex document:


\acmConference[SPLC'19]{23nd International Conference on Software Product Line}{9--13 September, 2019}{Paris, France}

Proceedings of earlier SPLC instance have been published in the ACM Digital Library. At least one author of each accepted submission must register and attend SPLC 2019 in order for the submission to be published. SPLC is ranked as a top conference. Submissions need to be sent using EasyChair:


Authors of accepted research papers are invited to submit for evaluation and publication artifacts associated with the paper. According to ACM’s “Result and Artifact Review and Badging” policy, an “artifact” is “a digital object that was either created by the authors to be used as part of the study or generated by the experiment itself […] software systems, scripts used to run experiments, input datasets, raw data collected in the experiment, or scripts used to analyze results.”

Accepted artifacts will receive one of the following badges on the first page of the paper, table of contents, and in the ACM Digital Library:

  • Artifacts Evaluated – Functional: The artifacts are complete, well-documented and allow to obtain the same results as the paper.
  • Artifacts Evaluated – Reusable: As above, but the artifacts are of such a high quality that they can be reused as is on other data sets or for other purposes.Authors of accepted Research Track papers who want to publish an artifact should submit a PDF via Easychair (select the Research Artifacts track). The PDF should contains a stable URL (or DOI) to the artifacts and that explains the steps or general instructions to execute/analyze the artifact. Each artifact submission will be reviewed by at least two reviewers.

Each accepted research paper associated with an accepted artifact will get one extra page in the proceedings. The authors must ensure that the artifacts are available from a stable URL or DOI. Please note that these badges exclude proprietary data or tools.


Laurence Duchien

University Lille, France

Thomas Thüm

 TU Braunschweig, Germany