Information about Proceedings --- ICSE 2001 PROCEEDINGS LAYOUT We used the following layout for the ICSE 2001 proceedings: Cover (front): usual ICSE cover specialized for colors and location Cover (back): blank Title page (front): page i but not numbered Copyright info (back of title page): page ii but not numbered Real title page with affiliates (front): page iii and numbered There will be logos for sponsorship (IEEE CS, ACM, etc.) There will be a list of corporate sponsors under the title (see ICSE 20, Japan) for sample Real title page (back): blank; page iv but not numbered Table of Contents: starts on page v and is numbered accordingly; for the rest of the discussion, assume that the TOC is t pages Forward (our letter; one letter for genera, program chairs) Organizing Committees Invited Presentations Technical Papers Education Papers Case Study Papers Panels Doctoral Symposium Formal Research Demos Frontiers of Software Practice Challenges of Software Engineering Industry Presentations Workshop Summaries Tutorial Summaries Author Index Ads from IEEE and ACM (one page each) Notes pages: 3-4 of these HOW THESE ITEMS ARE COLLECTED For ICSE 2001, - The proceedings editor, Anne Jacobs, collected all materials. - Shortly after the Program Committee and Conference meetings, which were held in November 2000 in San Diego, we provided a complete author list to Anne Jacobs. - For the next three months, we continued to update, correct, and supply information, abstracts, etc. to Anne for the proceedings - Each of us read the proceedings drafts a number of times before the proceedings went to print; even if you have the best proc editor, this is essential because the editor doesn't know the conference, the acronyms, the authors, etc. - The people contributing to the proceedings need to know in advance that they will be expected to contribute to the proceedings. Here is how we made arrangements for getting the information, collecting it, etc. for ICSE 2001. Forward: Hausi, Mary Jean, and Wilhelm wrote the letter and submitted it to Anne Jacobs Organizing Committee: Kenny Wong provided this information to Anne Jacobs since he had it from the web site. Session Title Page for "Invited Presentation": This is page 1 of the proceedings. Abstracts of Invited Sessions: These was one page for the abstract of each of the five talks (and a paper from one of the speakers). - We asked the speakers to submit an abstract and a bio and we included it in the proceedings. - One of the speakers asked for room for a paper, which we were happy to include. - We reviewed and revised the abstracts submitted by the speakers. For one of the speakers, we wrote the abstract, and asked for approval. - Getting abstracts from some speakers was one of the most difficult tasks - Hausi organized this task, and provided the abstracts to Anne Jacobs Paper Sessions (Technical, Education, Case Studies) Track Title Page for "Technical Papers": Session Title Page for "Design and Specification of Distributed Systems": Technical papers in this session: 3 x 10 or 30 pages (approx). Session Title Page for "Static Analysis": Technical papers in this session: 3 x 10 or 30 pages (approx). ... Session Title Page for "Architectures for Emerging Applications" Technical papers in this session: 3 x 10 or 30 pages (approx). Track Title Page for "Education Papers": Session Title Page for "Practical Software Engineering Education" Education papers in this session: 3 x 10 or 30 pages (approx). Session Title Page for "Where Are We Now and Where Could We Go? A Status Report on the First Annual Survey for International Academic Software Engineering Programs" Education papers in this session: 3 x 10 or 30 pages (approx). Track Title Page for "Case Study Reports": Session Title Page for "Infrastructure Support" Case Study reports in this session: 3 x 10 or 30 pages (approx). ... Session Title Page for "Reengineering of Object-Oriented Systems via Duplication Analysis" Case Study reports in this session: 3 x 10 or 30 pages (approx). ... - As expected, the technical, education, and case-study papers were the least troublesome to collect - Anne Jacobs collected them from the authors Panels Track Title Page for "Panels" Panel summaries: 4 x 4 or 16 pages (approx). Panel organizers will collect and organize the summaries - We had to contact the panel organizers a number of times to get the finalized list of panelists and the panel summaries - Anne Jacobs collected the organized summaries for the panels from the panel organizers Doctoral Symposium Track Title Page for "Doctoral Symposium" Doctoral summary: One page summary of symposium (optional; up to the Doc Symp chair) Doctoral abstracts: 10 x 2 or 20 pages - the requirement to write abstracts was included in the call for participation information, and should be a requirement for participation - Anne Jacobs collected these abstracts from the participants Formal Research Demos Track Title Page for "Formal Research Demos" Formal Research Demo papers: 9 x 2 or 18 pages - these were reviewed papers, so they weren't difficult to collect - Anne Jacobs collected them from the authors FoSP Track Track Title Page for "Frontiers of Software Practice" FoSP abstracts: 8 x 1 - we had a difficult time collecting this information because there was no incentive to provide it beforehand - Scott collected it and provided it to Anne Jacobs CHASE Track Track Title Page for "Challenges and Achievements in Software Engineering" CHASE summaries: 2 x 2 or 4 pages - Gregor collected and organized these summaries and provided them to Anne Jacobs Invited Industry Presentations Track Title Page for "Invited Industry Presentations" Invited Industry Presentations summaries: 9 x 1 or 9 pages - these were the most difficult to collect because, like the FoSP, there is no incentive to provide materials for the proceedings - Hausi collected these materials and provided them to Anne Jacobs Workshop and Tutorial Summaries Track Title Page for "Workshops Summaries": Workshop Summaries: 16 x 2 or 32 pages (authors will prepare and submit) Track Title Page for "Tutorial Summaries": Tutorial Summaries: 22 x 2 or 44 pages (authors will prepare and submit) - Hausi added a clause in the contract that for Workshop organizers and tutors that required them to submit these summaries - Anne Jacobs collected these from the organizers or tutors Author Index: Notes Pages: 3-4 pages Note about collecting materials: - We provided author information to Anne Jacobs shortly after the Program Committee and Conference meetings in San Diego - We also provided letters for the author kits - We provided letters for two author kits---one for those who had to sign a copyright and one for those who didn't.