We will evaluate all submissions according to the following three criteria:

    1. Contribution and Originality
    2. Technical correctness
    3. Writing Quality

    

Contribution and Originality

We welcome novel theoretical insights, practical solutions, tools, benchmarks and system-level applications, but also application scenarios, use cases, technology transfer success stories or failures and detailed descriptions of open and unsolved problems. A contribution must be original and non-trivial, related to real-time systems, and of interest to the community and or to the real-time industry. Consequently, papers relying on simple models must have more fundamental theoretical insights than papers that include more details by construction, such as system-level implementations. In any case the models, assumptions and the applications scenarios must be well justified. Below we provide a link to an incomplete list of realistic task models from industrial challenges, which do not require any further justification. Deviations from such models or strong simplifications require justification. We welcome system-level implementations or industrial papers even without theoretical contribution, if the practical implementation/use-case/application scenario/etc. is considered a valuable contribution in its own right. In such cases, we expect a proper justification and motivation.

Industrial Challenges with (incomplete) list of realistic task models

Technical correctness

Technical correctness is a mandatory requirement for acceptance. We consider it to be the duty of the authors to convince the reviewers of the technical correctness of the papers by whatever means the authors consider appropriate. We will only accept papers when we are convinced of their correctness. We acknowledge that due to IP constraints, implementation papers may not be able to provide all details. In this case, we expect a sufficient abstraction of the details. We encourage open-source initiatives and artifact evaluation to provide further confidence in the paper correctness. For theoretical contributions we strongly encourage the use of computer-guided proof systems.

Writing Quality

The paper must be well written, draw a clear connection to the addressed real-time problem, and be easily readable. We expect the authors to proof-read their paper and to reduce the number of typos and grammatical mistakes. Each submission must adhere to the provided template and page limit. Modifications to the template, especially to the font size and the margins, lead to paper rejection. Additional material that does not fit within the page limit can be published as a technical report, but will only be read at the reviewers' discretion. The technical report has to be provided via e-mail to the program chair.