Call for Papers
for the
1st Workshop on Software Development Process Patterns (SDPP'02)
(PDF-Version, Text-Version)

to be held at the 
17th Annual ACM Conference on Object-Oriented Programming,
Systems, Languages, and Applications (OOPSLA 2002)
Seattle, Washington, USA, November 4-8, 2002

(http://oopsla.acm.org/)

Themes and Goals
Industrial software engineers need a flexible and modular process model that enables them to combine the benefits of existing process models, methods, techniques, and best practices in a project-specific way. To devise such a process model, a comprehensive and clear notion of software development processes and the corresponding process artifacts is required. Over the last years, we have been working on the concept of process patterns. The underlying meta model and the corresponding description techniques provide a common understanding of all kinds of software development processes and their artifacts, respectively.

The workshop harvests best practices, techniques, methods, and development process fragments presented as software development process patterns. The purpose of this workshop is then to combine and relate these patterns, thus making a first step towards a comprehensive process pattern language. This language will be based on a common software development process framework, and it will include methodical guidelines on the selection of the appropriate process pattern for a specific situation.

Our mid- and long-term goal is to continually evolve the language in order to gain a general basis for the integration, communication, and evolution of process knowledge from different software engineering communities. The workshop may thus result in the establishment of an international community for software development processes based on process patterns. The interest of this community will be to collect, document, and improve software engineering and development process knowledge.

Topics
The workshop will elicit submissions of a large range of established best practices, techniques, methods, and development process fragments to support the software development process.

To ease communication among the participants, submissions are recommend to be documented as a process patterns. For this, a process pattern template, a sample process pattern, and a rough sketch of a conceptual framework for process patterns are provided at the workshop’s website (http://www.forsoft.de/zen/sdpp02/). Ideally, a paper might also reflect about the template or framework that was used to document a process pattern and argue why it is appropriate or not.

Besides a sound description of the proposed process pattern(s) itself, the paper should also discuss why the presented process fragment is a good candidate for a process pattern. This comprises a discussion of how the proposed pattern can be reused in different development processes and how it could possibly be combined with other patterns.

Topics that are relevant to the workshop are, guidelines, best practices, experience reports, techniques, methods, or development process fragments that describe how to be better in:

• teamwork and collaboration
• project management and planning
• requirements engineering and business analysis
• design, modeling, using tools, elaborating documentation
• using UML and other notations
• programming
• testing
• quality assurance
• redesign and refactoring
• customers and contracts
• cost estimation and measurement
• other software development process relevant topics

During the workshop the authors will present their papers and answer questions that relate directly to their presentation. Subsequently, the participants will discuss how the presented patterns may fit into a common process pattern language and how a process pattern framework must look like to provide an appropriate base for such a pattern language.

The main goal of the workshop is to establish an ongoing discussion on process patterns and thereby to agree on an appropriate conceptual framework for these patterns to enhance flexibility and evolution of software development processes.

Submissions
Paper submission is required for participation in the workshop. Submission deadline is the 19th September 2002. Papers should not exceed a length of 10 - 15 pages. Authors are invited to send their papers to the organizers of the workshop (mailto:sdpp@in.tum.de) in Postscript or PDF format. All submitted papers will be peer-reviewed by a minimum of three people.

The accepted papers will be published on the workshop website already before the workshop. Workshop proceedings including all papers will be published as Technical Report of the Technische Universität München.

Workshop Organization

Chairs

• Klaus Bergner, 4Soft GmbH, Germany
• Philippe Kruchten, Rational Software, Canada
• Andreas Rausch, Technische Universität München, Germany

Organizing Committee

• Michael Gnatz, Technische Universität München, Germany
• Frank Marschall, Technische Universität München, Germany
• Gerhard Popp, Technische Universität München, Germany
• Wolfgang Schwerin, Technische Universität München, Germany

Program Committee

• Scott Ambler, Ronin International, Colorado, USA
• Klaus Bergner, 4Soft GmbH, Germany
• Barry Boehm, USC Center for Software Engineering, USA
• Manfred Broy, Technische Universität München, Germany
• Michael Gnatz, Technische Universität München, Germany
• Hajimu Iida, Nara Institute of Science and Technology, Japan
• Philippe Kruchten, Rational Software, Canada
• Frank Marschall, Technische Universität München, Germany
• Jürgen Münch, Fraunhofer Institut, Germany
• Gerhard Popp, Technische Universität München, Germany
• Rodrigo Quites Reis, Universidade Federal do Pará, Brazil
• Andreas Rausch, Technische Universität München, Germany
• Dieter Rombach, Fraunhofer Institut, Germany
• Wolfgang Schwerin, Technische Universität München, Germany
• Louise Scott, University of New South Wales, Australia

Important Dates

• September, 19th 2002 Submission Deadline
• October, 10th 2002 Notification of Acceptance
• November, 4th -8th, 2002 OOPSLA’02
• November, 5th 2002 1st Workshop on Software Development Process Patterns