Tutorial Proposals
Dates
October 16, 2000 for tutorial proposals.
December 1, 2000 for notification.
February 1, 2001 for final copy of two-page tutorial summary.
Goal
The ICSE tutorial program provides conference participants with the opportunity to gain new insights, knowledge, and skills in a broad range of areas of software engineering. Participants at the tutorials include software practitioners, managers, teachers, researchers, and students seeking to gain a better understanding of software engineering.
Scope
We are soliciting proposals for full-day (6-hour) or half-day (3-hour) tutorials. A tutorial can cover a wide range of topics, from practical techniques, guidelines, standards, and surveys, to theoretical issues. We encourage tutorials that reflect the conference themes and provide clear utility to practitioners. The topics are not limited to past ICSE tutorial offerings.
Tutorials are intended to provide independent instruction on a topic of relevance to software engineers. Therefore no commercial or sales-oriented presentations will be accepted. Potential presenters should keep in mind that there may be quite a varied audience, including novice graduate students, seasoned practitioners, and specialised researchers. They should be prepared to cope with this diversity unless they make clear that the tutorial is oriented to a particular subgroup. Also bear in mind that not everyone will have English as their first language. Thus, presenters should provide comprehensive notes written in clear, standard English. Idioms, irony, slang and culture-specific references should be avoided as far as possible.
Review Process
The tutorials comittee will evaluate each tutorial proposal on its anticipated benefit for prospective participants and its fit within the tutorial program as a whole. Factors to be considered also include: relevance, timeliness, importance, and audience appeal; suitability for presentation in a half- or full-day tutorial format; effectiveness of teaching methods; and past experience and qualifications of the instructors.
How to Submit
In brief, the tutorial proposal should include a title, proposer’s contact information, tutorial aims and objectives, duration (full- or half-day), purpose and scope, and summary of material to be covered.
The format of tutorial proposals (ten pages or fewer each) may be:
Submit proposals via e-mail to the address below.
Acceptance Notification
December 1, 2000 for notification.
Each accepted tutorial will have two pages for a summary in the conference proceedings. This summary must conform to the proceedings publication format. The final camera-ready copy and signed copyright release form are due February 1, 2001.
Send To
Gail Kaiser
Department of Computer Science
Columbia University
607 CEPSR
1214 Amsterdam Avenue, Mail Code 0401
New York, NY, USA
10027
Voice: +1-212-939-7081
Fax: +1-212-939-7084
E-mail: kaiser@cs.columbia.edu
