Helsinki, Finland, September 1-5, 2003
Call for Papers
The deadline for tutorial proposals has passed!
Call for Proposals for Tutorials
to be held in conjunction with
9th European Software Engineering Conference (ESEC)
|Tutorial proposals due||March 15, 2003|
|Notification||May 25, 2003|
|Final material||July 31, 2003|
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.
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 specialized 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 much as possible.
Review process. Tutorial proposals will be evaluated for their presumed benefit to prospective participants to ESEC/FSE 2003, and how well they 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.
Submissions must be no longer than 10 pages. A proposal should include a description of the theme of the tutorial and a justification of its relevance for ESEC/FSE 2003. It should also include information about the duration, scope, key learning objectives for the participants, intended audience, and required background.
How to submit. The tutorial proposal should include a title, proposers contact information, tutorial aims and objectives, duration (full- or half-day), purpose and scope, and summary of material to be covered.
The preferred format of tutorial proposals (ten pages or fewer each) is Adobe Portable Document Format (PDF).
Submit proposals via e-mail to the Tutorial Co-Chair:
Computer Science Department (SAL 338)
University of Southern California
Los Angeles, CA 90089-0781
Phone +1 213 740 5579
e-mail: 'neno@usc edu' (replace spaces with dots)