Note: All deadlines are 11:59PM (Apia Time) on the dates indicated. All submission deadlines are firm!
Check your local submission deadline with the World Clock.
2003 - deadline for tutorial proposals
15th December 2003 - notification
2nd February 2004 - deadline for final copy of two-page tutorial summary for conference proceedings
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.
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.
The tutorials committee 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 and brief bio, 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:
Proposals shopuld be submitted via email to the Tutorials Chair, Sebastian Uchitel at email@example.com
Notification will be given by December 15 2003.
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 2 2003.
Department of Computing,
Imperial College London,
180 Queen's Gate,
Imperial College London, UK
University of Buenos Aires, Argentina
Praxis Critical Systems, UK
University of L'Aquila, Italy
NASA Ames, US
Tokyo Institute of Technology, Japan
University of Oregon, US