|
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
September
23, 2003, Erfurt / Germany |
|
CALL FOR PAPERS
Product
Line (PL) Engineering has become a major topic in industrial
software engineering. While traditional software engineering
approaches aim at the development of individual systems,
product-line development focuses on the development of complete
system families by exploiting the family members' commonalities and
by controlling their variabilities. PL has been reported to provide
relevant time-to-market, cost, and quality benefits.
Key
to the successful development of product lines are the early steps
like organizational issues, issues of PL planning, as well as issues
concerning requirements modeling and management in the context of
product lines.
The
goal of this workshop is to bring together practitioners and
researchers from the field to foster a strong exchange of ideas and
experiences. Topics of interest include but are not restricted to:
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:
 |
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?
|
|
How
do we scope product line and component based development in
order to maximize its pay-off?
|
|
How
do we motivate people for these approaches?
|
|
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
can we introduce a product line incrementally?
|
|
How
can we model the product line requirements in a way that also
supports their efficient instantiation?
|
|
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 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.
As
a basis for the discussion of these issues four typical,
experience-based scenarios for product line introduction have been
described. (You will find a detailed scenario description, if you
follow the links)
|
Green
Field - Product Lines can evolve directly, without any
previous product development |
|
Integrating
- Existing, independent product development can be integrated
into a single product line |
|
Reengineering-Based
- Based on a legacy system a new product line can be created |
|
Leveraged
- Based on a previous product line a product line infrastructure
for a new product line can be created |
Each position
paper is required to relate itself to one of these scenarios and
identify:
| the main
problems in product line adoption / evolution
|
| the
main advantages of the proposed approach in relation to the
overall scenario. |
It is the aim of the workshop to derive a key list of
research questions and lessons learned relative to typical product
line adoption situations. This will be done by a mixture of
presentations, plenary discussion sessions, and break out groups.
(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 to their ability to generate discussion between the
workshop participants. The relationship to a specific adoption
situation is also a key evaluation criterion. Papers should be no longer than 6 pages (single-column,
11pt) and submitted as PDF-file.
(top)
Important Dates:
| Workshop presentation: September 23, 2003 |
(top)
Registration, Hotel, Location:
Participants must be registered for GPCE.
For registration,
hotel, and other information about the location, see http://gpce.org/GPCE03/.
(top)
Program
Committee:
|
Günter Böckle, Siemens, Germany |
|
Paul Clements, SEI, USA |
|
Birgit Geppert, Avaya Labs, USA |
|
Erik Kamsties,
University Duisburg-Essen |
|
Julio Leite, PUC-Rio |
|
Frank Rössler, Avaya
Labs, USA |
|
Klaus Schmid, Fraunhofer IESE,
Germany |
(top)
Workshop
Chairs:
|
| | | |
