Join us on:
Facebook
LinkedIn
Plaxo

DesignFest®

Call for Papers - Due June 11, 2009

The OOPSLA DesignFest® gives OOPSLA attendees the opportunity to learn more about design by solving a design problem in a team of fellow OOPSLA attendees. DesignFest is not about passively sitting and listening to experts talk about design. DesignFest is about sharpening your design skills by rolling up your sleeves and working on a real problem with others in the field. You can expect to interact with everyone from total beginners to textbook authors!

Submission Summary
Due date:June 11, 2009
Notification date:
July 17, 2009
Submit to:OOPSLA submission system
Contact: This e-mail address is being protected from spambots. You need JavaScript enabled to view it (chair)
DesignFest® is looking for new problems. Problem descriptions should define the problem clearly, and ideally are different from past problems. For a list of past problems, see http://designfest.acm.org/Problems/Welcome.htm.

If you would like to participate in solving a DesignFest® problem during the OOPSLA conference, you do not have to submit a proposal--simply sign up when you fill out your registration form.

Content

DesignFest® problem submissions must include the required items below (and may include the optional items):

  • Abstract: a concise presentation of the problem. The abstract will be used in the subscription process for attendees. Please keep this to fewer than 200 words. Required.
  • Domain description: a description of the contextual organization for the deployed solution. Pictures, images, text or other material may accompany this description. The text should define all terminology and should be understandable by a layperson. All abbreviations must be explained. Required.
  • Problem statement: the problem that needs solving or the improvements required to an existing solution. This could be a description of the program, including the goals of the program and the required functions. It should state what the program should achieve without enforcing any solutions. Required.
  • Use cases: descriptions of a system’s behavior as it responds to requests that originate outside of the system. Use cases analysis is widely used to capture the functional requirements of a system. Use cases are well suited to provide hints for the design process, as design teams tend to work on them first. A handful of use cases should be provided. Required.
  • Analysis diagrams: a class diagram of the problem domain's object model, or any other type of diagram which may serve as a basis for the design, could be included here. Optional.
  • Detailed requirements. Because of time restrictions in the design sessions, these should be limited. An indication of performance and capacity requirements may be given. Optional.
  • Interfaces: 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. Optional.
  • References for further study: references to articles, other similar systems or implementations that may aid in understanding the domain or problem. Optional.
  • Expected deliverables. This is not a strict requirement, but if the author wishes to see his or her problem addressed in a particular setting or process method this can be indicated in this way. If the intent is to do detailed analysis rather than design, this should be stated, and analysis-related portions of the submission can be significantly less detailed or eliminated. Optional.

Problem descriptions from past DesignFests® are available on the DesignFest® web site. You may want to review some descriptions to get a sense of suitability and complexity.

Submission Process

Electronic submission of proposals is required through the OOPSLA submission system.

Additional information

For additional information, clarifications, or questions, please contact the DesignFest® chair, Juanita Ewing, at This e-mail address is being protected from spambots. You need JavaScript enabled to view it

Please email any questions to . This e-mail address is being protected from spambots. You need JavaScript enabled to view it