This material is being posted by Carnegie Mellon University's Software Engineering Institute (SEI) on this Web site as a community service.


The First Software
Product Line Conference

Conference Workshops

Important: Workshop Attendance Criteria

SPLC Logo
Monday, August 28
{short description of image} Combining Architecture, Asset Management, and Culture to Successfully Develop Product Lines
{short description of image} Product Line Architecture
{short description of image} Architecture Reconstruction and Product Lines
{short description of image} Measurement Issues for Software Product Line Engineering
Tuesday, August 29
{short description of image} Generative Techniques for Product Lines
{short description of image} Product Lines for Command-and-Control Ground Systems
{short description of image} Embedded System Product Lines
{short description of image}

Combining Architecture, Asset Management, and Culture to Successfully Develop Product Lines

A product line development solution (PLDS) consists of three aspects: an architecture, a software asset management strategy and a social/organizational structure. To be successful at moving from a product focused development paradigm to a product line focused paradigm it is important to design all three elements of the PLDS to match the business situation (business needs, technology, and culture). Each of the three elements has valid solutions that differ greatly. Architectures can vary from a highly optimized code set to a highly decoupled code set. Asset management can vary from a central group control to an open source model. Organization strategies can vary from reuse group focused to project focused.

We believe that there has been much exploration and progress in each of the three elements of the PLDS, but there has been little focus or discussion on how the three elements need to be combined to provide a successful approach for various business situations. This workshop will focus on the full solution instead of any one element.

Prospective workshop participants are required to submit a 2 - 3 page position paper describing either:

We will select the participants based on the quality and relevance of their position papers. We will limit the number of participants to 15, and the number of presentations to 5

Workshop Organizers:
Phil McCoog (primary contact)
Hewlett Packard, Vancouver Division
+1 (360) 212-8296
phil_mccoog@hp.com
Joe Bauman
Hewlett Packard, Vancouver Division
+1 (360) 212-2749
joe_bauman@hp.com

Product Line Architecture

A product-line architecture must adequately capture and support the description of commonalities and variabilities in the solutions. However this is not enough; variation points in the architecture, for example, are not sufficient to support the decisions that lead to a particular choice of variant. A decision model, the decisions and the relationships among them, defines a set of decisions that are adequate to distinguish among members of application family and to guide adaptation of adaptable architecture and its components. The objective of this workshop will be to investigate potential technologies necessary to support the derivation of architecture variants. Two main focus areas will be addressed:

Workshop Organizers:
Jean Jourdan (primary contact)
Thomson-CSF/LCAT
Domaine de Corbeville
91404 ORSAY France
Phone: +33 (1) 69 33 09 18
FAX : +33 (1) 69 33 08 65
jourdan@lcr.thomson-csf.com
Michel Coriat
Thomson-CSF/LCAT
Domaine de Corbeville
91404 ORSAY France
Phone: +33 (1) 69 33 07 76
FAX : +33 (1) 69 33 08 65
coriat@lcr.thomson-csf.com
Dr Cristina Gacek
Fraunhofer Institute for Experimental
Software Engineering (IESE)
Sauerwiesen 6
D-67661 Kaiserslautern Germany
Phone: +49 (6301) 707-224
FAX: +49 (6301) 707-200
Cristina.Gacek@iese.fhg.de

Architecture Reconstruction and Product Lines

This workshop will focus on architecture reconstruction in product line contexts. In most cases product lines evolve out of existing products. To manage the evolution in a disciplined way organizations have to 'mine' existing assets for architecture, commonalities, and varieties. Reconstruction focuses in most cases on an abstraction of at least a few components and interactions to present an understandable structure. But this focus is not sufficient in the context of product lines. To detect reusable components and varieties for a potential product line migration there are further challenges: (1) The reconstruction process should be applied to at least one further product and (2) the analyst has to find a useful abstraction level to detect and describe the commonalities and varieties. Summarized the objectives of this workshop are:

Participants are invited to submit a position paper with a contribution on one or more of the objectives. The workshop will consist of presentations of these papers in the morning session, followed by an afternoon session of discussion and collaboration.

Workshop Organizers:
Christoph Stoermer (primary contact)
Robert Bosch Corp.
Research and Technology Center
+1 412-268 3949
cstoerme@sei.cmu.edu
William O'Brien
Software Engineering Institute
+1 412-268 7727
lob@sei.cmu.edu

Measurement Issues for Software Product Line Engineering

Effective management and improvement of software development requires the support of a good measurement system. While measurement for software engineering is not new, it appears that measurement in support of a product line approach to software engineering does pose some unique challenges. This workshop will identify and discuss:

Much work and guidance exists on software measurement. More recently, measurement in support of software reuse has appeared in the literature. The concept of a product line approach to software development is still evolving, however, and little work has been done to date to describe the measures and measurement practices that are needed to efficiently and effectively manage and improve a software product line operation.

For measurement to be useful and effective, it needs to support action and decision-making. In the operation of a software product line, there are at least distinct managerial roles to be addressed: the overall product line operation, asset development and management, and application development and maintenance. We will investigate the scope and responsibilities of the managerial roles and the characteristics of a measurement system that supports these roles.

Prospective workshop participants should submit a 2 - 3 page position paper describing their experiences with software product line management and/or measurement. We will select the participants based on the quality and relevance of their position papers. We will limit the number of participants to 15, and the number of presentations to 5.

Workshop Organizers:
Dave Zubrow (primary contact)
Software Engineering Institute
+1 412-268-5243
dz@sei.cmu.edu
Grady Campbell
gradycampbell@acm.org
Wolf Goethert
Software Engineering Institute
+1 412-268-3889
wbg@sei.cmu.edu

Generative Techniques for Product Lines

The workshop on Generative Techniques for Product Lines aims to bring together practitioners, researchers, academics, and students to discuss broadly the state-of-the-art of generators and their role in developing a product line. Topics of interest, include:

The goal is to share experience, consolidate successful techniques, and identify open issues for future work in product lines.

Potential participants are asked to submit a two-page position paper detailing their experience with generative techniques, their perspective on one or more of the above topics, and their planned contribution to the workshop. Based on the position papers, the organizers will invite a cross-section to participate.

Workshop Organizers:
Greg Butler (primary contact)
Concordia University, Montreal
gregb@cs.concordia.ca
Krzysztof Czarnecki
Software Technology Lab
DaimlerChrysler Research, Ulm
czarnecki@acm.org
Ulrich Eisenecker
University of Applied Sciences
Kaiserslautern
Ulrich.Eisenecker@t-online.de

Product Lines for Command-and-Control Ground Systems

This workshop will address issues relating to implementation of product lines for C2 ground systems. Although the focus is not exclusively on C2 ground systems for spacecraft, discussions will begin with that domain, since the organizers of this workshop have also been organizers of the Ground System Architectures Workshops (GSAW), which have drawn their attendees primarily from the spacecraft C2 domain. Issues relating to command-and-control ground systems in other domains will also be addressed in this workshop, especially with regard to how they are similar to and different from issues in the spacecraft ground systems domain.

This workshop will begin with a focus on the following issues in the context of command-and-control ground systems:

Prospective workshop participants should submit a 1 - 2 page position paper describing their experiences with software product lines for command-and-control ground systems. The participants will be selected based on the quality and relevance of their position papers.

Workshop Organizer:
Judy Kerner
The Aerospace Corporation
MS M1/113 POB 92957
Los Angeles, CA 90009
+1 (310) 336-6555
Judy.Kerner@aero.org

Embedded System Product Lines

A product line is a group of products sharing a common, managed set of features that satisfy specific needs of a selected market. Once a product line has been developed, managing the product line to balance core and application specific content and changes can be challenging. As new product requests are encountered, requirements need to be compared with current core content to determine if the product should be added to the product line and which parts should be added to the core and which parts should be application specific. The organizational structure must be in place to facilitate these decisions. Application teams should not have too many resources or too much freedom to make application specific changes or else core product line assets won't be used effectively. As the product gets closer to production, there will be a need to freeze the content for an individual application. This means the same change may need to be made for a specific application and later in the core so that when the application takes a future core release the content will be included. A strategy needs to be in place for coordinating core and application releases throughout the product line life-cycle.

The workshop is focused on managing the product line once it has been developed. The problems to be addressed include:

Prospective workshop participants are required to submit a 2 - 3 page position paper describing their experiences with software product line analysis in this field. We will select the participants based on the quality and relevance of their position papers. We will limit the number of participants to 15, and the number of presentations to 5.

Workshop Organizers:
Kathy Rose (Primary Contact)
+1 (248) 684-3726
krose01@powertrain.mpg.gm.com
Jim Kolhoff
+1 (810) 220-2595
jkolho01@powertrain.mpg.gm.com
Jim Kurnik
+1 (810) 220-2458
jkurni01@powertrain.mpg.gm.com

Workshop Attendance

Workshops are by invitation only. Each workshop may have its own invitation criteria. The most likely criteria for attendance will be the submission and acceptance of a workshop paper. Workshop papers tend to be much less formal and comprehensive than main-conference papers.

If you are interested in attending a specific workshop, please follow the invitation criteria provided with the workshop and contact the workshop organizer(s).


The SEI is a federally funded research and development center sponsored by
the U.S. Department of Defense and operated by Carnegie Mellon University.

Copyright ©2000 by Carnegie Mellon University