Home

NEW!
Post-conference
reports and
talk slides


Final
Program


Call For
Participation


About
Minneapolis


Recent OOPSLAs &
Attendee Comments


Conference
Committee


Site Map

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


Chair: Peter Smith, designfest@oopsla.acm.org
Submissions due date: April 3rd, 2000.

The DesignFest was created to give attendees the opportunity to learn more about analysis and design by actually working through the design process rather than just reading about it. The DesignFest is not about passively sitting and listening to experts talk about design -- it is about sharpening your analysis and design skills by rolling up your sleeves and working on a real problem with others in the field. The DesignFest is neither a design class nor a tutorial; it is an opportunity for designers to enhance and measure their skills by interacting with their peers.

This call-for-participation is for analysis and design problems, not participants. Problems should be sufficiently large that they present an interesting challenge, and yet sufficiently small that the participants can complete a design in a single day. Problem descriptions may be focussed toward analysis, design or preferably both.

We invite you to submit problem proposals, especially ones extracted from real-world projects.

People wishing to participate in solving these problems (rather than submitting problems) should simply sign up for DesignFest on the OOPSLA 2000 registration form.

DesignFest Problems
When submitting a problem description, you should use the following structure as a guide.

1. Contents of the Problem Description
A description of a domain - This description can be accompanied by pictures, images, text or whatever. The purpose of this description is to make clear in which context the problem is placed. The text should explain terminology and should be understandable by laymen. All abbreviations must be explained.

A description of the program that is wanted - This should state the goals of the program and the required functions. This description should state what the program should achieve without enforcing any solutions.

2. Detailed Requirements
Because of time limitations these should of course be restricted. An indication should be given of performance requirements and capacity. Requirements should be "refutable" statements (at least according to Michael Jackson).

3. Use Cases
Descriptions of interfaces to other systems. This could be header files or file formats. This is of course optional when no interfaces to other systems are necessary.

4. References for Further Study
These are references to articles, other similar systems or implementations.

Suitability of Problems
In an effort to improve the suitability of problems, the DesignFest review committee may ask the problem author to make clarifications if the problem requirements are not clearly specified. In particular, for problems that are "Design specific," all requirements must be clearly stated such that participants can easily understand them without further elaboration during the DesignFest sessions. For "Analysis specific" problems, this requirement is less important.

In addition, in order to clarify requirements, it is likely that the problem authors will be asked to be present during the opening of each of the sessions.

Submission Process

  • Electronic submission of problems is required. Paper and fax submissions will not be accepted.
  • 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 DesignFest Problem" 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 may be modified up until the submission deadline.

Proposals must be submitted no later than 3 April 2000, but earlier is better. Acceptance and rejection notifications will be emailed by 26 May 2000.

After a problem is accepted and review comments have been exchanged, it is necessary that the problem authors submit their problem in HTML format.

For additional information, clarification, or questions please feel free to contact the DesignFest Chair, Peter Smith, at designfest@oopsla.acm.org.



Back to Call For Participation

Top Of Page