Chair: Sherman R. Alpert, IBM T. J. Watson Research Center, firstname.lastname@example.org
OOPSLA is the premier venue for sharing and acquiring knowledge about object technologies and related software engineering practices, and the principal setting for these educational opportunities is the Tutorials program. OOPSLA has always offered tutorials of extraordinary breadth, depth, and quality, presented by world-class experts. Thousands of students, both novice and expert, have learned how to improve their skills and practices as a result of OOPSLA Tutorials.
This tradition of excellence in object-oriented education requires tutorial instructors with exceptional skills, knowledge, and experience. We invite object technology professionals to submit proposals for tutorials of high quality with the greatest relevance to other technology professionals. Tutorial proposals may range across all aspects of object technologyfrom introductions to applied software engineering practices or specific programming languages to advanced topics in object technology to leading edge research subjects.
Tutorials may be delivered in traditional lecture style, or in a hands-on form wherein participants actively engage in presenter-led activities, or other more innovative approaches, or any combination of stylesany approach that will result in a successful learning experience for the audience. OOPSLA tutorials are presented in half-day (3 contact hours plus breaks) or full-day (6 contact hours plus breaks) sessions throughout the conference week, primarily during the first two days of the conference. Popular subjects may be repeated. Tutorial presenters must provide hardcopy tutorial notes for attendees. Tutorials will be presented in rooms that include 800x600 resolution projection monitors.
Back To Top Of Page
Submissions due date: 22 March 2002, earlier is better
Notification of acceptance or rejection emailed: 7 May 2002
Accepted tutorials will become part of the OOPSLA 2002 Program and will be described in the Advance Program (hardcopy and online) using the text of the Abstract portion of the tutorial proposal.
Camera ready tutorial notes for participants are due: 6 September 2002
Back To Top Of Page
Tutorial presenters receive an honorarium. The amount of the honorarium is calculated as follows, where a half-day tutorial is 1 unit and a full-day tutorial is 2 units. For N = the number of non-student attendees who register for the tutorial (Note: Student Volunteers and conference attendees who have registered as students will have free admittance to tutorials on a space-available basis):
|N < 10
||$0 and the tutorial is canceled
(Here, N is based on number of registrants as of close of business 17 October 2002, the end of Advance Registration; for all other cases, N is based on final registration numbers)
|10 <= N < 75
||$1800 for the first unit + $500 for each subsequent unit (for full days and/or repeats)*
|N >= 75
||$2500 for the first unit + $500 for each subsequent unit (full days, repeats)
|Sold-out tutorials regardless of N**
||Same as N >= 75
* When a tutorial is repeated (presented more than once during the conference), N will be based on whichever session has the highest attendance.
** The Tutorials Committee assigns tutorials to rooms of varying capacities based on each tutorial's expected interest and attendance. A tutorial may be assigned to a room of capacity M where M < 75; when M people enroll for the tutorial, it is considered sold-out and the presenters receive the higher compensation. If (a) the presenters themselves make a specific request for the tutorial to have less than 75 maximum attendees, and (b) the Tutorials Committee disagrees and wishes to assign the tutorial to a larger capacity room, and (c) the presenters insist on the smaller capacity, then the presenters waive the right for the higher compensation in the case of the tutorial reaching the requested capacity.
||Tutorial compensation does not include free registration as in previous years.
||At least one of the tutorial presenters must register for the conference. Tutorial presenters pay the reduced registration fee for ACM members, even if they are not ACM members.
||When a tutorial has multiple presenters, the primary tutorial presenter will decide in advance how the honorarium is to be divided among the tutorial presenters.
||The honorarium policy is the same for both US and non-US presenters.
||For those subject to US income tax, the amount of the honorarium is reported to the IRS.
||Honorarium checks will be available at the conference when the tutorial presentation is complete.
Back To Top Of Page
Electronic submission of proposals is required by means of the OOPSLA submission system. Other submissions will not be accepted. Be sure to thoroughly complete all required portions of the online submission form. Incomplete submissions will not be evaluated. Proposals may be modified up until the deadline date.
Back To Top Of Page
Tutorial Proposals will be evaluated by the OOPSLA 2002 Tutorials Committee according to the following criteria:
- Value and relevance of the topic to OOPSLA attendees
- Completeness and quality of tutorial proposal
- Expertise and experience of the presenter(s)
- Demonstrated presentation ability of the presenter(s) (e.g., past experience in presenting tutorials at OOPSLA or elsewhere)
In order to make informed decisions, the Tutorials Committee members will need to clearly understand from each proposal the tutorials technical content, the intended audience of the tutorial, the instructional objectives for this audience, and the tutorial organization and instructional approach that will be used to achieve the objectives. More precise field-by-field guidelines follow:
Field in online submission system
What to enter
||Include for each presenter: name, email address, affiliation, address, and a brief biography indicating the presenter's expertise and experience in the tutorials subject matter. If additional room is needed for additional presenters, include such information in the Remarks field.
||Along with the Abstract, the main topic keywords will help us better understand your submission and choose appropriate reviewers.
||The maximum number of words for the abstract is 200. If your proposal is accepted, the abstract will appear in the hardcopy Advance Program and on the OOPSLA 2002 Web site. Therefore submit an accurate and polishedi.e., finalizedabstract.
||Specifically, what will an attendee learn in this tutorialthat is, what knowledge will an attendee have at the end at the tutorial that he or she did not possess beforehand?
||The expertise level of the tutorial. Choose from Beginner, Intermediate or Advanced.
||Briefly describe the appropriate pre-tutorial knowledge of attendees.
||What instructional format will the presenter(s) use? E.g., lecture along with slides, hands-on exercises, group problem solving sessions.
||Choose from Half day (3 contact hours plus breaks) or Full day (6 contact hours plus breaks). If you propose a full day tutorial, be sure to explain in the Remarks field why you feel a full, rather than a half, day is necessary.
||Yes or No: whether or not you are willing to repeat the presentation of the tutorial if there is sufficient demand.
||You should use this field:
(a) for information about additional presenters, if any
(b) if you are proposing a full day tutorial, to explain why a full day is required
(c) to indicate whether you have presented this tutorial before (where and when)
(d) if you have any further remarks about your submission that you would like to communicate to reviewers.
Examples To Emulate
Below are some exemplary examples of four portions of a tutorial proposal, the Abstract, the Tutorial Objectives, the Attendee Background section, and the Presentation Format. (These are intended simply as good examples of the information requested. No endorsement on content or topic is implied by the use of these examples; they are merely for illustration purposes.)
Note: The following sample Abstracts are short, due to space considerations. Your proposals Abstract may be up to 200 words.
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 Formats
Presentation Format: This tutorial will be lecture 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 Top Of Page
For More Information
For additional information, clarification, or questions please feel free to contact the Tutorials Chair: Sherman R. Alpert, email@example.com
Back To Top Of Page
OOPSLA Home || Call For Participation || Registration Info || Site Map || Committee
Submission System || About Seattle || Past OOPSLAs
OOPSLA 2002 6220 NE Glisan Street Portland, OR 97213 USA
Voice: +1-503-252-5709 Fax: +1-503-261-0964 E-mail: firstname.lastname@example.org