Join us on:


Call for Papers - Due March 19, 2009

It's all about networking and collaboration - whether you are seeking research partners, potential funders, new ideas or perhaps even a new job!

OOPSLA workshops are a great way to grow your knowledge and expand your professional network! They have a global reach and draw diverse groups of technologists from various industry and research organizations around the world who share common interests and passions for advancing the field of software engineering. They are highly interactive events, with ample opportunity to share insights, learn from others and build connections that typically extend well beyond the OOPSLA experience.

Submission Summary
Due date:March 19, 2009
Notification date:
May 15, 2009
Format:ACM Proceedings format
Submit to:OOPSLA submission system
Contact: This e-mail address is being protected from spambots. You need JavaScript enabled to view it (chair)

In the 24 years of OOPSLA Conferences and workshops, there have been many dramatic improvements in software design and development technologies and methodologies. Many of these changes have been nurtured by OOPSLA including UML, Eclipse, distributed objects, agile software development, new programming languages, and Patterns. Workshops have always played an important role at OOPSLA in addressing seminal topics that led to significant advances, especially during their formative stages.

Today, the software world is moving forward at an accelerating pace and the changes in the next 5 years will be more dramatic than the last 25. Explosive new technologies have created many challenging problems - technical, cultural and organizational - that must be solved to support the next generation of software design and development.

If there is a topic about which you feel passionate - and you want to connect with others who have similar interest and passions - consider submitting a proposal to organize an OOPSLA 2009 workshop! The major themes for OOPSLA 2009 are:

  • Scaling: Multi-core to Cloud
  • Mashups of Models, Data and Code
  • Tools for Reliability and Evolution
  • Enterprise Agile Management

Other possible topics for a workshop include, but are not limited to: processes and methods, testing, tools and languages, architecture and design, and collaboration tools and techniques. Some specific examples include: 

  • Languages and tools for multi-core and GPU systems
  • Tools for computer game software development
  • Virtual world application development
  • Agile software development
  • Design and development for cloud computing applications
  • Next-generation computing paradigms (e.g. quantum, biology-inspired)
  • Programming environments for mobile devices
  • Applications for sensor and device networks
  • Programming models, methodologies, and tools for data intensive computing
  • Modeling and simulation of complex systems
  • Computational data understanding applications (e.g. Semantic Web)
  • Globally distributed software development environments
  • Enterprise RESTful and SOA software deployment and operation
  • Programming environments for robotic systems
  • Petascale computing challenges
  • Developing social network and Web 2.0 applications
  • Tools and programming environments for Web rich interface applications (e.g. Ajax)
  • Advanced user interfaces development (e.g. voice, touch, visualization)
  • Software support for "green computing"
  • Software engineering education for the 21st century
  • Industry specific application of emerging technologies (e.g. health care, telecommunications, entertainment, finance, emergency response, education, science, aerospace, environmental)

Submission Guidelines

Workshop proposals are submitted through the OOPSLA on-line submission system.

Your proposal should include the following elements:

  • Main Theme and Goals - The proposal must explain the importance of the workshop theme to the OOPSLA community. Goals should be clearly stated.
  • Abstract - The proposal must include a 150-word abstract that summarizes the theme and goals of the workshop. If the workshop is accepted, this abstract will be published in the advance program and the final program.
  • Organizers - The proposal must list the workshop organizers. Workshop organizers are responsible for advertising the workshop, reviewing potential participants' submissions, running the workshop, and collating any results of the workshop for dissemination to others. Workshop organizers should be listed, together with their contact information. The primary organizer of the workshop and a contact person should be specified (they need not be the same person). For each organizer, the proposal should describe his/her background (expertise in the area, and previous experience running workshops) and also identify his/her responsibilities for this workshop.
  • Anticipated Attendance - The ideal, minimum, and maximum number of participants.
  • Advertisement - Describe how you plan to advertise your workshop to ensure participation.
  • Participant Preparation - Your proposal should describe what preparation is expected of workshop participants.
  • Activities and Format - The format of the workshop should be described and a timetable given. Please state clearly if a full-day or a half-day workshop is proposed. You should consider, for example, whether there will be any introductory material, whether there will be any paper presentations, any panel discussion, debate, or focus groups, and how such groups will report back to the other participants.
  • Post-workshop activities - The proposal should describe what results the workshop will produce and how those will be disseminated to the wider public.
  • Special Requirements - Identify any special requirements.

The following questions may help focus your submission:

  • Are there at least two organizers and do they represent a reasonably varied cross-section of the community?
  • Does the proposal present a compelling case for the importance of the topic area? Is this done succinctly and completely?
  • Are the goals of the workshop expressed clearly?
  • Is the topic likely to be attractive to OOPSLA attendees?
  • Is the format clearly described and does it encourage a high level of interaction between the participants?
  • Is a workshop the right forum to address the theme and goals or does the proposal fit better into another type of OOPSLA event?

For additional information, clarification, or questions please contact the workshops committee chair, Steve Marney, at This e-mail address is being protected from spambots. You need JavaScript enabled to view it

Workshops Committee

  • Steve Marney, EDS an HP company, USA (chair)
  • Bill Opdyke, Motorola, USA
  • Douglas Schmidt, Vanderbilt University, USA
  • Bob Marcus, SRI. USA
  • Doug Lea, State University of New York, USA
  • Jutta Eckstein, Braunschweig University of Technology, Germany
  • Jens Coldewey, Coldewey Consulting (BDU), Germany
Please email any questions to . This e-mail address is being protected from spambots. You need JavaScript enabled to view it