|
Home
PLEES'01
PLEES'02
PLEES'03
Resources
| |
 |
Transitioning Product Line and Component-Based Approaches
to Industrial Practice
International Workshop on Product Line
Engineering
The Early
Steps: Planning, Modeling, and Managing
November 5, 2002,
Seattle / USA  |
|
CALL FOR PAPERS
Product Line (PL) Engineering has become a major topic in industrial
software engineering. It focuses on the development of complete system families as opposed to single systems. PL engineering aims at
efficient and cost-effective development through large-scale reuse by exploiting the family members' commonalities and by controlling their variabilities. Systematic exploitation usually results in a PL infrastructure that enables rapid development of its family
members.
The technical foundation for family-based development techniques has been studied for quite some time now. In product-line practice we often employ component-based approaches and techniques based on OO-frameworks for developing the PL infrastructure. Research in these areas has been very strong. However, in order to be truly successful these implementation-related, down-stream activities need
to be performed in an organizational and technical framework that is
appropriately prepared to support them. This raises organizational issues, issues of PL planning, problems of technology transfer and system migration, as well as issues concerning management of products, requirements, design, and reusable components. These more up-stream activities have not yet seen as much attention in product line research. In this workshop we focus on these early steps in PL engineering
and Component-Based Software Engineering in particular.
Topics
of Interest:
The
goal of this workshop is to bring together practitioners and
researchers from the field to foster a strong exchange of ideas and
experiences. Thus, we strongly invite research papers, experience
reports, and case studies both from industry and academia.
Main
Topics and Questions:
Organizations:
 |
What are characteristics of particularly
effective organizations and processes? |
|
How must an organization be structured to
support product line and component-based engineering? |
|
How does this differ from conventional
organizations? |
|
How can product line development be
integrated in a development organization that previously
performed stovepipe development? |
|
How to determine the best starting point in
terms of functionality or organizational unit? |
Economics:
|
How do we determine the economics of
product line and component based development and use it as a
basis to drive the effort? |
|
How do we select functionality areas to
start with migrating to PL development or wrapping as components? |
|
How do we scope product line and component
based development in order to maximize its pay-off? |
|
How can planning for product lines be
integrated into a company's portfolio planning process? |
Managerial:
|
How do we plan the introduction process? |
|
How do we motivate people for these
approaches? |
|
How do we plan for product line development,
i.e., how do we manage the multi-project (and thus
multi-customer) coordination problems? |
|
How do we manage the refinement of a family
into subfamilies? |
|
How can we cope with the various needs to
adapting and evolving product lines like changing customer
requirements (from individual customers or market needs) or
environment changes (technological progress, legal constraints)? |
|
How do we identify and address product line
specific risks (i.e., risks that are typical for reuse and other
long-term projects)? |
Technology:
|
How can we introduce a product line
incrementally? What ordering of steps should be respected? What
are dependencies among technologies? |
|
How do we identify adequate component and
implementation technologies? |
|
How do we support the efficient elicitation
of product line information? |
|
How can we model the product line
requirements in a way that also supports their efficient
instantiation? |
|
How do we manage the common components so
that they are optimally used and reused during further
development? |
Topics
for papers are not limited to the above-mentioned topics.
In particular industrial experience papers relating to the workshop
topics are sought.
This workshop is planned as a highly interactive forum that aims at
industrial practitioners and researchers alike. Consequently as key
results the workshop aims at a comprehensive list of lessons learned
from industrial practice and a research agenda for increasing our
knowledge on the early steps of product line development.
(top)
Paper Submission:
To participate as presenters, authors should send papers relevant
to one or more of the topics by email to the following address:
plees@iese.fraunhofer.deSubmissions
will be evaluated according to the relevance and originality of the
work and to their ability to generate discussion between the
workshop participants. Papers should be no longer than 6 pages (single-column,
11pt) and submitted as PDF-file.
(top)
Important Dates:
| Submission deadline:
| Notification of acceptance: September 24, 2002
| Camera ready version: October 15, 2002 |
| Workshop presentation: November 5, 2002 |
| |
(top)
Registration, Hotel, Location:
Participants must be registered for OOPSLA.
For registration,
hotel, and other information about the location, see http://oopsla.acm.org.
(top)
Program
Committee:
| Colin Atkinson,
Independent Consultant, Germany |
|
Günter Böckle,
Siemens, Germany |
| Jan Bosch,
University of Groningen, The Netherlands |
| Lars Bratthall,
ABB, Norway |
| Paul Clements, SEI,
USA |
|
John Favaro,
Consulenza Informatica, Italy |
|
Birgit Geppert, Avaya
Labs, USA |
|
Rick Kazman, Software
Engineering Institute, USA |
|
Frank van der Linden,
Philips, The Netherlands |
|
Klaus Schmid,
Fraunhofer IESE, Germany |
| Douglas C. Schmidt,
University of California, Irvine, USA |
| Johannes
Siedersleben, sd&m AG, Germany |
|
Kevin Sullivan,
University of Virginia, USA |
|
Juha-Pekka Tolvanen,
MetaCase Consulting, Finland |
|
David Weiss, Avaya
Labs, USA |
(top)
Workshop
Chairs:
| | |
