============================================================================ ICSE 97 - International Conference on Software Engineering Pulling Together CALL FOR PARTICIPATION THIS CALL FOR PARTICIPATION IS AVAILABLE ELECTRONICALLY VIA: World Wide Web: http://www.ics.uci.edu/icse97/ Anonymous FTP: ftp://www.ics.uci.edu/pub/icse97/ ---------------------------------------------------------------------------- Boston, Massachusetts, USA May 18-23, 1997 Sponsored by ACM Special Interest Group on Software Engineering (SIGSOFT) and IEEE Computer Society - Technical Council on Software Engineering (TCSE) In cooperation with CEPIS (Council of European Professional Informatics Societies) ============================================================================ Pulling Together: ICSE 97 Boston, Massachusetts, USA May 18-23, 1997 The creation, deployment, evolution, and meaning of software and its role in modern society is changing and expanding as a result of new technologies, new applications, and new social factors. The Internet, the World-Wide-Web, multimedia interfaces, and neighborhood software stores have added new dimensions to traditional issues and topics in software engineering. The International Conference on Software Engineering is changing with the discipline to encompass the new emphases and the broadened sweep of topics and concerns which confront today's software professionals and researchers. The theme of the 1997 International Conference on Software Engineering is "Pulling Together." Pulling together denotes coordinated action of many individuals in achieving a common goal. It also describes the coming together of many different perspectives, concerns, and abilities to find a common ground and a way of achieving cooperation. Pulling together is fundamentally dynamic in nature, and is often a matter of explicit negotiation and communication. Major changes have been instituted in ICSE 97 to help the software engineering community pull together, in the full sense of that phrase. ICSE 97 includes a widened range of conference activities, a widened range of participants, and new technical areas. A broadened outlook challenges old beliefs, promotes new ideas and new synergies, and provides for a dynamic, exciting program. New or expanded conference activities include a doctoral symposium, lessons and reports from software engineering organizations, a mentor program, posters, and a commercial exhibit. A major addition to the conference is a suite of sessions and activities focusing on the interests and needs of the practicing professional. Numerous invited presentations, timely panel topics, experience reports, and an expanded tutorial program are included. As the discipline expands, papers and presentations on topics such as software engineering and the WWW, end-user involvement in software development and customization, usability testing, design for an international marketplace, and intelligent applications are encouraged. We hope that you will pull together with us, bringing new ideas, new concerns, and new goals, thus helping us to find common ground and reach new objectives. Alfonso Fuggetta, Richard N. Taylor, Anthony I. Wasserman ICSE 97 Program Coordinators ============================================================================= ICSE 97 --- INVITATION TO SUBMIT/CHOOSING A SUBMISSION CATEGORY The annual International Conference on Software Engineering (ICSE) is the leading forum for the exchange of ideas on all aspects of software engineering. ICSE 97 invites you to submit work to share with the ICSE community. Different classes of contributions are sought, ranging from research papers to lessons and status reports from software engineering organizations. The ultimate goal is to build a rich and comprehensive conference program that can fit the interests and needs of different classes of attendees: professionals, researchers, managers, and students. SUBMISSIONS AT A GLANCE: TECHNICAL PROGRAM ----------------------------------------------------------------------------- PARTICIPATION CATEGORY DEADLINE ----------------------------------------------------------------------------- Workshops: Discuss focused topic in a small-group setting 15 May 1996 Papers: Report research or practical experiences 2 August 1996 (electronic abstract), 9 August 1996 (full paper due) Panels: Discuss and debate pressing issues 2 August 1996 Tutorials: Teach Software Engineering techniques and theory 2 August 1996 Software Engineering in Organizations: Lessons and Status Reports Summaries of work taking place in institutions, organizations, or groups 16 September 1996 Research Demonstrations: Present demo of research tools 1 November 1996 Doctoral Consortium: Ph.D. students share their work 1 November 1996 Posters: Present late-breaking results and ongoing work 15 February 1997 ========================================================================= For information on topics, submission categories, and programme organization contact the program coordinators at the following addresses: Alfonso Fuggetta Dipartimento di Elettronica e Informazione Politecnico di Milano P.za Leonardo da Vinci, 32 20133 Milano, Italy fuggetta@elet.polimi.it +39-2-2399-3540 +39-2-2399-3411 (fax) http://www.elet.polimi.it/~fuggetta/ Richard N. Taylor Information and Computer Science University of California, Irvine Irvine, California, 92697-3425 U.S.A. taylor@ics.uci.edu +1-714-824-6429 +1-714-824-4056 (fax) http://www.ics.uci.edu/~taylor/ Anthony I. Wasserman tonyw@methods-tools.com ========================================================================= ========================================================================= REGISTRATION The ICSE 97 Advance Program, which contains conference registration materials, will be mailed in January, 1997 to members of ACM/SIGSOFT, IEEE Computer Society TCSE, and cooperating societies. To request additional copies of the Advance Program, contact the ICSE 97 Conference Office. Early registration discounts will apply to registrations received on or before 15 March 1997. ELECTRONIC CALL FOR PARTICIPATION The Call for Participation is available electronically via * anonymous ftp to www.ics.uci.edu; change directory to pub/icse97/cfp.txt * World Wide Web: http://www.ics.uci.edu/icse97/cfp.html ICSE 97 CONFERENCE OFFICE For general conference information contact: ICSE 97 Department of Computer Science 307 Lederle Graduate Research Center PO Box 34610 University of Massachusetts, Amherst Amherst, MA 01003-4610 USA +1-413-545-2475 +1-413-545-3729 (fax) icse-97@cs.umass.edu W. Richards Adrion ICSE 97 General Chair Alfonso Fuggetta, Richard N. Taylor, Anthony I. Wasserman ICSE 97 Program Coordinators ========================================================================= INVITATION TO SUBMIT * CHOOSING A SUBMISSION CATEGORY PROGRAM COORDINATORS Alfonso Fuggetta Dipartimento di Elettronica e Informazione Politecnico di Milano P.za Leonardo da Vinci, 32 20133 Milano, Italy fuggetta@elet.polimi.it +39-2-2399-3540 +39-2-2399-3411 (fax) http://www.elet.polimi.it/~fuggetta/ Richard N. Taylor Information and Computer Science University of California, Irvine Irvine, CA 92717-3425 USA taylor@ics.uci.edu +1-714-824-6429 +1-714-824-4056 (fax) http://www.ics.uci.edu/~taylor/ Anthony I. Wasserman IDE 595 Market Street, 12th floor San Francisco, CA 94105 USA tonyw@ide.com +1-415-543-0900 +1-415-543-0145 (fax) http://www.ide.com/Bios/Wasserman.html PROGRAM COMMITTEE (PAPERS) Guillermo Arango (USA) David Barstow (USA) Don Batory (USA) Marty Cagan (USA) Aniello Cimitile (Italy) Bruce Croft (USA) Michael Cusumano (USA) Jean-Claude Derniame (France) Laurie Dillon (USA) David Eichmann (USA) Jacky Estublier (France) Herm Fischer (USA) Kokichi Futatsugi (Japan) John Gannon (USA) David Garlan (USA) Marie-Claude Gaudel (France) Sol Greenspan (USA) William Griswold (USA) Jonathan Grudin (USA) Mehdi Harandi (USA) Mary Jean Harrold (USA) Ellen Isaacs (USA) Paola Inverardi (Italy) Matthias Jarke (Germany) Ross Jeffery (Australia) Takuya Katayama (Japan) Richard Kemmerer (USA) Jeffrey Kramer (UK) Mark Linton (USA) Bev Littlewood (UK) Tom Maibaum (UK) John McHugh (USA) Mark Moriconi (USA) John Mylopoulos (Canada) Oscar Nierstrasz (Switzerland) David Notkin (USA) Dewayne Perry (USA) Mauro Pezzé (Italy) Adam Porter (USA) David Rosenblum (USA) Will Tracz (USA) Axel van Lamsweerde (Belgium) Lawrence Votta (USA) Bruce Waddington (USA) Brian Warboys (UK) Martin Wirsing (Germany) Alexander Wolf (USA) PROFESSIONAL TRACK COMMITTEE Anne Duncan, Digital Equipment Corporation (USA) John Favaro, Intecs (Italy) Joe Keller, SunSoft (USA) Mary E.S. Loomis Hewlett-Packard (USA) Ann Miller, Motorola (USA) Marie Silverthorn Texas Instruments (USA) John Swainson IBM Canada Ltd. (Canada) Ed Weller, Bull (USA) FOR MORE INFORMATION To contact the Program Coordinators send e-mail to icse-97-program@ics.uci.edu The annual International Conference on Software Engineering (ICSE) is the leading forum for the exchange of ideas on all aspects of software engineering. ICSE 97 invites you to submit work to share with the ICSE community. Different classes of contributions are sought, ranging from research papers to lessons and status reports from software engineering organizations. The ultimate goal is to build a rich and comprehensive conference program that can fit the interests and needs of different classes of attendees: professionals, researchers, managers, and students. CHOOSING A PARTICIPATION CATEGORY If you are unsure of which category to submit to, please consult the Program Coordinators or the Co-chairs in charge of specific events you may be interested in. MULTIPLE AND RELATED SUBMISSIONS You may prepare as many submissions as you like in the same or different categories. In a given category, materials should be presented only once. Submitted papers must not have been previously published or be currently under consideration for publication outside of ICSE 97. REACHING THE ENTIRE SOFTWARE ENGINEERING COMMUNITY ICSE 97 encourages participation from the entire Software Engineering community in the following ways: * International Relations Co-Chairs represent ICSE communities from America, Asia, Australasia, and Europe and may be contacted to obtain more information on any aspect of participation in the Conference. * Conference committees are composed of individuals from a variety of countries and disciplines. * Mentoring is available (see page 1). * Guides to successful submission and answers to frequently asked questions are available. Please see individual submission categories for details on where to find this information. * For the Technical Program, the technical merit of submissions is more important than the quality of the English used in the submission. However, the quality of English may be a key determinant in a paper's acceptance: the better your English is, the more readily your ideas communicate. Submitters are encouraged to find a native speaker of English to help edit the submission or ask for an ICSE mentor. LANGUAGE OF THE CONFERENCE In keeping with the international character of ICSE 97, the written and spoken language of the conference is English. QUALITY For an ICSE submission to be accepted you must say something significant. All submissions should address the following: Content * State your message clearly. * What methods did you use and why? * What are your findings or what are the issues? Be specific regarding the status of any software systems discussed. * Review the literature carefully. Please read and cite relevant material from previous ICSE Proceedings, journals, and other conference proceedings. * Identify the innovative aspects of your work clearly. Consequences * What should the audience do differently if and when they have accepted your message? * What are the directions for future work based on your work? REVIEW PROCESS All submissions will be reviewed by the technical area Co-Chairs and their committees. Submissions will be evaluated according to accepted ICSE standards of excellence. If you have questions about these standards, please see information in the individual submission categories, retrieve the additional electronic documents mentioned there, or contact one of the Co-Chairs. If you need further help, please request an ICSE mentor. PUBLICATION: CONFERENCE PROCEEDINGS Accepted papers and other material (see details in the various participation categories) will be published in the ICSE 97 Conference Proceedings. The Proceedings is a citable archival source: it will have an ISBN number and will be available for sale through the ACM and the IEEE Computer Society. ICSE MENTORING Every year ICSE submissions from people unfamiliar with the ICSE community are rejected because authors do not understand the expectations for an ICSE submission. We are consequently missing many interesting viewpoints. If you are not familiar with how to write a good ICSE submission, please ask for a mentor. A mentor is a person who helps you learn something unfamiliar through a personal one-on-one relationship. Ask for a mentor by contacting one of the Program Coordinators through electronic mail, fax, or phone. If you want to ask for a mentor we will need to hear from you no later than 10 weeks prior to the submission deadline for the chosen category. We highly recommend that you request a mentor even earlier. You may need a mentor to help you choose a submission category, or to help you figure out how to prepare your submission, or both. The mentor does not prepare the submission for you but helps you do a better job of it yourself. The mentor addresses questions such as, but not limited to: * Are the issues addressed relevant to the ICSE community? How could the work be made more relevant? * Is the work adequately related to and differentiated from other relevant work that ICSE community members are likely to be familiar with? * Is the information given about methodology and results at the right level of detail and rigor for an ICSE audience? We expect mentoring will be most useful for participants that have not traditionally contributed to ICSE (e.g., from a particular application domain). However, mentoring is available to any submitter on a first come, first serve basis. Please note that there are no guarantees that participating in this program will ensure that your submission will be accepted by the review committee. The mentoring process is completely independent of the review process. The mentor does not become a co-author. The mentor need not appear in the acknowledgments of an accepted submission, as mentoring is a private matter between mentor and submitter. In the Proceedings, we will have a page listing those who mentored to acknowledge their contribution, but acknowledgment is completely separate from an individual submission. We have limited resources (volunteers) available, so mentors will be assigned on a first come, first served basis. Act early, since the feedback given by the mentor may suggest extensive modifications to the submission, which cannot easily be done at the last minute. Mentoring is available to submitters in all participation categories covered in this Call for Participation. INTERNATIONAL RELATIONS CO-CHAIRS Will Tracz - Americas Loral Federal Systems 1801 State Route 17C, M/S 0210 Owego, CA 13827-3998 USA tracz@lfs.loral.com +1-607-751-2169 +1-607-751-6025 (fax) Koji Torii - Japan/Asia Nara Institute of Science and Technology Graduate School of Information Science 8916-5, Takayama, Ikoma, Nara 630-01 Japan torii@is.aist-nara.ac.jp +81-7347-2-5310 +81-7347-2-5319 (fax) Chris Marlin - Australia/New Zealand Flinders University GPO Box 2100 Adelaide 5001 Australia marlin@cs.flinders.edu.au +61-8-201 2662 +61-8-201 3626 (fax) Nazim Madhavji - Canada Canada School of Computer Science McGill University 3480 University Street Montreal, Quebec, Canada H3A 2A7 madhavji@cs.mcgill.ca (514)-398-3740 (514) 398-3883 (fax) Michel Lemoine - Europe CERT/ONERA-DERI 2, Ave. E. Berlin 31055 Toulouse CEDEX France Michel.Lemoine@cert.fr +33-62-25-26-45 +33-62-25-25-93 (fax) TOPIC AREAS ICSE 97 encourages submissions from the many perspectives that contribute to the whole of Software Engineering. We particularly encourage papers addressing topics wherein software engineering issues play a key role, but where those topics have not been highlighted in previous ICSEs. We encourage discussions of both the process and outcome of research, design, engineering, development, installation, use, and maintenance. Examples include: Requirements engineering. Acquisition, modeling, specification, prototyping, and analysis requirements. Software architectures. Domain-specific software architectures, evaluation of architectures, architecture description languages, supporting environments, architecture development approaches, and marketplace issues. Issues with specific architectural styles, such as client-server, event-based, and blackboard architectures. Development of architectures. Hypermedia. Establishing and navigating links among disparate artifacts. Use of hypermedia in software development and evolution. Configuration management of hyperwebs used to support software evolution. Navigation paradigms. Design. Design methods and strategies, languages, and evaluation of designs. Design patterns. Reuse. Technologies, tools, and strategies for developing reusable software. Issues in changing organizations to support and reward reuse. Legal issues. Object oriented technology and patterns. Development and specification of interfaces, encapsulation issues, changing the interfaces over time, adapting components. Codification and regularization of standard solutions to typical problems. Programming languages and software engineering. Language issues in component description and implementation. Dynamic components. Generic components. Language issues in system evolution. Language issues in software deployment (á la Java). Knowledge-based approaches. Applications of automated reasoning, knowledge representation, and artificial intelligence techniques to software engineering problems. Techniques may be fully automatic, may support, or may cooperate with humans. Information retrieval, digital libraries, and information systems design. Software engineering issues inthe construction or use of information retrieval systems and digital libraries, including issues of filtering, routing, and integration with other aspects of an enterprise's computing. Mobile computing and mobile applications. Design issues, dynamic languages and application architectures, quality assurance, configuration management, deployment, and operations management. Reliability. Development of operational profiles. Reliability models. Assessment of value. Formal methods. Formal approaches to specification; Information retrieval, digital libraries, and information systems design. Software engineering issues in the construction or use of information retrieval systems and digital libraries, including issues of filtering, routing, and integration with other aspects of an enterprise's computing. Testing, analysis, and verification. Algorithms, techniques, and processes concerned with assuring, developing, or assessing software with respect to requirements or goals. development, analysis, and testing. Reverse engineering and program transformation. Incremental approaches to dealing with legacy software. Environments: organization and integration principles. Object management support, language-directed tools. Software process: modeling, analysis, execution, evolution. Formalisms and support tools. Integration with environments. Empirical evaluations, identification of processes through empirical means. Process improvement. Strategies, approaches, and experiences in enhancing organizations' corporate abilities. Process assessment strategies. Demonstration of benefits. Workflow, computer supported cooperative work (CSCW) and software engineering. Supporting and coordingating teams of software engineers. Workflow and process specification and execution. Project management. The relationship of organizational structure to product characteristics. Tools for management support. Team restructuring, and relation to software processes and process technology. Measurement, metrics, experimentation. Integration of metrics gathering and evaluation into processes. Experimental paradigms for software research. Integration of multiple metrics. Special techniques for information systems design. Distributed and parallel systems. Special software requirements, design issues, and real-time and safety-critical systems. Software documentation. Documentation in an era of the Web and multimedia. Video and audio documentation. Information retrieval issues and approaches to software documentation. Application of artificial intelligence techniques. Design environments, evaluation agents, knowledge-based approaches. Human-computer interaction (HCI). The role and relation of HCI research to requirements engineering, usability assessment. User involvement in system specification, design, and implementation. Ethnographic studies and software development. Technology transfer, education. Software engineering curriculum design. Teaching issues of large-scale systems in the classroom. Standards and legal issues. De facto and unofficial "standards". Evolution of standards in a highly dynamic world. Standards formation processes. Recent and influential standards from OMG and others. Interoperability. Between languages, frameworks, platforms, components, processes, object repositories, and environments. Module interconnection languages. MILs and rapid prototyping. MILs and software architecture research. Configuration management. Version control and system evolution. Integration of configuration management tools with environments. ========================================================================= INVITATION TO EXHIBIT EXHIBITION MANAGEMENT Danieli & O'Keefe Associates, Inc. CONTACT Susan Hines Danieli & O'Keefe Associates, Inc. 490 Boston Post Road Sudbury, MA 01776 USA Expo_sales.DOK@notes.compuserve.com +1-508-443-3330, extension 1227 +1-508-443-4715 (fax) DEADLINE 1 January 1997 Late registrations will be handled on a space-available basis after the deadline. For twenty-five years, the International Conference on Software Engineering has been the premier conference inthe field. Drawing an average of over 1000 participants when held in the U.S., ICSE showcases state-of-the-art technologies and attracts both researchers and software practitioners. ICSE 97 includes a widened range of conference activities, a widened range of participants, and new technical areas. ICSE 97 is expanding its commitment to practitioners by offering commercial exhibit space to vendors. Take this opportunity to reach the broad segment of the software engineering community represented by ICSE 97 attendees by exhibiting your products and services at the conference. DETAILS Applications for exhibit space will be accepted on a first come, first served basis. While the exhibition is new to ICSE, interest has been high, so prompt registration is recommended. The ICSE 97 Exhibition is intended for commercial vendors of products and services of interest to the software engineering community. Academic, government, non-profit and industrial research laboratories may apply to be included in the Research Demonstrations track (see page 8). The ICSE 97 Program Coordinators reserve the right to determine eligibility for the Research Demonstration track. In addition to booth space, each exhibitor receives the following benefits: * One full conference pass at a reduced rate * A complete list of registered conference attendees, including title and address * Exhibitors that sign up prior to 15 November 1996 will be included in the advance program, which is mailed to over 20,000 potential attendees EXHIBIT SPACE All commercial exhibit space is sold in increments of 10' x 10'. Space rental rate is $2000 per 10' x 10' booth, prior to 1 January 1997. After 1 January, the rate increases to $2100 per booth. Questions should be directed to the exhibition management at (508) 443-3330, extension 1227. Cancellations of space will be assessed a $200 fee if cancellation is received in writing by 1 January 1997. Thereafter, no refunds will be provided for unoccupied space; space may not be sublet. For more information and a floor plan, contact the exhibition management. SHOW HOURS Tuesday, 19 May 12:00pm - 5:00pm Exhibits open 5:00pm - 7:00pm ICSE 97 Opening Reception in Exhibit area Wednesday, 20 May 10:00am - 5:00pm Exhibits open 6:00pm - 8:00pm ICSE 97 Reception at the Computer Museum Thursday, 21 May 5:00pm - 8:00pm Exhibitor move-out ========================================================================= Invitation to Corporate Sponsors DEADLINES For listing in the Advance Program, Final Program, and Proceedings: 15 November 1996. For listing in the Final Program, and Proceedings only: 15 January 1997. CONTACT W. Richards Adrion CRICCS Deptartment of Computer Science 307 Lederle Graduate Research Center PO Box 34610 University of Massachusetts, Amherst Amherst, MA 01003-4610 USA adrion@cs.umass.edu +1-413-545-2475 +1-413-545-3729 (fax) http://www.cs.umass.edu/~adrion ICSE 97 invites interested organizations to support the conference by becoming corporate sponsors. The generosity of Corporate Sponsors enables us to offer a more well-rounded program. Conference Sponsorship begins at $2000. Corporate Sponsorship entitles your organization to receive the following benefits: * Your company logo to appear in the conference proceedings * Your company logo to appear in the Advance Program, Final Program and the Conference Proceedings (see deadlines) * One complimentary Conference Registration * A copy of the Conference Proceedings * Recognition of your company during the Conference ICSE 97 is also seeking corporate sponsorship for the following events and items: * Sponsorship of the opening reception in the Exhibition Hall * Sponsorship of the reception at the Computer Museum * Sponsorship of the Conference tote bag and/or other mementos to be issued to all Conference attendees Special events/items sponsors will receive the same benefits as general Corporate Sponsors as well as the opportunity to have their name associated with the event or their logo included on the item. Details on general Conference Sponsorship or on special event/item sponsorship may be obtained from the Conference General Chair. ========================================================================= TECHNICAL PAPERS CO-CHAIRS Alfonso Fuggetta, Politecnico di Milano Richard N. Taylor, University of California, Irvine DEADLINE Abstract in electronic format (ASCII email): 2 August 1996. Full paper due (6 copies, hard copy only): 9 August 1996. 5:00 p.m. (17:00) local time at receiving address. SEND TO Richard N. Taylor ICSE 97 Information and Computer Science Room 444 Computer Science Building University of California, Irvine Irvine, CA, 92717-3425 USA icse-97-papers@ics.uci.edu FOR MORE INFORMATION To contact the ICSE 97 Papers Co-Chairs, send e-mail to icse-97-papers@ics.uci.edu CHECKLIST Please follow the steps in this checklist to ensure completeness of your submission. ( 1. If you wish to request a mentor, please see the description of the mentoring program in the Invitation to Submit (page 2), and contact one of the Technical Program Co-Chairs no later than 15 May 1996. ( 2. Read the Invitation To Submit (page 2). ( 3. Fill out Cover Pages One and Two (pages 15-16). ( 4. Prepare your paper in the Conference Proceedings Format (pages 13-14). Papers must be no longer than 11 pages, including the text, figures, references, and appendices. ( 5. Submit the title and abstract of your paper by email to the address given. ( 6. Collect Cover Pages One and Two and the Paper, in the order given, in a packet, and make 6 copies of the packet. Use 8.5 x 11 inch or A4 paper. ( 7. Make sure each copy of the packet is STAPLED, not loose or held by clips. ( 8. You may include a self-addressed reply postcard which will be mailed to acknowledge receipt of your submission. ( 9. Send the 6 copies of your submission packet and the reply postcard, to the Papers Co-Chair at the Send To address shown. TECHNICAL PAPERS Papers describe innovative and significant work in the research and practice of Software Engineering. Papers are collected in an archival, refereed conference proceedings, published by ACM/IEEE, which is cited and read by researchers and practitioners world-wide. Accepted papers are presented at the ICSE conference, attended by hundreds of people. Having a paper on the technical program gives authors an opportunity to have a tremendous impact on the study and application of Software Engineering principles, theory, and techniques. Paper submissions to ICSE are reviewed rigorously by the Program Committee, who are volunteers drawn from the international technical community of Software Engineering researchers and professionals. Because there is no revision cycle, the content and presentation of submitted papers must be essentially acceptable as received. TYPES OF PAPERS The Software Engineering community consists of researchers and professionals from many different disciplines and intellectual traditions. The paper review process tries to rigorously review all submissions in a manner that takes into account the different criteria from different parts of the community. For reviewers to do this effectively, they need an accurate assessment of the type of each paper they read. Please select a type of paper from the following list that best describes your submission and write it in the appropriate place on the Cover Page. If you feel that your submission does not fit any of these types, or if it seems to match more than one type description, please contact a Papers Co-Chair for help in best classifying your submission. The three primary categories of papers are grouped into sets that will be published and identified separately in the conference proceedings. Research contributions Theory Papers. Theory Papers describe principles, concepts, or models on which work in Software Engineering might be based; authors of theoretical papers are expected to position their ideas within a broad context of Software Engineering frameworks and theories. Review criteria include the originality and soundness of the analysis provided, as well as the relevance of the theoretical content to Software Engineering practice and/or research. Systems Papers. Systems Papers describe novel technology for any aspect of software engineering. Review criteria include the originality and relevance of the system's architecture and behavior with respect to the existing state-of-the-art. Authors should be clear to what extent the system has been implemented and applied in practical circumstances. Empirical Papers. Empirical Papers describe the collection and interpretation of data concerning the use of software engineering methods, techniques, and tools. Data might include interviews, observations, surveys, or experimental manipulations. Both qualitative and quantitative approaches to data collection and analysis are welcome. Review criteria include the appropriateness and rationale for the methods of data collection and analysis, and the significance of the conclusions for practice or research in Software Engineering. Experience reports. Experience Papers describe the application of software engineering methods, theory or tools to the development of significant software products. Review criteria include the value of the reflections abstracted from the experience and their relevance to other designers or to researchers working on related methods, theory or tools. Opinion papers. Opinion papers present the author's well-supported opinion about some aspect of Software Engineering. Review criteria include the impact and quality of the argumentation, including the experience (research or practice) used to support the opinion. Authors of opinion papers are urged to contact one of the Papers Co-Chairs in advance of submitting a paper, to get feedback on their idea, since ICSE rarely accepts opinion papers. REVIEW PROCESS Each submitted paper will be reviewed by a group of at least three members of the program committee. Reviewer assignment will be done by matching the topic and focus of the paper with committee member expertise. The committee members will develop a summary review and recommendation for acceptance or rejection. Final decisions will be made at a program committee meeting, where the committee as a whole will review the recommendations and rationale made by committee members. Note that in addition to considering the criteria outlined for each type of paper, all papers will be evaluated for overall quality of presentation: the problem and its context must be clearly described, including relation to prior work. It must also be clear from the presentation that a succinct (25-minute), high quality verbal presentation at the conference will be possible. HOW TO SUBMIT Electronic Submission of Title and Abstract (Required): In addition to their appearance in the full, printed paper, the title and abstract of every submission must also be transmitted by email to icse-97-papers@ics.uci.edu by the deadline for abstracts shown above. This abstract must be plain text only (ASCII) - no markup languages, no binhex, no binary files. Submission of Full Papers: Submitted papers must appear in the standard Conference Proceedings format (see pages 11-12). Papers may be no longer than 11 pages in the Conference Proceedings format, including references, appendices and figures. The full papers may not be submitted electronically; paper copies are required. UPON ACCEPTANCE Authors will be notified of acceptance or rejection by the end of November 1996. Accepted papers will be published in the ICSE 97 Conference Proceedings. The primary author of each accepted paper will receive an Author Kit with detailed instructions on how to submit the camera-ready copy. These materials are due on 24 February 1997. ========================================================================= PANELS PANELS CO-CHAIRS Colin Potts, Georgia Institute of Technology David Leblang, Atria Software DEADLINE 2 August 1996 SEND TO Colin Potts College of Computing Georgia Institute of Technology 801 Atlantic Drive Atlanta, GA 30332-0280 USA potts@cc.gatech.edu +1-404-894-5551 +1-404-853-9378 (fax) or David Leblang Atria Software 20 Maguire Road Lexington, MA 02173 USA leblang@atria.com +1 (617) 676-2610 +1 (617) 676-2600 (fax) FOR MORE INFORMATION Contact the ICSE 97 Panels Co-Chairs. CHECKLIST Please follow the steps in this checklist to ensure completeness of your submission. ( 1. Read the Invitation To Submit (page 2). ( 2. Fill out Cover Pages One and Two (pages 15-16). ( 3. Prepare a Panel Proposal in the Conference Proceedings Format for publication, as described here. ( 4. Collect Cover Pages One and Two, the Conference Proceedings Summary, and the Proposal, in the order given, in a packet, and make 6 copies of the packet. Use 8.5 x 11 inch or A4 paper. ( 5. Make sure each copy of the packet is STAPLED, not loose or held by clips. ( 6. You may include a self-addressed reply postcard which will be mailed to acknowledge receipt of your submission. ( 7. Send the 6 copies of your submission packet, and the reply postcard, to one of the Panels Co-Chairs at the Send To address shown. THE AIM of the ICSE 97 panels is to stimulate discussion about ideas and issues of crucial importance to the software engineering community. Panels may emphasize complex technical issues, but they may equally provide an opportunity to propose views and address controversies through the medium of informed debate. Suitable topics for such discussion include pressing issues in software engineering theory and practice, emerging industry trends and enabling technologies, and professional, organizational, and social issues associated with software engineering. A panel is an interactive discussion. It is essential for the moderator and panelists to design it in advance, for them to prepare fully, and for the moderator to exercise control over the discussion. Too many promising panels turn out to be dreary paper sessions in disguise. We want the panels at ICSE 97 to stick (positively) in people's minds. TYPES OF PANELS Panels last 90 minutes and can be organized in many formats. Several suggestions are provided below. However, we strongly encourage proposals in original formats that will engage the panelists and audience in a lively and substantive discussion. Analytic Panels An analytic panel analyzes and synthesizes current practices in the various fields of software engineering. The panelists aim at introducing the audience to new ideas and should therefore be technical experts selected from distinct fields but addressing a single problem. Panelists should address the following questions: * How do their topic areas complement each other? * How do we reconcile vocabulary, concepts and notations? * How can their research results be transferred effectively to industrial practice, and, conversely, how can industrial needs be recognized and addressed by the research community? The biggest challenge in an analytic panel is to ensure it does not deteriorate into a paper session. It is therefore essential that panelists' ideas are explicitly interrelated and synthesized. Comparative Panels In a comparative panel, panelists compare distinct approaches, techniques and models to a particular problem. Panelists should explain why their approach is better than everyone else's (and not merely assert that it is). The panel should aim at identifying the common philosophy among the approaches represented in the panel, and on what crucial distinctions (as opposed to accidental details) their differences depend. A comparative panel should be controversial, but the panelists should treat each other's approaches with respect. Panelists should be technical experts within the same field. The biggest challenge with a comparative panel is to ensure that the panelists understand and respect each other's approaches and do not see the panel as an opportunity for a sales job. One technique is to have each panelist present "someone else's" approach as positively as possible. Exercises In an exercise, the aim is to have panelists solve a small but representative problem, using their chosen approach and with little preparation. In suitable circumstances, the problem scenario could be revealed to the panelists at the start of the session itself. The problem scenario will be selected in advance by the moderator of the session. The biggest challenges with an exercise are to ensure that the panelists are prepared and that the audience goes away seeing the forest, not just the trees. For an excercise panel to achieve any closure, it is essential that the moderator be able to summarize at the end of the session the key similarities and differences among the panelists' approaches. Predictive Panels In a predictive panel, panelists from different fields discuss the ways in which emerging techniques and technologies will affect the practice of software engineering in the future. Panelists should be experts in their relevant fields and should have clear ideas about how work in their fields is influencing the future. The challenge with a predictive panel is to avoid idle speculation and waffling. The key idea is careful selection of the topic and panelists TOPICS Panels may address any topic of relevance to software engineering research and practice. Panels are an opportunity to stimulate thinking about how software engineering is evolving. This means that topics need not be limited to the conventional boundaries of the field. REVIEW PROCESS Each proposal will be reviewed by the members of the panel committee, who will consist of academics and practitioners. We are looking for stimulating and timely proposals that will be debated by well-informed and engaging panelists and that will form a diverse, controversial, and well thought out collection. Please feel free to contact either panel co-chair in advance to discuss your proposal. Our criteria will include: * Clear emphasis on a well-defined topic, and the positions that the panelists are likely to take; * Relevance of the proposed topic to software engineering research or practice; * Likelihood of debate and controversy; * Demonstrated expertise of the panelists; * Evidence of fresh thinking in the panel format. In summary, we will ask ourselves whether the average audience member will go away from the panel with new and valuable ideas. FORMAT Proposal A proposal should contain the following: * A ONE-PAGE description of the topic, stating compelling issues to be debated, and their relevance to software engineering. * A ONE-PAGE description of the panel format (not limited to those specified above), stating how the panel will be conducted and why the proposed format is suitable for the given topic. * A ONE-PAGE summary of the organizer(s) and all the panelists, including names, affiliations, telephone numbers and e-mail addresses. Panelists must have agreed to be members of the panel. * A HALF-PAGE position paper from EACH panelist, summarizing his or her view about the topic, the issues it raises, and their qualifications to address the topic. Conference Proceedings Summary A summary of each panel will appear in the conference proceedings. The panel organizer is required to collate the half-page position papers (or later revisions of them), together with an introduction into a summary description of the panel. Panelists must agree to the half-page position papers being published in the conference proceedings. UPON ACCEPTANCE Authors will be notified of acceptance or rejection by the end of November 1996. Summaries of accepted panels will be published on the World Wide Web in the pre-conference publicity. Panel organizers will be sent an author kit for preparing camera-ready or electronic materials ready for publication. These materials are due 24 Feburary 1997. Panel organizers are expected to help panelists prepare for participation and coordinate the contributions of the panel. ========================================================================= TUTORIALS TUTORIALS CO-CHAIRS Mehdi Jazayeri, Technical University of Vienna Patricia Oberndorf, Software Engineering Institute Ed Weller, Bull HN Information Systems DEADLINE 2 August 1996 5:00 p.m. (17:00) local time at receiving address. SEND TO Mehdi Jazayeri Technical University of Vienna Distributed Systems Department Argentinierstrasse 8/184-1 A-1040 Vienna, Austria m.jazayeri@infosys.tuwien.ac.at +43-1-58801-4470 +43-1-5058453 (fax) http://www.infosys.tuwien.ac.at or Patricia Oberndorf Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 USA po@sei.cmu.edu +1-412-268-6138 +1-412-268-5758 (fax) FOR MORE INFORMATION To contact the ICSE 97 Tutorials Co-Chairs send e-mail to icse-97-tutorials@ics.uci.edu 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 (pages 15-16). ( 3. Prepare a Proposal for review, as described here. ( 4. Prepare a Conference Companion Summary (two pages) in the Conference Proceedings format for publication, as described here. ( 5. Prepare an Advance Program Description, as described here. ( 6. Prepare a Requirements List, as described here. ( 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 acknowledgment 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. 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. 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. ========================================================================= POSTERS POSTERS COORDINATOR Debra J. Richardson, University of California, Irvine DEADLINE 15 February 1997 5:00 p.m. (17:00) PST. SEND TO Debra J. Richardson Information and Computer Science University of California, Irvine Irvine, CA, 92717-3425 USA djr@ics.uci.edu +1-714-824-7353 +1-714-824-4056 (fax) http://www.ics.uci.edu/~djr/ FOR MORE INFORMATION To contact the ICSE 97 Posters Co-Chair send e-mail to djr@ics.uci.edu. CHECKLIST Please follow the steps in this checklist to ensure completeness of your submission. ( 1. Read the Invitation To Submit (page 2). ( 2. Fill out Cover Page One (pages 15). ( 3. Prepare an Informal Sketch of the poster for review, as described here. q 4. Collect Cover Page One and the Sketch in a packet; make 6 copies of the packet. Use 8.5 x 11 inch or A4 paper. q 5. Make sure each copy of the packet is STAPLED, not loose or held by clips. q 6. You may include a self-addressed reply postcard which will be mailed to acknowledge receipt of your submission. q 7. Send the 6 copies of your submission packet and the reply postcard, to the Posters Coordinator at the Send To address shown. Posters provide an excellent opportunity to show late-breaking results and ongoing work or finished results during the conference. Note that not all types of work in software engineering can be presented effectively using posters during the conference. Prospective submitters should carefully consider how their work may be presented. REVIEW PROCESS Submissions will be reviewed by a panel of experts in the field using the standard ICSE criteria: originality, importance and generality of contribution, soundness of rationale or demonstration, quality of written and graphic presentation, and appropriate citation of relevant literature. FORMAT Authors should prepare a four page description of their poster for review. The description should provide: (a) a summary of the technical content of the poster and (b) a description of how the material will be presented on the poster. UPON ACCEPTANCE Authors will be notified of acceptance or rejection by the end of March 1997. AT THE CONFERENCE Posters will have display space (approximately 2.5 m by 1.2 m), with a table for other materials, optionally including an informal demonstration and/or videotape. Author(s) will be expected to be present at scheduled times for informal discussions at their posters. (The conference will not provide any electronic equipment for demonstration or presentation of cd-rom or videotapes; use and security of such equipment is fully the authors' responsibility.) GROUND RULES The poster should effectively communicate the material without the presence of the author, as posters will remain posted throughout the entire conference. Dedicated interactive poster sessions, where presenters will be available at their posters to discuss the work and answer questions will be scheduled during conference breaks and other appropriate times. ========================================================================= RESEARCH DEMONSTRATIONS RESEARCH DEMONSTRATION COORDINATORS Anne Duncan, Digital Equipment Corporation Volker Gruhn, LION GmbH Barbara Lerner, University of Massachusetts, Amherst DEADLINE 1 November 1996 5:00 p.m. (17:00) local time at receiving address. SEND TO Volker Gruhn LION GmbH Universitaetsstr. 140 44799 Bochum, Germany gruhn@lion.de +49 (0) 234 9709 0 +49 (0) 234 9709 111 (fax) or Barbara Lerner Department of Computer Science Lederle Graduate Research Center PO Box 34610 University of Massachusetts, Amherst Amherst, MA 01003-4610 USA lerner@cs.umass.edu +1-413-545-3787 +1-413-545-3729 (fax) FOR MORE INFORMATION To contact the ICSE 97 Research Demonstration Coordinators send e-mail to icse-97-researchdemos@ics.uci.edu. CHECKLIST Please follow the steps in this checklist to ensure completeness of your submission. ( 1. Read the Invitation To Submit. ( 2. Fill out Cover Page One (page 15). ( 3. Prepare a Proposal for review, as described here. ( 4. If submitting a formal demonstration, prepare a two page summary in the Conference Proceedings format for publication, as described here. ( 5. If submitting a formal demonstration, prepare a Script Outline for review, as described here. ( 6. Collect your demonstration proposal (including Cover Page, summary and script outline for formal demonstrations) in a packet, and make 6 copies of the packet. Use 8.5 x 11 inch or A4 paper. ( 7. Make sure each copy of the packet is STAPLED, not loose or held by clips. ( 8. You may include a self-addressed reply postcard which will be mailed to acknowledge receipt of your submission. ( 9. Send the 6 copies of your submission packet, and the reply postcard, to one of the research demonstrations coordinators at the Send To address shown. RESEARCH DEMONSTRATIONS Research demonstrations enable conference participants to view research systems in action and to discuss the systems with the people who created them. Research demonstrations are intended to show early implementations of novel software engineering concepts. Proposals will be evaluated on the basis of their potential as demonstrations, their originality, and their promise for bringing new and exciting ideas to the conference. We consider any system which is at least six months away from appearing in a commercial product as a "research system". Commercial systems will not be accepted as research demonstrations. TYPES OF RESEARCH DEMONSTRATIONS Formal Research Demonstrations Formal research demonstrations are for mature presentations that can be communicated effectively in front of a large audience using projection technology. Formal research demonstrations will be scheduled into 40-minute blocks of time. In addition to the formal demonstration, a booth will be provided in the demonstration room to allow informal demonstrations throughout the conference. A 2-page description of each formal demonstration will appear in the conference proceedings. Informal Research Demonstrations Informal research demonstrations are appropriate for work that is very new, in a prototype stage, or otherwise not as fully developed as a formal research demonstration. Informal research demonstrations can also be used by presenters who feel that their work may be more effectively presented to a small audience. A booth will be provided in the informal demonstration room to allow ongoing demonstrations throughout the conference. There will be no description of informal demonstrations in the conference proceedings. REVIEW PROCESS Formal Demonstrations Submissions of formal research demonstrations will be reviewed for both content and presentation by at least three reviewers. Acceptance criteria for formal demonstrations include: * originality, significance, and relevance of the work; * maturity of the system as demonstrated by the script outline and screen pictures; * quality of the demonstration, indicated by the script outline and screen pictures. In addition, the number of demonstrations accepted may be limited by space and time. Informal Demonstrations Submissions of informal research demonstrations will be reviewed for content only. Acceptance criteria for informal demonstrations include: * originality, significance, and relevance of the work; * maturity of the system as demonstrated by the script outline and screen pictures. In addition, the number of demonstrations accepted may be limited by space. FORMAT Formal Demonstrations Submitters of formal demonstrations should prepare a proposal for purposes of review. The proposal should contain: * a statement of why a demonstration is an appropriate way to present the work; * a description of the relevance of the work to the software engineering community, emphasizing its novelty, uniqueness, and sound rationale; * a statement about the commercial status of the technology. (Commercial products should be demonstrated in the exhibits area.); * a description of who the presenter is (developer, designer, etc.); * a detailed description of the necessary equipment support. Researchers are strongly encouraged to bring their own computing equipment; * a two-page summary (see below); * a script outline (see below). Two-page Summary Submitters of formal demonstrations should prepare a two-page summary, suitable for publication in the ICSE 97 proceedings. It must be prepared in the Conference Proceedings format (see pages 13-14). Since this summary will be read by many people who will not view the system, it must be understandable without seeing the demonstration. It should contain appropriate references to papers and computer implementations that are closely related. Script Outline Submitters of formal demonstrations must also include a script outline which will be used to review the submission. The script outline should include at least the most important screen pictures. The outline should begin with a statement of the problem and the proposed solution, and how it addresses the problem. It is recommended that presenters refer to the screen pictures liberally throughout the text. Presenters should also refer to related work in the field, specifically to other implementations of similar ideas. Informal Demonstrations Submitters of informal demonstrations should prepare a proposal for purposes of review. The proposal should contain: * a statement of why a demonstration is an appropriate way to present the work; * a description of the relevance of the work to the software engineering community, emphasizing its novelty, uniqueness, and sound rationale; * a statement about the commercial status of the technology; * a description of who the presenter is (developer, designer, etc.); * a detailed description of the necessary equipment support. Researchers are strongly encouraged to bring their own computing equipment. COMPUTING AND PROJECTION EQUIPMENT Researchers doing demonstrations are expected to provide their own computing equipment, cables, and power cords whenever possible. Foreign researchers should remember to bring converters to 110V AC. If it will be impossible for you to bring your own equipment, you should provide a list of the equipment you would like the conference to provide. The conference might be able to provide a limited number of monitors and keyboards. The conference will not provide CPUs or disk drives as the likelihood of incompatibility with the software being demonstrated is very high. If you request equipment, acceptance of your demonstration will be contingent upon availability of the hardware. The conference will provide projection technology to be used in the formal demonstrations. More details about the specific projection technology will be provided to those with accepted formal demonstrations. UPON ACCEPTANCE Authors will be notified of acceptance or rejection by the end of December 1996. The primary author of each accepted formal demonstration will receive an Author Kit with detailed instructions on how to submit camera-ready materials for publication. These materials are due on 24 February 1997. AT THE CONFERENCE Formal and informal research demonstrations will be held in rooms dedicated to this activity throughout the conference. Formal research demonstrations will occur at scheduled times during the conference. Informal demonstrations will be ongoing; researchers are expected to be available throughout the conference. ========================================================================= SOFTWARE ENGINEERING IN ORGANIZATIONS: LESSONS AND STATUS REPORTS LESSONS AND STATUS REPORTS CO-CHAIRS Ian Thomas, Ian Thomas and Associates Elliot J. Chikofsky, DMR Group Inc. DEADLINE 16 September 1996. 5:00 p.m. (17:00) local time at receiving address. SEND TO Elliot Chikofsky DMR Group 404 Wyman Street, Suite 450 Waltham, MA 02154 e.chikofsky@computer.org +1-617-272-0099 +1-617-272-8464 (fax) or Ian Thomas Ian Thomas and Associates 650 Castro St, Suite 120-274 Mountain View, CA 94041 USA ithomas@netcom.com +1-415-390-0833 +1-415-964-1997 (fax) FOR MORE INFORMATION Contact the ICSE 97 Lessons and Status Reports Co-Chairs directly by e-mail. CHECKLIST Please follow the steps in this checklist to ensure completeness of your submission. 1. Read the Invitation To Submit. 2. Fill out Cover Page One (page 15). 3. Prepare a proposal (maximum two pages) in the Conference Proceedings format for publication, as described here. 4. Collect Cover Page One and the proposal, in the order given, in a packet, and make 6 copies of the packet. Use 8.5 x 11 inch or A4 paper. 5. Make sure each copy of the packet is STAPLED, not loose or held by clips. 6. You may include a self-addressed reply postcard which will be mailed to acknowledge receipt of your submission. 7. Send the 6 copies of your submission packet, and the reply postcard, to one of the Lessons and Status Reports Co-Chairs at the Send To address shown. Software Engineering in Organizations: Lessons and Status Reports are a new element in the ICSE program. The reports are intended to provide software engineering professionals with a picture of interesting and innovative software engineering work and research in the areas of software engineering practices, procedures, techniques, products, and organizational structures. Our goal in presenting the Lessons and Status Reports is to provide software engineers with: * insights that can be adapted and applied within their own work and organization; * information on the activities of software engineering groups doing innovative and interesting work; * information on software engineering activities laying the basis for future generations of software engineering tools and practices. We encourage submissions from institutions, organizations, and groups within companies, universities, and government. For example, company submissions are welcome from small product development teams in start-up companies to SEPGs to established software groups in large companies. We also encourage submissions from the broadest range of applications, from single-user PC software to global, enterprise-wide solutions. We are looking for lessons, procedures, techniques, approaches, products, and new perspectives on old problems that stimulate practicing software engineers, R&D organizations, and software engineering researchers, and which can be learned and applied. We expect submissions that: * present experience on some aspects of the application of innovative software engineering techniques in organizations; * report on the structure and status of software engineering activities and programs at an organization; though we also encourage submissions that do not fall into these two classes. The submissions should emphasize: * the circumstances under which work is done; * the underlying goals, policies, and organizational background; * perspectives of past, present, and future software engineering efforts. We aim to bring together people to report about their work with the focus on giving the "big picture" rather than the technically interesting spotlight on a singular scientific result. Authors of accepted submissions will be invited to make a 30 minute presentation at the conference. Example Submission We have included a sample submission in the conference Web pages (http://www.ics.uci.edu/icse97/) to illustrate what a good status report might contain. The submission is an example of an experience report on the use of an innovative software engineering technique. TYPES OF ORGANIZATIONS FOR LESSONS AND STATUS REPORTS Reports may describe software engineering work in: * Product development or consultancy organizations * Corporate, university, or government research/advanced development * Software engineering process groups (SEPGs) * Groups or institutions * Countries or geographical region * Collaborative efforts involving several groups or organizations * Partnerships of different types of groups, or groups cooperating across geographical, political, or cultural boundaries REVIEW PROCESS Proposals will be reviewed for acceptance based on the interest to members of the software engineering community and the objective of informing the community of software engineering activities world wide. Proposals may also be solicited from organizations. Solicited proposals will be subject to the same review process and criteria as proposals submitted in response to this call. PROPOSALS Proposed Lessons and Status Reports must be prepared in the Conference Proceedings Format, as described in pages 13 and 14. Proposals must not exceed two pages in length. UPON ACCEPTANCE Authors will be notified of acceptance or rejection by the end of November 1996. Accepted reports will be published in the ICSE 97 Conference Proceedings. The primary author of each accepted report will receive an Author Kit with detailed instructions on how to submit camera-ready materials for publication. These materials are due on 24 February 1997. AT THE CONFERENCE At the conference, the Status Report should be presented by a major participant in the work. The presentation should be based on the material described in the Status Report summary. It should be appropriate for a 30-minute verbal presentation that includes 5 minutes for audience questions. ========================================================================= WORKSHOPS WORKSHOPS CO-CHAIRS Reino Kurki-Suonio, Tampere University of Technology, Finland Lawrence G. Votta, AT&T Laboratories DEADLINE Proposal due (7 copies, hard copy only): 15 May 1996. 5:00 p.m. (17:00) local time at receiving address. SEND TO Reino Kurki-Suonio Tampere University of Technology P.O. Box 553 FIN-33101 Tampere, Finland rks@cs.tut.fi +358 31 316 2699 +358 31 316 2913 (fax) or Lawrence G. Votta AT&T Bell Laboratories Room 1G347 1000 E. Warrenville Road Naperville, Illinois 60566 USA votta@research.att.com +1-708-713-4612 +1-708-713-4982 (fax) FOR MORE INFORMATION Contact one of the Workshops Co-Chairs. CHECKLIST Please follow the steps in this checklist to ensure completeness of your submission. 1. Read the Invitation To Submit 2. Fill out Cover Page One (page 15). 3. Prepare a Conference Proceedings Summary (one page) in the Conference Proceedings Format (pages 13-14) for publication, as described here. 4. Prepare a Proposal for review, as described here. 5. Prepare a 250-Word workshop Call for Participation, as described here. 6. Collect Cover Page One, the Conference Proceedings Summary, the Proposal, and the workshop Call for Participation, in the order given, in a packet, and make 7 copies of the packet. Use 8.5 x 11 inch or A4 paper. 7. Make sure each copy of the packet is STAPLED, not loose or held by clips. 8. You may include a self-addressed reply postcard which will be mailed to acknowledge receipt of your submission. 9. Send the 7 copies of your submission packet, and the reply postcard, to one of the Workshops Co-Chairs at the Send To address shown. Workshops provide an opportunity for a group of participants to exchange ideas on a topic, either research or applied. Workshops are held before the formal conference and may be one, one and a half, or two days in length. Workshops can be a valuable forum for exchange of ideas among individuals with different perspectives on a topic. Workshops are not alternative forums for full papers which otherwise could be submitted to ICSE. Participation in workshops is typically dependent on submission of position statements. REVIEW PROCESS Workshop proposals will be reviewed by a committee representing a cross-section of Software Engineering researchers and professionals. Acceptance will be based on an evaluation of the workshop's potential for generating useful results, the timeliness and expected interest level in the topic, and the organizer's ability to lead a successful workshop. FORMAT You should prepare a proposal which will be used in the review process, a summary to be published in the ICSE 97 Conference Proceedings if the workshop is accepted, and a Call for Participation. Proposal Prepare a three-page proposal for the workshop review committee. Workshop proposals should contain: * an outline of the theme and goals of the workshop and its relevance to the field; * a description of the desired number of participants, the participant solicitation and selection process, pre-workshop activities, and planned workshop activities, including length of time; * a brief description of each organizer's background, including relevant past experience with workshops, and whether the organizers have organized ICSE workshops before. Feel free to discuss your ideas with the Co-Chairs before submitting. PUBLICATION Conference Proceedings Summary Prepare a one-page summary of the workshop, suitable for publication in the ICSE 97 Conference Proceedings. The summary should contain the title, organizer's name, organizer contact information, keywords, and a summary of the issues and goals of the workshop. This summary must be prepared in the Conference Proceedings Format (pages 13-14), except that no abstract is required. CALL FOR PARTICIPATION Prepare a 250-word Call for Participation describing the workshop and the participant selection process. The Call will be disseminated electronically, published in the ACM SIGSOFT and IEEE TCSE Newsletters, and the ICSE 97 Advance Program, if the workshop is accepted. UPON ACCEPTANCE Organizers will be notified of acceptance or rejection by the end of May 1996. Summaries of accepted workshops will be published in the ICSE 97 Conference Proceedings. The organizer is responsible for: * soliciting diverse participation in the workshop by disseminating the Call for Participation to appropriate mailing lists and other settings; * receiving requests for participation in the form of position or participation statements; * selecting and inviting participants; * distributing statements to all participants in advance. The statements provide participants with background and a chance to interact before the event; * developing an agenda in advance of the event and outlining planned workshop activities and their durations. Production of a proceedings for the workshop, if desired, will be the complete responsibility of the workshop organizer. ICSE 97 maybe able to assist with this, however. Interested parties should contact the Workshops Coordinators for more information. AT THE WORKSHOP The organizer is responsible for facilitating discussion by helping to establish and maintain a productive interaction and encouraging participation. In workshops, the emphasis is typically on group discussion of a topic rather than presentations of individuals' positions with follow-up questions. Diversity of perspectives should be encouraged. ICSE 97 will provide meeting rooms, coffee breaks, and audio-visual support for workshops. Workshop participants, including organizers, will be charged a fee to cover this support. If a proceedings is produced, its costs must also be covered by the registration fee. AFTER THE WORKSHOP It is important for the results of a workshop to be communicated to a larger audience. This can be accomplished in a number of ways, such as by holding a Special Interest Group meeting at the conference. In any case, workshops are expected to produce a poster describing the workshop for the ICSE 97 poster session, and a report on the workshop for publication in Software Engineering Notes. ========================================================================= DOCTORAL CONSORTIUM DOCTORAL CONSORTIUM CHAIR Michal Young, Purdue University DEADLINE 1 November 1996 5:00 p.m. (17:00) local time at receiving address. SEND TO See detailed instructions. FOR MORE INFORMATION To contact the ICSE 97 Doctoral Consortium Co-Chairs send e-mail to icse97-phd@cs.purdue.edu. The ICSE 97 Doctoral Consortium is a one day workshop prior to the regular ICSE technical conference. The goal of the doctoral consortium is to publicly discuss research goals, methods, and results at an early enough stage in Ph.D. research to provide useful guidance in completion of the dissertation research and initiation of a research career. The consortium and ICSE will also provide an opportunity for student participants to interact with established researchers and others in the wider software engineering community. A limited number of student participants will be offered support in the form of complementary admission to the consortium and ICSE 97. WHO SHOULD SUBMIT? Student participants should consider participating in the doctoral consortium at least six months before completion of their dissertation, but after having settled on a research area or thesis topic. REVIEW PROCESS Each prospective student participant will submit a package of materials for consideration by the consortium organizing committee. The committee will select participants on the basis of their anticipated contribution to the workshop goals. Among the criteria that will be considered in reviewing submissions are: * The quality of the research, as evidenced by submitted materials, and its relevance to software engineering. * The stage of the research. The organizers will seek to select students across a range of research stages. * Diversity of background, research topic, and approach. HOW TO SUBMIT To apply as a student participant in the Doctoral Consortium, prepare a submission package consisting of three parts listed below. Each of these parts must be submitted electronically by the listed deadlines; hardcopy submissions will not be accepted. GENERAL INFORMATION * Name of Student Participant * Name of thesis Advisor * University and Department * Full mailing address (repeat information from above as needed) including country and postal code. * Telephone * Fax * Electronic mail address * Electronic mail address of thesis advisor * Universal resource locator (URL), if available * Related submissions (e.g., if you are also submitting a technical paper to ICSE) * Brief description of research topic (25 words or less) * 2 to 5 key words and phrases RESEARCH ABSTRACT Submit an abstract describing your dissertation research. Your abstract should be at least 2 pages, but not more than 5 pages long, when prepared according to the format guidelines below. The research abstract should clearly indicate: * The research area or sub-area of your work. * The relation of your research to prior work in that area. * The expected contribution of your dissertation research. * The methods you are using or will use to carry out your research. It is particularly important to describe a plan for evaluating your work and presenting credible evidence of your results to the research community. Students at relatively early stages of their research will have some difficulty addressing some of these areas. Nonetheless, each prospective student participant should address them as well as possible. LETTER OF RECOMMENDATION Ask your thesis advisor to submit a letter of recommendation to icse97-phd@cs.purdue.edu. The letter of recommendation must include an assessment of the current status of your thesis research and an expected date for thesis submission. WHERE TO SUBMIT The general information should be submitted using electronic mail to icse97-phd@cs.purdue.edu by the date listed under Deadline. The subject line of the email message should be Application. Your packet will be acknowledged within 7 days. The letter of recommendation should be submitted using electronic mail to icse97-phd@cs.purdue.edu by the date listed under Deadline. The subject line of the email message should be Recommendation for XXX, where XXX is the name of the student applicant. The research abstract should be submitted electronically using ftp (preferred) or electronic mail to icse97-phd@cs.purdue.edu. Directions for submitting by ftp and electronic mail can be obtained by sending a message with subject line Instructions to icse97-phd@cs.purdue.edu. The general information packet and letter of recommendation should be plain ASCII text with no markup. Research abstracts may be submitted in any of the following formats: * Level 1 PostScript, with all fonts included except Times, Helvetica, and Symbol. * Adobe Portable Document Format (PDF) * Plain ASCII text with no markup Each research abstract must be a single file. Typeset abstracts should be set in 12 point type on a 14 point baseline, with 1 inch margins on all sides. Please note that this format is for initial submissions only. UPON ACCEPTANCE Notification of acceptance or rejection will be transmitted electronically by 10 December 1996. Hardcopy letters of acceptance (only) and offers of complimentary conference registration will also be mailed by 10 December 1996. Final versions of thesis abstracts for inclusion in the electronic proceedings are due by 15 February 1997. These abstracts must be prepared according to the ICSE Conference Proceedings format. Signed copyright release forms are also due by 15 February 1997. ========================================================================= STUDENT VOLUNTEER PROGRAM* STUDENT VOLUNTEER APPLICATION FORM STUDENT VOLUNTEER COORDINATORS Gregory D. Abowd, Georgia Institute of Technology Kevin Sullivan, University of Virginia DEADLINE Applications must be received no later than 15 February 1997. 5:00 p.m. (17:00) local time at receiving address. SEND FORM TO Kevin Sullivan Computer Science Department Thornton Hall University of Virginia Charlottesville, VA 22903 USA sullivan@uvacs.cs.virginia.edu +1-804-982-2206 +1-804-982-2214 (fax) http://www.cs.virginia.edu/~sullivan/ FOR MORE INFORMATION Send email to icse97@cs.virginia.edu. STUDENTS from throughout the world, both graduate and undergraduate, are invited to participate as ICSE 97 Student Volunteers. Student Volunteers are an important part of the success of each ICSE conference. In exchange for assisting with the conference, Student Volunteers receive free conference registration, participation in one tutorial, reduced-rate housing, and an invitation to a reception with leading people from the ICSE community. Other benefits include experiencing the conference from behind the scenes, a great team spirit, the chance to establish lasting friendships with other students, and the opportunity to learn more about the field by interacting closely with leading software engineering experts. Many people first get involved with ICSE by being Student Volunteers, building on this initial involvement throughout their professional career. A Student Volunteer application form is available electronically and applications are accepted electronically. For information or to apply, please contact the Student Volunteers Coordinators. STUDENT VOLUNTEERS ICSE 97 invites students to be part of the most exciting event in the Software Engineering field. Student volunteers are an integral part of the success of each ICSE conference. In return for their help with the conference, Student Volunteers receive complimentary conference registration, reduced-rate housing, and an invitation to a reception with leading figures in the ICSE community. A wide variety of positions are available, ranging from audio-visual support to registration assistance. Many of the duties are not glamorous, but all positions provide opportunities to interact with ICSE-97 contributors, attendees, and committee members from all parts of the world and many diverse areas of the software engineering community. QUALIFICATIONS Volunteers must be undergraduate or graduate students during the 1996-1997 academic year. All students, regardless of discipline, are encouraged to apply. No experience is required. We are looking for enthusiastic, intelligent, reliable people. Volunteers must commit to work a total of 20 hours beginning 24 hours prior to the first day of ICSE, i.e. between 17 May and 23 May. HOW TO APPLY An application form may be obtained via the ICSE-97 World Wide Web page http://www.ics.uci.edu/icse97 in the Student Volunteer Program. COMPENSATION POLICY All volunteers receive free registration for the conference, participation in one conference tutorial, and reduced-rate housing. Rooms are shared with another student of the same sex. Each volunteer will receive a free ICSE 97 T-shirt. All volunteers are responsible for their travel to and from Boston. Name: Sex: q Male q Female Address: Daytime telephone (include international code): Home telephone (include international code): Fax (include international code): E-mail address: Have you served as an ICSE Student Volunteer before? q Yes q No If yes, indicate which year(s): Do you have any special qualities or experience you think would be helpful to ICSE 97? What languages do you speak well enough to assist with non-native English speakers? Do you need housing at the conference? q Yes q No Department and School: Department and School Address: Student status as of 1 May 1997: q Undergraduate q Master's student q Doctoral student ========================================================================= COVER PAGE ONE COVER PAGE ONE should accompany all submissions. Submissions in the Paper, Panel and Tutorial Categories must also include Cover Page Two. You may use these paper copies from the booklet or photocopy the pages. An electronic version of the Cover Pages may be obtained via the World-Wide Web: http://www.ics.uci.edu/icse97/ PARTICIPATION CATEGORY (please check one): q Workshop Proposal q Paper q Panel q Lessons and Status Reports q Tutorial q Poster q Doctoral Consortium q Research Demonstration TITLE OF SUBMISSION Name of Contact Person Affiliation Street Address City State/Province Postal/Zip Code Country Email Telephone Fax NAMES AND AFFILIATION OF ADDITIONAL AUTHORS Name Affiliation Name Affiliation Name Affiliation Name Affiliation Name Affiliation Name Affiliation 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." SUBMISSION(S) Please list title and category of any related submission(s): ========================================================================= COVER PAGE TWO SUBMISSIONS of Papers, Panels, and Tutorials must also be accompanied by Cover Page Two. If your submission belongs to one of these categories please check the Matching Phrases and the Submission Type below. MATCHING PHRASES FOR PAPERS The following list contains matching phrases for papers that will aid in selecting reviewers for your submission. You are encouraged to check multiple matching phrases. If you do not see phrases that you would like to describe your submission, please create phrases and add them in for your submission. The phrases are listed in no particular topic order, so please read through them carefully when searching for descriptors for your own work. o Requirements engineering o Software architectures o Hypermedia o Design o Reuse o Object oriented technology and patterns o Programming languages and software engineering o Knowledge-based approaches o Information retrieval and digital libraries o Testing, analysis, and verification o Reliability o Formal methods o Mobile computing and mobile applications o Reverse engineering and program transformation o Environments o Software process: modeling, analysis, execution, evolution o Process improvement o Workflow o Computer supported cooperative work (CSCW) o Project management o Measurement, metrics, experimentation o Special techniques for: information systems design, distributed systems, real-time systems, safety-critical systems o Software documentation o Application of artificial intelligence techniques o Human-computer interaction (HCI) o Technology transfer, education o Standards and legal issues o Interoperability o Module interconnection languages o Configuration management TYPE OF SUBMISSION PANELS: o Analytic Panels o History Panel o Comparative Panels o Influencing the Future o Common Ground in Action PAPERS: o Research Contribution o Experience Reports o Opinion Papers TUTORIALS: Audience experience level o introductory o intermediate o advanced Duration o half-day o full-day CERTIFICATION FOR PAPER SUBMISSIONS This paper has not been previously published nor is currently under consideration for publication in any other forum than ICSE 97. Initials: ========================================================================= CONFERENCE COMMITTEE GENERAL CHAIR W. Richards Adrion CRICCS Department of Computer Science 307 Lederle Graduate Research Center PO Box 34610 University of Massachusetts, Amherst Amherst, MA 01003-4610 USA adrion@cs.umass.edu http://www.cs.umass.edu/~adrion +1-413-545-2475 (office) +1-413-545-3729 (fax) PROGRAM COORDINATORS Alfonso Fuggetta, Politecnico di Milano Richard N. Taylor, University of California, Irvine Anthony I. Wasserman, IDE IEEE LIAISON Anne-Marie Kelly ACM LIAISON Julie Goetz TECHNICAL PROGRAM RESEARCH DEMONSTRATIONS Anne Duncan, Digital Equipment Corporation Volker Gruhn, LION GmbH Barbara Lerner, University of Massachusetts, Amherst DOCTORAL CONSORTIUM Michal Young, Purdue University SOFTWARE ENGINEERING IN ORGANIZATIONS: LESSONS AND STATUS REPORTS Elliot J. Chikofsky, DMR Group Ian Thomas, Ian Thomas and Associates PANELS David Leblang, Atria Software Colin Potts, Georgia Tech POSTERS Debra J. Richardson, University of California, Irvine TUTORIALS Mehdi Jazayeri, Technische Universitaet Wien Patricia Oberndorf, Software Engineering Institute Ed Weller, Bull HN Information Systems WORKSHOPS Reino Kurki-Suonio, Tampere University of Technology, Finland Lawrence Votta, AT&T Bell Laboratories, USA OPERATIONS EXHIBITS Susan Hines, Danieli & O'Keefe Associates, Inc WWW COORDINATOR Roy Fielding, University of California, Irvine PUBLICITY LIAISON Debra A. Brodbeck, University of California, Irvine PROCEEDINGS Kari Nies, University of California, Irvine REGISTRATION Registration Department, Danieli & O'Keefe Associates, Inc. STUDENT VOLUNTEERS Kevin J. Sullivan, University of Virginia Gregory Abowd, Georgia Tech University CONFERENCE NEWSLETTER Will Tracz, Loral Federal Systems INTERNATIONAL RELATIONS AMERICAS Will Tracz, Loral Federal Systems, USA CANADA Nazim Madhavji, McGill University, Canada ASIA Koji Torii, Nara Institute of Technology, Japan AUSTRALIA/NEW ZEALAND Chris Marlin, Flinders University, Australia EUROPE Michel Lemoine, CERT, France About ACM ACM, the First Society in Computing, is a major force in advancing the skills and knowledge of Information Technology professionals and students throughout the world. ACM serves as an umbrella organization offering its 80,000 members a variety of forums in order to fulfill its members' needs- the delivery of cutting-edge technical information, the transfer of ideas from theory to practice and opportunities for information exchange. Providing high quality products and services - world-class journals and magazines; dynamic special interest groups; numerous main event conferences; tutorials; workshops; local special interest groups and chapters; and electronic forums - ACM is the resource for life-long learning in the rapidly changing Information Technology field. About ACM SIGSOFT ACM SIGSOFT focuses on issues related to all aspects of software development and maintenance. To that end, SIGSOFT provides a forum forcomp uting professionals from industry, government and academia to examine principles, practices, and new research results. SIGSOFT sponsors two major conferences each year, the International Conference on Software Engineering (co-sponsored with IEEE) and Foundations of Software Engineering, as well as specialized conferences on topics such as testing and maintenance. In addition, SIGSOFT sponsors several workshops that bring researchers and practitioners together to discuss and debate more specialized topics. SIGSOFT publishes a six times yearly newsletter, Software Engineering Notes, which includes articles submitted by members as well as the popular forum "Risks to the Public," which describes software safety mishaps and concerns. In addition, members receive proceedings from two sponsored conferences or workshops as a part of membership in the SIG. The SIG also offers its members a Member Plus Package. About IEEE Computer Society Celebrating its 50th anniverary in 1996, the IEEE Computer Society is the oldest and largest association of computer professionals in the world. It offers its 100,000 members a comprehensive program of publications, meetings, and technical and educational activities, fostering an active exchange of information, ideas, and innovation. The society is the world's leading publisher of technical materials inthe computing field. Headquartered in Washington, DC, the society services its members from offices in Los Alamitos, California, Tokyo and Brussels. The Computer Society is the largest technical society with the Institute of Electrical and Electronics Engineers, Inc. About IEEE Technical Council on Software Engineering (TCSE) The Technical Council on Software Engineering (TCSE) is the IEEE Computer Society's coordinating body for innovative programs and services in software engineering. TCSE is at the forefront of information exchange and support for both practitioners and researchers throughout the software engineering field. TCSE serves as both a coordinating entity for existing programs and as a wellspring for new initiatives and activities. The Key to the Technical Council approach is economy of scale. TCSE provides both resource sharing and extra resources for developing and continuing programs. These activities cooperate in scheduling, awareness, and encouragement for new programs and services. This forms a new critical mass to foster innovation and the expansion of software engineering offerings for the international members of the IEEE Computer Society. COOPERATING SOCIETIES Council of European Professional Informatics Societies (CEPIS) ========================================================================= ICSE 97 C/O Danieli & O'Keefe 490 Boston Post Road Sudbury, MA 01776 USA