‹Programming› 2018
Mon 9 - Thu 12 April 2018 Nice, France

Today’s IT systems are often distributed and heterogeneous. Therefore, many (functional and non-functional) system requirements must be implemented across different layers of the system stack. This workshop is interested in experiences from implementing such systems and methods or tools for their development and support.

Call for Papers

The landscape of computation platforms has changed dramatically in recent years. Emerging systems - such as wearable devices, smartphones, unmanned aerial vehicles, Internet of things, cloud computing servers, heterogeneous clusters, and data centers - pose a distinct set of system-oriented challenges ranging from data throughput, energy efficiency, security, real-time guarantees, to high performance. In the meantime, code quality, such as modularity or extensibility, remains a cornerstone in modern software engineering, bringing in crucial benefits such as modular reasoning, program understanding, and collaborative software development. Current methodologies and software development technologies should be revised in order to produce software to meet system-oriented goals, while preserving high internal code quality. The role of the Software Engineer is essential, having to be aware of the implications that each design, architecture and implementation decision has on the application-system ecosystem.

This workshop is driven by one fundamental question: How does internal code quality interact with system-oriented goals? We welcome both positive and negative responses to this question. An example of the former would be modular reasoning systems specifically designed to promote system-oriented goals, whereas an example of the latter would be anti-patterns against system-oriented goals during software development.

Topics of Interest

Areas of interest include but are not limited to:

  • Energy-aware software engineering (e.g. energy efficiency models, energy efficiency as a quality attribute)
  • Modularity support (e.g., programming language design, development tools or verification) for applications in resource-constrained or real-time systems
  • Emerging platforms (e.g., Internet of Things and wearable devices)
  • Security support (e.g., compositional information flow, compositional program analysis)
  • Software architecture for reusability and adaptability in systems and their interactions with applications
  • Empirical studies (patterns and anti-patterns) on the relationship between internal code quality and system-oriented goals
  • Software engineering techniques to balance the trade-off between internal code quality and efficiency
  • Memory bloats and long-tail performance problems across modular boundaries
  • Program optimization across modular boundaries
  • Internal code quality in systems software
  • Reasoning across applications, compilers, and virtual machines

Author Instructions

PASS is designed to stimulate interactions and debates in an informal environment. We welcome papers that identify new problems or report work in progress. A good PASS submission should be interesting, concrete, and clear. It does not need to describe a complete solution. Specifically, PASS accepts both regular papers and position papers. Regular papers must not exceed 6 pages in length (including all references and appendixes), and short papers must not exceed 2 pages in length.

Submissions should use the ACM Conference acmart Format with the ‘sigconf’ option with a font size of 10 point and the font family Times New Roman. All submissions should be in PDF format. If you use LaTeX or Word, please use the provided ACM acmart templates. Otherwise, please follow the ACM author instructions.

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 for review using the LaTeX command \settopmatter{printfolios=true} (see examples in template).

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.

The submission URL will be published soon.