The ICSE 97 Tutorials program provides conference participants with the opportunity to gain new insights, knowledge, and skills in a broad range of areas in the field of software engineering. Tutorial topics are expected to cover a wide range, from practical guidelines, standards, and surveys to academic and theoretical issues. The topics are not limited to past ICSE Tutorial offerings. Participants at tutorials include software professionals (developers, designers, testers, analysts, and managers), teachers and researchers in software engineering, and professionals in other areas seeking to gain a better understanding of how to apply software engineering technologies to their specialties.
Tutorials are intended to cover a wide range of topics. In the past they have included introductions and overviews of software engineering methods and processes, techniques for specific phases of the process, new methodologies, formal approaches, theoretical issues, different application areas, assessment approaches and techniques, requirements analysis techniques, design methodologies, user interface development software, multimedia, computer supported cooperative work and groupware, participatory design, teaching software engineering, software documentation, cost/benefit analysis, legal issues, and standards. Tutorials on these and other topics broadly related to software engineering are solicited. To broaden the scope of ICSE tutorials, topics of current interest to professionals (e.g. WWW authoring, Java applications, C++, CORBA, Windows NT) are especially encouraged.
There will be tutorials of different durations, different scopes, and for different experience levels.
Each tutorial is designed to be a half day or a full day in duration. Half-day tutorials are 3 hours long (not including breaks). Full-day tutorials are 6 hours long (not including breaks).
Tutorials will range in scope from survey of many topics to in-depth study of one or a few topics.
Each tutorial is designed for one of three audience experience levels:
Tutorial proposals will be evaluated on the basis of their estimated benefit for prospective participants and on their fit within the tutorials program as a whole. Factors to be considered include: relevance, timeliness, importance, and audience appeal; suitability for presentation in a half-day or full-day tutorial format; use of presentation methods that offer participants direct experience with the material being taught; and past experience and qualifications of the instructors. Selection is also based on the overall distribution of topics, approaches (overview, theory, methodology, how-to), audience experience levels, and specialties of the intended audiences. Thus, not all tutorials of technical merit can be accommodated within the tutorials program.
Submissions for ICSE 97 tutorials must include the following four documents:
Prepare a proposal, no longer than 10 pages, for review purposes. The proposal should be a clearly written specification of the tutorial. It should:
If the proposed tutorial has been given previously, the proposal should include a brief history of where the tutorial has been given and how it will be modified for ICSE 97. In addition, if the tutorial has been given at a previous ICSE, the proposal should tell how changes to the tutorial will address comments from previous attendees.
Prepare a two-page summary suitable for publication in the ICSE 97 Conference Proceedings. The summary should provide a descriptive statement of the content of the tutorial. It must be in the Conference Proceedings format, and must contain the title, authors, contact information, keywords, abstract, body, and references.
Prepare a description of the tutorial suitable for inclusion in the ICSE 97 Advance Program. It should guide potential participants in deciding whether to take the tutorial. The description should consist of four paragraphs, as follows:
Prepare a list of requirements for running the tutorial. Include any supplies required for each participant, restrictions or conditions on offering the tutorial, and other information that the review committee should know in considering the proposal.
Instructors will be notified of acceptance or rejection by the end of November 1996. Acceptance is conditional upon the instructors' compliance with deadlines and requirements.
Summaries of accepted tutorials will be published in the ICSE 97 Proceedings.
The primary instructor of each accepted tutorial will receive an Author Kit with detailed instructions on how to submit camera-ready and electronic materials for publication. These materials are due on 24 February 1997.
Instructors of accepted tutorials will also receive detailed format requirements for preparation of camera-ready versions of their tutorial notes. The notes are also due on 24 February 1997.
Instructors should prepare course material specifically for the ICSE 97 tutorial session. Presentation materials used by the instructor for other courses or projects must be reworked within the guidelines described in the Author Kit.
Attendees at previous ICSEs have indicated that the tutorial notes are a valuable benefit of taking a tutorial. Consequently, proposed tutorials are accepted contingent upon receipt of high-quality tutorial notes. The notes should serve as reference materials for attendees and should support the presentation of material during the tutorial. The tutorial notes should include:
Instructors must sign a release form giving ICSE 97 one-time only permission to utilize the notes for tutorial participants and to dispose of any surplus notes at the conference.
Please follow the steps in this checklist to ensure completeness of your submission.
Technical University of Vienna
Distributed Systems Department
A-1040 Vienna, Austria
Software Engineering Institute
Carnegie Mellon University
Pittsburgh, Pennsylvania 15213 USA