Authors should submit an electronic copy of the full paper, in English, to the program chair by no later than June 10th, 1996. Email firstname.lastname@example.org. Papers must be formatted in Postscript with only the most comprehensive pattern languages to exceed 10 pages. Submissions must be prefaced with ASCII text containing the paper's title, authors' names, contact name, email address, postal address, phone number, and a 100-word abstract.
We will notify you as to whether your paper will be reviewed at the conference by July 15th, 1996. Revisions for draft distribution to registrants are due July 29th, 1996. Final versions for papers selected for publication in the proceedings are due 14 October, 1996, roughly one month after the conference. Our publisher requires that papers accepted for publication in the proceedings be in Microsoft Word format.
This year, we'll be holding workshops in the evening that cover topics like ``experience with patterns in practice'' and ``how to write good pattern descriptions.'' The workshops scheduled so far are presented below. If you'd like to propose a workshop, please send email to Douglas C. Schmidt (email@example.com)
Experience reports are short presentations by practitioners sharing their experiences in using patterns in various aspects of the software development process. Experience reports are selected for their general interest, diversity, new or novel slant, and willingness by the presenters to share technical information. Experience reports may describe internal applications or commercial product developments. However, it is inappropriate for an experience report to have any commercial sales content.
The best proposals generally describe projects that have achieved some major milestone, reached a point of completion, or have been terminated. Early or premature results, with promise of being completed by PLoP'96 generally are not appropriate for this forum. Also, experience reports should not cover specific details or techniques that more appropriately might be covered in a pattern paper.
Successful proposals must identify two or three issues that represent the valuable contribution that the authors will present if the report is accepted. General conclusions such as "teams must be small", "interaction between team members is essential", "the use of a pattern language helped the development", etc. will not be accepted as a valuable contribution to the experience report session this year.
Experience reports should be brief but to the point (not less than 5 and not more than 10 pages). The report must include a brief description of the overall development life cycle. This implies that if the experience is based on a prototype development or research in progress, then it is not suitable for this year's Experience Reports session. The report should articulate concisely the issues that will be presented to improve the chances of considering the report for further evaluation and review. The report must also include the specific lessons and insights gained in tackling the issues under consideration.
Accepted reports will be presented during the Experience Reports session of the conference. The presetation should include a brief overview of the results reported. Following the presentation, the report will be reviewed using the pattern workshop procedure. Authors will be given an opportunity to incorporate feedback received before publishing in the conference proceedings.
Submissions must include contact information of the person(s) who will be presenting the report if accepted. Contact information must include name, affiliation, address, electronic mail, phone and fax numbers where the presenter can be reached to answer further questions.
If you have any questions regarding experience reports, send email to either or both of the Experience Reports Co-Chairmen, Steve Peterson (firstname.lastname@example.org) and Kyle Brown (email@example.com). For more information about the dates and procedures for submitting experience reports to PLoP '96 please see the discussion above on submitting papers to PLoP.
Here are just some of the issues you need to consider:
You do not have to qualify to attend this workshop. All conference attendees are welcome. However, you will have to qualify to make a presentation. If you have some strong opinions about How to Write Effective Patterns and would like to make a 5-10 minute presentation, send me an outline (firstname.lastname@example.org).
The conference will be held at Allerton House, a mansion on a large, mostly wooded estate that is owned by the University of Illinois. Accommodations a re available on site, in the nearby village of Monticello or in Champaign-Urbana. Airport limousine service is available to the conference site.
If your schedule allows it, arriving early on Wednesday the 4th will let you get settled in and renew acquantences, plus, commuter airline schedules are undependable under the best of circumstances. Pizzas will be served around 7:00 on Wednesday night for early arrivals.
Last modified 11:34:24 CDT 28 September 2006