Tutorials

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.

Deadline

Topics

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.

Types of Tutorials: Duration and Audience Experience Level

There will be tutorials of different durations, different scopes, and for different experience levels.

Duration

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).

Scope

Tutorials will range in scope from survey of many topics to in-depth study of one or a few topics.

Audience experience levels

Each tutorial is designed for one of three audience experience levels:

Introductory:

Introductory level tutorials cover fundamental software engineering concepts, principles and techniques. Little previous background or knowledge is assumed.

Intermediate:

Intermediate level tutorials give deeper and more thorough treatment of a selected topic area. Some general background in one or more software engineering disciplines is assumed, but background in the topic area is not required.

Advanced:

Advanced level tutorials cover emerging developments from software engineering research or detailed treatment of a specific area. Background in the topic area is assumed.

Review Process

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.

Format

Submissions for ICSE 97 tutorials must include the following four documents:

• Proposal
• Conference Proceedings Summary
• Advance Program Description
• Requirements List

Proposal

Prepare a proposal, no longer than 10 pages, for review purposes. The proposal should be a clearly written specification of the tutorial. It should:

• Describe in detail the material that will be covered in the course.
• Justify the tutorial for an ICSE audience.
• Explain how the tutorial will be conducted.
• give a schedule of events with time allocations.
• Describe and provide samples of materials that will be included in the tutorial notes.

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.

Conference Proceedings Summary

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.

Advance Program Description

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:

• The content, duration (half day or full day), and scope (survey or in-depth) of the course.
• The key learning objectives for the participants (what specific knowledge each participant is expected to obtain).
• The intended audience of the tutorial (their specialties and experience level, plus any prior knowledge they will be assumed to have).
• The background of each instructor.

Requirements List

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.

Upon Acceptance

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.

Tutorial Notes

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:

• an introduction to the topic;
• copies of all overhead transparencies and slides;
• an annotated bibliography;
• copies of relevant background material or scholarly papers (for which the instructors have obtained any necessary reprint permission);
• tutorial exercises, as appropriate.

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.

Ground Rules

1. Your submission must be in English.
2. Electronic and fax submissions are not accepted.
3. Submissions which arrive after the deadline will not be considered.
4. Your submission should contain no proprietary or confidential material and should cite no proprietary or confidential publications. Your submission should not be a demonstration of a commercial product.
5. Responsibility for permissions to use video, audio or pictures of identifiable people rests with you, not ICSE 97.
6. If your submission is accepted, it will not be published without copyright release forms signed by the first-listed author and representative of the first author's institution.
7. We strongly suggest the use of express mail or a courier service, for speedy delivery. Customs labels should bear the words "Educational materials with no commercial value."

Checklist

Please follow the steps in this checklist to ensure completeness of your submission.

1. Read the Invitation To Submit.
2. Fill out Cover Pages One and Two.
3. Prepare a Proposal for review, as described above.
4. Prepare a Conference Companion Summary (two pages) in the Conference Proceedings format for publication, as described above.
5. Prepare an Advance Program Description, as described above.
6. Prepare a Requirements List, as described above.
7. Collect Cover Pages One and Two, and the Proposal, in the order given, in a packet, and make six copies of the packet. Use 8.5 x 11 inch or A4 paper.
8. Make sure each copy of the packet is STAPLED, not loose or held by clips.
9. You may include an email address for acknowledgement of receipt of your submission.
10. Send the 5 copies of your submission packet, and the reply postcard, to one of the Tutorials Co-Chairs at the Send To address shown below.

Send To

Mehdi Jazayeri
Technical University of Vienna
Distributed Systems Department
Argentinierstrasse 8/184-1
A-1040 Vienna, Austria

E-mail: m.jazayeri@infosys.tuwien.ac.at
Tel: +43-1-58801-4470
Fax: +43-1-505-8453

or

Patricia Oberndorf
Software Engineering Institute
Carnegie Mellon University
Pittsburgh, Pennsylvania 15213 USA

E-mail: po@sei.cmu.edu
Tel: +1-412-268-6138
Fax: +1-412-268-5758

For more information