DemonstrationsASE 2019

The objective of the ASE 2019 Demonstrations Track is to excite the software engineering community about new advances in our field through compelling demonstrations that help advance research and practice. The track is a highly interactive venue where researchers and practitioners can demonstrate their tools and discuss them with attendees.

Accepted Papers

Call for Contributions

Demonstrations should be tool-based and describe novel aspects of early prototypes or mature tools.

The tool demonstrations must communicate clearly the following information to the audience:

• the envisioned users;
• the software engineering challenge it proposes to address;
• the methodology it implies for its users; and
• the results of validation studies already conducted for mature tools,
• or the design of planned studies for early prototypes.

Highlighting scientific contributions through concrete artifacts is a critical supplement to the traditional ASE research papers. A demonstration provides the opportunity to communicate how the scientific approach has been implemented or how a specific hypothesis has been assessed, including details such as implementation and usage issues, data models and representations, APIs for tool and data access. Authors of regular research papers are thus also encouraged to submit an accompanying demonstration paper, stating clearly the contributions of the tool paper over the research paper.

EVALUATION

Each submission will be reviewed by at least three members of the demonstrations selection committee. The evaluation criteria include:

• the relevance of the proposed demonstration for the ASE audience;
• the technical soundness of the demonstrated tool;
• the originality of its underlying ideas;
• the quality of the optionally provided video, code, and datasets;
• and the degree to which it considers the relevant literature.

Tool demos that can demonstrate real-world applicability of the underlying ideas, e.g. by references to industrial case studies, will be particularly appreciated.

SUBMISSION

Submissions must conform to the ASE 2019 formatting and submission instructions (IEEE format). In particular, submissions of demonstrations papers must meet the following criteria:

• A demonstration submission must not exceed four pages (including all text, references, and figures).
• Authors are encouraged to submit a short video (between three and five minutes long) illustrating the demonstration. The video should be made available on YouTube at the time of submission. Videos should (i) provide an overview of the tool’s capabilities; (ii) walk through (some of) the tool capabilities; (iii) where appropriate, provide clarifying voice-over and/or annotation highlights; and (iv) be engaging and exciting for the watcher!
• Authors are encouraged to make their code and datasets open source, and to provide a URL for the code and datasets with the submission.
• A submission must not have been previously published in a demonstration form and must not simultaneously be submitted to another symposium other than ASE.
• Submissions for the tool track will NOT follow double-blind review process. If a tool track submission is accompanying a submission to the research track (which is double blind), please email the track chairs notifying them about this. The chairs will ensure that tool papers and research papers are not reviewed by the same people, to avoid revealing the authorship of research papers.
• The paper submission must be in PDF.

Submissions that do not comply with the instructions will be rejected without review. For further information, please email the track chairs.

Papers must be submitted electronically through HotCRP by June 19, 2019. At the end of the abstract, please append the URLs, if any, at which your demo video, code, and datasets can be found. Please note that for consistency, we require that ALL videos be uploaded to YouTube and made accessible during the time of reviewing. Authors of successful submissions will have the opportunity to revise the paper, the video (and its hosting location), the code, and the datasets by the camera-ready deadline.