reports and
talk slides


Call For


Recent OOPSLAs &
Attendee Comments


Site Map

OOPSLA 2000, Conference On Object-Oriented Programming, Systems, Languages and Applications

Chair: Laura Hill, tutorials@oopsla.acm.org
Submissions due date: April 3, 2000
Notification of acceptance or rejection: May 26, 2000

One of the hallmarks of OOPSLA is the breadth, depth, and high quality of its tutorial program. Traditionally, OOPSLA tutorials have covered all aspects of object-oriented technology from introductory surveys to industrial software engineering practices to leading edge research topics. For OOPSLA 2000 we especially encourage proposals for innovative tutorials - tutorials that depart from lecture style delivery, or tutorials on highly advanced topics in object technology. Tutorials are presented in half-day or full-day sessions throughout the conference week, primarily during the first two days of the conference. Popular subjects are sometimes repeated.

Tutorial proposals will be evaluated by the OOPSLA 2000 Tutorial Committee, which is composed of people from industry, academia and industrial research, all with extensive experience in object-oriented technology. Submissions will be evaluated on the following criteria:

  • Value and relevance of the topic to OOPSLA attendees
  • Completeness and quality of tutorial proposal
  • Expertise of the presenter(s)
  • Presentation ability of the presenter(s)
  • Innovation in topic or proposed presentation approach.

The Tutorial Chair will send notification of acceptance or rejection by May 26, 2000. Accepted tutorials will become part of the OOPSLA 2000 Tutorial Program and will be described in the Advance Program using the text submitted in the tutorial proposal. Camera ready and electronic tutorial notes for participants will be required by a date stipulated in the acceptance notifications. Please be sure to thoroughly complete all of the required portions on the online submission form. In order to make informed decisions, the Tutorial Committee members will need to find sufficient information in the proposal to clearly understand the intended audience, the tutorial objectives for this audience, the technical content plan and the tutorial organization and approach that will be used to achieve the objectives. Incomplete submissions will not be evaluated. Tutorial presenters will receive a complementary conference pass (one per tutorial), an honorarium and some travel expense coverage (contact the Tutorials Chair for full details).

Tutorial Proposal Format
Tutorial proposals will be submitted through the Web by following the instructions in the "Submission Process" section of these guidelines. The Web submission system will be able to handle PostScript, PDF, Microsoft Word, and HTML. Each submitted proposal MUST include the following information:

  • Tutorial summary (used in advance program)
  • Content outline
  • Presenter resume
  • Tutorial resume
  • Supporting material

1. Tutorial Summary: The tutorial summary contains cover information, the tutorial description, and a brief presenter biography (for each presenter). It is used as the copy that appears in the Advance Program.

a) The cover information includes each speaker's name and affiliation, as well as the contact information (phone, email, postal address) for the primary contact person. It also includes a classification of the tutorial level (introductory, intermediate, advanced, or expert), topic area(s), attendee prerequisites, and whether it is intended as a half or full day tutorial. This information will be entered directly into the online submission system.

b) The tutorial description may be edited to maintain consistency among entries, but due to publication deadlines, presenters will NOT get an opportunity to revise this text after the original submission. Make the description complete, descriptive, and less than 200 words total. The description should include an (1) abstract, (2) tutorial objective, (3) attendee background, and (4) presentation format. The abstract should briefly describe the tutorial content. The tutorial objective should state succinctly what the attendee will understand, learn, or be able to do after taking the tutorial. The attendee background should state clearly all assumed participant knowledge or skills. The presentation format should describe how the content will be delivered (See examples for all of these at end of guidelines).

OOPSLA tutorial attendees expect material that is accurate, specific, and useful. They want to use the tutorial to learn new things about your corner of object technology. They have real problems to solve and are attending your tutorial because they expect to learn, and to become effective, in a way that they could not do simply by reading the latest paper on the subject. Traditionally, OOPSLA tutorials have been lecture based. We'd like to encourage more interactive tutorials with individual or group based exercises. If the exercises are well designed and the group dynamics well controlled, the tutorial objectives can be met with minimal or even no lecturing by the presenters; the presenters bring their expertise to bear by creating good exercises, a good session process, and by good facilitation of the groups.

NOTE: Tutorials always sell out. There is no need to worry about making your tutorial sound wider than it is to attract more people. On the contrary, precision in the description is more likely to gain acceptance than is vague broadness.

c) The brief biography should be no more than 150 words to summarize the presenter(s)' resume(s).

2. Content Outline: The outline should illustrate the scope (both breadth and depth) as well as the proposed format of the tutorial. For OOPSLA 2000 we are looking for tutorials with innovative delivery that is more effective than pure presentation, encouraging active attendee participation. The estimated time to be spent on each major item should be noted. Significant examples, case studies, or exercises that will be used should be included. A half-day tutorial is three hours broken into two sessions by a twenty minute coffee break. A full-day tutorial is six hours broken into four sessions by lunch and two coffee breaks. Half-day tutorials are the norm unless a full day is absolutely needed to meet well scoped tutorial objectives.

3. Presenter Resume: Attendees not only expect the tutorial material to contain distilled expertise, but also expect the tutorial speaker(s) to be expert in the field and to be able to answer a wide variety of questions. In this section, please include a summary of technical and presentation experience for each presenter. References from previous presentations are useful. Be certain to include previous OOPSLA or other conference tutorial experience. The technical experience related to the subject should be highlighted.

4. Tutorial Resume: Has this particular tutorial been given before (as opposed to whether or not the presenters have given tutorials before)? Is so, where was it given, how was it received, and what changes or improvements are you planning to make for this rendition?

5. Supporting Material: Other material that might be submitted in your proposal (but which is not required) could include:

  • Tutorial Notes: a set of notes for the tutorial would certainly be useful. We don't expect a completely developed set of notes if the tutorial is new; however, a few representative pages that illustrate the level of content and the quality of the illustrations would be very useful.
  • Sample exercises, if appropriate
  • Representative AV Materials: Samples of slides, transparencies or other materials.
  • Other Materials: Books titles, papers, and any other information that illustrates the content of the tutorial.
  • Advertising materials, if the tutorial is offered commercially.

This information is particularly important for new tutorials or presenters.

Submission Process

  • Electronic submission of proposals is required. Paper and fax submissions will not be accepted. Much of the information will be entered directly. Other information will be attached as files with the submission, or cut and pasted into an entry field.
  • Go to your OOPSLA 2000 Personal Page. If you do not have a personal page yet, or if you have forgotten the URL, go to the "My OOPSLA2000"" page (you can also get there from the OOPSLA home page).
  • From your OOPSLA 2000 Personal Page, follow the "Submit Tutorial" link.
  • Complete the Tutorial Form on the Web page and hit "submit". You will be transferred to your own private URL from which you can check on the status of your Tutorial submission at any time.
  • You will receive confirmation by email that your proposal has been received and is complete.
  • Proposals must be submitted no later than 3 April 2000, but earlier is better. We will read early proposals and work with the submitter(s) to further develop proposals that need additional information or to identify possible innovative techniques for delivery.
  • Proposals may be modified up until the deadline

Acceptance and rejection notifications will be emailed by 26 May 2000.

For additional information, clarification, or questions please feel free to contact the Tutorial Chair, Laura Hill, at tutorials@oopsla.acm.com

Examples to Emulate
Below are some examples of the essential and required three pieces, abstracts, objectives, and attendee background, of good tutorial descriptions. These are good examples of the information requested. No endorsement on contents or topic is implied by the use of these examples; they are merely for illustration purposes.

Example Abstracts

Abstract: When the performance penalty of object-oriented systems is mentioned, a common response is to blame antiquated hardware designs for not supporting object-oriented languages as they deserve. To what extent can the performance gap between conventional languages and object-oriented languages be closed using hardware? What architectural changes benefit object-oriented systems, and by how much? There have been many attempts to make hardware that better supports object-oriented programming. This tutorial describes some of these systems, and the extent that they have succeeded or failed in their aims. These systems include the iAPX432, SOAR, Rekursiv, and MUSHROOM, as well as some features from mainstream architectures such as SPARC.

Abstract: This tutorial presents techniques for improving, understanding, and expressing object analysis and design models. These techniques include development of: Use Case Conversations, User Navigation Models, CRC cards, object behavior stereotypes, control style analysis, behavior refactoring worksheets, hot spot cards, and flexibility design. These techniques can be successfully applied to augment your analysis and design toolkit, regardless of methodology. This tutorial will be conducted as a hands-on-workshop where we review guidelines and examples to illustrate key techniques, and use the techniques to develop the artifacts.

Abstract: There are many issues that need to be addressed before a truly reusable C++ class library can be built. This tutorial will examine these issues from both an abstract perspective (design) and a pragmatic perspective (code).

Abstract: As Smalltalk projects grow, they tend to hit the Smalltalk productivity wall - the point at which added resources do not contribute proportionately to project progress. This can happen at any point between three to six or more developers. This tutorial defines the problem, surveys available products, and provides generic and customized practical solutions using Object Technology's ENVY/Developer as a model.

Abstract: A project that is using object technology and an iterative development process faces a number of unique issued in order to deal with the project's entire life cycle. This tutorial presents a process framework that can be tailored to a specific project's situation. The tutorial follows a logical order of topics facing projects. Topics include estimating, scheduling, methodology selection, iterative development, and reuse. Specific advice derived from multiple project experiences is given during the discussion of each topic area.

Example Tutorial Objectives

Objective: The intermediate level C++ programmer who attends this tutorial will gain experience in the following areas: the design of a minimal public interface; the handling of variable-sized object; the avoidance of memory leakage; the construction of optimally reusable base classes; heuristics for efficient operator overloading; the roles of containment, inheritance, and multiple inheritance in C++ programming; the use of polymorphic vs. monomorphic functions.

Objective: This tutorial is intended to prepare the participant (1) to determine whether an object DBMS is appropriate technology for his or her database needs (2) to understand the technical tradeoffs between relational and object DBMS technologies, and (3) to evaluate the commercially available object DBMS products.

Objective: Participants will acquire experience using design patterns to solve real problems. This experience will enhance participants' design abilities by teaching them how to apply design patterns to their own object-oriented systems.

Objective: Participants will be acquainted with a comprehensive test plan that integrates the construction process and the testing process, and will be provided with a scalable total process that can be tailored to the size of a project and the degree of coverage required by the application.

Example Attendee Backgrounds

Background: Participants should be experienced Smalltalk programmers

Background: Participants should have a general familiarity with the object-oriented paradigm, preferably being fluent in one or more object-oriented languages. Familiarity with Smalltalk will be useful, but not required. The intended audience is professionals charged with developing or managing instruction in object-oriented techniques, either in a university or industry context.

Background: The tutorial is targeted to those individuals interested in the managerial issues that influence the success of object -oriented software development efforts. It is assumed that the audience has some familiarity with the basic concepts of object technology and have begun to worry about how to effectively employ the technology.

Background: Basic knowledge of the operational behavior of languages, particularly inheritance and polymorphism, but with no formal theoretical understanding. Only a knowledge of simple set theory will be required; and a willingness to perform certain mathematical substitutions. The tutorial is aimed at software professionals wanting to write type-correct software; language designers wanting to understand type issues in OOP; final year undergraduates and first year graduate students wanting to relate traditional notions of type to OOP.

Example Presentation Format

Presentation Format: This tutorial will be presentation based.

Presentation Format: This tutorial will be 70% lecture and 30% individual paper exercises.

Presentation Format: This tutorial will offer only a minimum amount of lecture, with the majority of time spent in small groups trying to solve specific problems. Lectures will be used to deliver the key points but after approximately every 30 minutes of lecture, participants will complete a set of short exercises to reinforce the lecture material. Solutions to the exercises will be presented and discussed.

Presentation Format: After a brief introduction by the presenter to set the scope and objectives
for the session, participants will be divided into groups, and each group given one of four different problems to solve. Then two groups that have tackled different problems will swap members to compare solutions and prepare a poster that explains how the differences in the problems affected the solution approaches taken. There will then be an opportunity for all participants to view and discuss the posters. In the second half of the session the process will be repeated but with different group memberships and different problems. The session will end with the presenter drawing together the results of the exercises and explaining how they compare with recently published research results.

Back to Call For Participation

Top Of Page