|Now accepting submissions!|
|Date Due||Friday, October 8, 2021|
|Time Due||23:59 AoE (Anywhere on Earth, UTC-12h)|
|Submission Limits||2 pages (including abstract of 250 words)|
|Submission Link||SIGCSE TS 2022 Submission via EasyChair|
|Notification to Authors||Friday, November 5, 2021|
|Camera-Ready Deadline||Tuesday, November 30, 2021|
|Duration||45 minutes (during breaks)|
ACM Policy : Prior Publication and Simultaneous Submissions
Under no circumstances shall a paper (or substantially the same paper) be simultaneously submitted to two or more publications, or to a second publication while still under review elsewhere, without a letter of notification to the Editor-in-Chief (EiC) or Program Chair (PC) of each affected publication. Failure to adhere to this policy is cause for rejection of the manuscript. Repeated violations may lead to a ban on future submissions at the discretion of the EiC or PC.”
The ACM website has the full policy.
Author Guidelines: Demos
Demos provide a way to showcase an educational tool or project in a live setting. Not designed to be sales pitches, demonstrations are a way for the community to see the relevance, potential, and innovation of the tool and allow time for discussion with its creator.
Since SIGCSE TS 2022 is planned to be held as an on-site event, Demos will take place during break periods and will last 45 minutes. This follows the Demo format as used traditionally until the SIGCSE TS 2020. Thus physical presence of at least one of the presenters at the conference site is mandatory. However, we expect there will be virtual attendees as well. The proposals must clearly state how the Demo would be run on-site and either suggest a plan to accommodate remote attendees or explain why this would not be feasible.
Single-Anonymous Review Process
Initial submissions to the Demos track are reviewed with the single-anonymous review process, where the submissions are not anonymized but reviewers are anonymous to each other and to the authors. During the discussion of a submission in EasyChair, reviewers can refer to each other by their reviewer number on that submission’s review.
How Should The Proposal Be Formatted?
Demo proposals are submitted in PDF format. The full proposal contains an abstract and a body that describes your Demo (as detailed below). Proposals are limited to 2 pages, including an abstract of 250 words, and will be reviewed with a single-anonymous process for acceptance. Note that the full proposal is used only for the review process. If the proposal is accepted, the title and authors appear in the printed program, while the title, authors, and abstract appear in both the online program and the proceedings. The format for the proposal is described in the following section.
Demo Proposal Format and Contents
Title: A descriptive title for the Demo.
Proposer(s): Include name, affiliation, email address, and website address of all proposers. You should expect most correspondence related to the conference to arrive via email. Please check your spam filter if you haven’t received an expected notification because the auto-responses generated by the conference software are sometimes blocked.
Abstract: A description of the Demo. The same abstract will also need to be submitted via a text box on the submission page. Please be sure that your description is accurate and that both submitted copies (here in the Demo Proposal, and in the submission text box) are exactly the same. Please recall that the abstract is the only part of the proposal to appear in the program and proceedings and should thus be self-contained.
Significance and Relevance of the Topic: Please include information about any recent developments in relation to the tool/project and possibly describe (or cite) evidence. Your objective is to explain how the tool/project is significant. Explain how the tool/project is important for the computing education community and what the expected benefits of using it are with regard to teaching or learning computing topics. Ideally also explain ideas for courses/topics in which the tool/project is beneficial and provide evidence of its benefits, if possible.
Expected Audience: Briefly describe the nature and size of the expected audience. This information will help reviewers assess the level of interest SIGCSE Technical Symposium attendees will have in the Demo.
Other Presenter(s): Although correspondence will be with the proposer(s) above, there might be additional presenter(s) involved.. Please list any additional such names (besides the proposer(s)) and affiliations here. Be certain that you have their commitments to attend the SIGCSE Technical Symposium. All presenters must register for the Symposium and at least one proposer or presenter must be physically present for the Demo session.
Expertise of Presenter(s): Give a summary of the qualifications of the presenter(s) as it relates to the tool/project being proposed.
Materials Provided: Briefly explain which materials such as handouts/links/codes (if any) will be provided for the audience to take home.
Agenda for the Demo: Exact timing details for organization of the Demo session are required here. Explain what the attendees can expect. Be sure to budget a realistic amount of time for questions from attendees. Describe how you will interact with and engage attendees.
Audio/Visual and Computer Requirements: Indicate any specific requirements you may have since your Demo will need to consider interacting with both on-site and virtual attendees. Note that not all requirements might be met by the conferencing software used. At the time of acceptance more information about the conferencing software’s capabilities will be available.
Tips for Creating an Effective Demo
Interactivity with the audience!
While proposed agendas may change, you should be as detailed in your agenda as possible. Illustrate the specific activities you have in mind to the best of your ability.
Make sure that you are explicit about what you want to get out of the Demo experience. As described above, Demos are meant for you (the presenter) to get exposure for your tool or to generate discussion. However, it is helpful for your reviewers to understand if you are looking to find users, vet future research directions, etc.
Demo Proposal Abstract
The abstract is the description of the Demo that will appear on the conference web pages. The description is limited to and must match verbatim the abstract section of the Demo Proposal. The Demo abstract must be submitted in plain text. The abstract for an accepted proposal may contain a URL with more information. (Abstracts of accepted Demos can be edited in response to reviews.)
Recall that since we expect virtual attendees in addition to on-site attendees, the proposal must clearly state how the Demo will be run on-site and either suggest a plan to accommodate remote attendees or explain why this would not be feasible.
Teaser Video Option
Independent of your Demo presentation, you may optionally provide a pre-recorded video with an overview of the Demo of at most 5 minutes in length. The video must be provided before the symposium starts and will be referenced from the online program in order to give attendees the chance to get acquainted with the Demo beforehand. It may also widen the potential audience for your Demo.
How Do I Submit My Demo?
Please be aware that the submission form asks you to provide demographic information. This demographic information is being collected by ACM; they created the questions and require them to be in the submission form. Please know that the demographic information submitted is not seen (and thus cannot be used in any way) by Technical Symposium reviewers or leadership. We also have no control over the questions asked nor where they appear in the form.
Submissions use the English language. If you desire editing services, consider the following from the ACM.
ACM has partnered with International Science Editing (ISE) to provide language editing services to ACM authors. ISE offers a comprehensive range of services for authors including standard and premium English language editing, as well as illustration and translation services. Editing services are at author expense and do not guarantee publication of a manuscript.
Prepare your Demo submission using the format specified above.
Recall that you will also need to copy-and-paste or type your text abstract description into a text box in the submission form. Be sure that the same text appears in the submission and in the abstract text box in the submission form.
Be sure to choose the appropriate topic areas when submitting. Your choices help in assigning appropriate reviewers to your submission, and assist the reviewers in evaluating the paper from an appropriate perspective.
Please enter between 3 and 7 topic choices. This will help match your submission with reviewers.
Convert your submission-ready paper into Adobe PDF format. Refer to our Creating Adobe PDF Documents page for assistance.
When you’re ready to submit, use the online submission system - EasyChair to complete the submission form and upload your submission. In addition to uploading the PDF version of your submission, you will fill out a form with metadata about your submission.
Please do not wait until the last minute to submit your documents because that is when everyone else will be connecting to our server!
Make note of the proposal ID number and password assigned to your submission. You will receive an email message confirmation. Spam filters sometimes trap these automatically generated messages so you may need to check your spam trap for the confirmation and later, acceptance or rejection notification.
After receiving confirmation, go to the submission site to review your submission for accuracy. Send email to the chair(s) (see below) if there are any problems.
If you have questions about anything discussed above, please contact:
Demos and Lightning Talks Team
- Carsten Kleiner
University of Applied Sciences & Arts Hannover
- Bedour Alshaigy
University of Aberdeen