Categories
Original submissions in all areas related to the conference theme
are invited for the following categories:
We particularly encourage contributions along the following lines:
- The use of technology in supporting computer science teaching
and learning: This might include intelligent tutoring systems,
visualization, mobile computing, distance education, electronic
forms of classroom support, or web-based tools.
- The practice of teaching computer science: Submissions here
might cover such topics as curricular issues, teaching material
or aids, or innovative instructional methods. Qualitative work
is encouraged, but it should not be merely anecdotal or descriptive.
- Computer science education research: Submissions in this area
will involve research evidence or the use of theory to inform
pedagogy.
Author Information
All submissions must be original work.
The official language of the conference is English. Submissions
should use clear, ordinary grammar and avoid the use of colloquialisms
that might be difficult for those who speak English as a second
language.
Note that reviewers will assume they are reviewing completed works,
as they will eventually appear in the conference proceedings. Do
not submit incomplete drafts.
All submissions should be in Rich Text Format (RTF). To submit
your work, visit the
online submission web site. There you will find a submission
form that will require you to enter the type, title, topic and URL
of your submission, plus author contact information.
If accepted, final papers, panel abstracts, poster abstracts, demo
abstracts and tips & techniques summaries must be submitted
in camera-ready format, electronically, as RTF files. Camera-ready
submissions will be formatted for 8.5 x 11 inch (22 x 28 cm) paper
using 9 pt Times Roman (or similar) font, single-spaced, double
columns, justified, with 1 inch (2.5 cm) top and bottom margins
and 0.75 inch (1.9 cm) side margins.
Note that you may use the
ACM templates as a guideline, but remember to covert your paper
to RTF format for submission.
For more information, contact the program co-chair: Ian Utting
(email-link).
Papers
All papers should be high quality, unpublished, original work related
to the themes of the conference.
We are again expecting all paper submissions to be full papers.
They are limited to five pages (note that previous years' limit
has been four).
Author identification must be concealed in paper submissions to
allow for a blind review process.
Papers will be reviewed and, if accepted, presented at the conference
by one or more of the authors. Paper presentations last twenty minutes
(including q/a).
All accepted papers will be published in the conference proceedings.
Authors must sign the ACM copyright release form before publication.
The deadline for paper submission is November 13, 2001. For more
information, contact one of the program co-chairs: Ian Utting (email-link)
and Don Goelman (email-link).
Submission
of paper.
Panels
Panel sessions provide a forum for the exploration of a "hot topic"
among expert panel members and between the panel and the audience.
A panel abstract is limited to two (2) pages. It should contain
the following information, in this order: panel title, panel organizer
information (name, affiliation, address, email, phone), panelist
information (name, affiliation, email) for each panelist, and panel
description.
The panel description should include an introduction to the panel
topic and a short position statement from each panelist.
The panel organizer must select appropriate panelists who will
make a commitment to participate. The panel organizer is responsible
for obtaining position statements from panelists and integrating
them into the abstract before submitting the proposal.
All accepted panel abstracts will be published in the conference
proceedings.
The deadline for panel proposals is November 13, 2001. For more
information, contact one of the program co-chairs: Ian Utting (email-link)
and Don Goelman (email-link).
Submission
of panel proposals.
Working Groups
Several working groups will convene during ITiCSE 2002. A working
group will consist of five to ten people who share a common interest
related to the themes of the conference, selected on the basis of
their qualifications in the area.
Working groups will begin work by electronic communication two
months before the conference. The working groups will meet at the
conference site for the two days before the conference and throughout
the conference. Each working group will determine its own meeting
schedule. Intermediate working group results will be presented to
all conference attendees at a conference session. By the end of
the conference each working group will have produced a robust draft
of a report.
Within four weeks the groups will submit a polished version of
the report, which will be reviewed and edited under the supervision
of the working group coordinator. Suitable reports will be published
in the SIGCSE Bulletin and become part of the ACM Digital Library.
To apply to lead a working group, create a proposal describing
the topic you wish to address, what you expect the group to produce,
and information on your experience in the area. You may also include
a list of potential working group members. Proposals should be 2
to 4 pages in length.
Established communities are especially encouraged to form a working
group at ITiCSE to both bring their members together for intensive
work and to introduce the work to others who may be interested.
The deadline for working group proposals is November 13, 2001.
For more information, contact the working group chair: Joe Bergin
(email-link).
Submission
of working group proposal
Tutorials
Proposals for tutorials that provide in-depth coverage of a topic
of interest to computing educators are invited.
A tutorial should be designed to be a thorough and comprehensive
exploration of the topic. Each tutorial is classified as either
half-day (three hours) or full-day (seven hours) and will be held
the day before or the day after the conference.
There is an additional fee for a symposium attendee to participate
in a tutorial.
Tutorial presenters will earn two night's accommodation at a conference
hotel.
A tutorial proposal is limited to two (2) pages. It should contain
the following information, in this order: tutorial title, tutorial
organizer information (name, affiliation, address, email, phone),
tutorial category (half-day or full-day), and tutorial description.
The tutorial description should provide an introduction to the
topic, a description of the tutorial activities, the background
of the presenter, and a separate paragraph (max 60 words) for publication
that serves as a succinct description of the tutorial for symposium
attendees.
You must also specify all equipment needed to conduct the tutorial
(some instructional laboratories may be available). A list of tutorial
titles and presenters will be published in the conference proceedings.
The deadline for tutorial proposals is November 13, 2001. For more
information, contact the tutorial chair: Bruce Klein (email-link).
Submission
of proposals for tutorials.
Tips & Techniques
ITiCSE attendees have many valuable ideas to share about practical
educational approaches that work well for them - a particular assignment,
a method of assessment, a class activity, a pedagogical tool. Such
ideas may not warrant a full paper at the conference. Therefore,
in order to make them available for the entire community, the ITiCSE
program includes, for the third consecutive year, our popular Tips
& Techniques session(s). They consist of short presentations
(10 minutes), each of which explains the goal, the application,
and the results of a particular tip or technique. Each idea will
be supported by a one-page summary that will appear in the proceedings.
The summary should include a title, presenter information (name,
affiliation, address, email, and phone), a description of the idea
to be presented, and if appropriate, a URL where further information
or materials are available.
The deadline for tips & techniques summaries is February 15,
2002. For more information, contact the tips & techniques chair:
Michael Kölling.
Submission
of tips & techniques summary.
Posters
Works in progress may be submitted for presentation in poster format
at the conference. Each poster will be supported by a half-page
abstract that will appear in the proceedings.
The abstract should include a title, presenter information (name,
affiliation,
address, email, phone), and a description of the poster topic and
contents.
Presentation guidelines will be sent to authors upon acceptance.
The deadline for poster abstracts is February 15, 2002. For more
information, contact the poster chair: Mats Daniels (email-link).
Submission
of poster abstract.
Demonstrations
This year we are formally soliciting demonstrations. Consider demonstrating
the software you use in your classrooms and labs to support your
delivery of computer science education. Demonstrations could be
used by paper authors who do not have enough time during their 20-minute
paper presentation to fully demonstrate support software. Demonstrations
will be presented along with posters.
Presenters must supply their own equipment - at this time we are
promising electrical outlets only. As we get closer to the conference
we may be able to offer more facilities. Please come back to check
for updates on this situation.
Each demonstration will be supported by a half-page abstract that
will appear in the proceedings. This should include a title, presenter
information (name, affiliation, address, email, phone), and a description
of the demonstration topic and contents.
The deadline for demonstration abstracts is February 15, 2002.
For more information, contact the demonstration chair: Mats Daniels
(email-link).
Submission
of demonstration abstract.
Note that we will be accepting on-site demonstration applications,
but those demonstrations obviously will not receive any space in
the program or proceedings.