skip to main content
10.1145/1808937acmconferencesBook PagePublication PagesicseConference Proceedingsconference-collections
PLEASE '10: Proceedings of the 2010 ICSE Workshop on Product Line Approaches in Software Engineering
ACM2010 Proceeding
Publisher:
  • Association for Computing Machinery
  • New York
  • NY
  • United States
Conference:
ICSE '10: 32nd International Conference on Software Engineering Cape Town South Africa 2 May 2010
ISBN:
978-1-60558-968-8
Published:
02 May 2010
Sponsors:
SIGSOFT, IEEE CS
Next Conference
Bibliometrics
Skip Abstract Section
Abstract

Software Product Line Engineering (SPLE) is an engineering technique for creating a portfolio of similar systems from a shared set of software assets. It capitalizes on identifying commonalities and points of variability across the portfolio and promotes strategic software reuse. Organizations that adopt SPLE are able to achieve significant improvement in development and maintenance costs, time-to-market, portfolio size, and quality.

The main goal of PLEASE 2010 is to explore new ways for making SPLE more approachable to software practitioners from all segments of the industry, thus broadening its adoption. It seeks to tear down barriers by allowing the SPLE community to share its ideas regarding approaches, techniques, and tools with the broader software engineering community.

In addition, the workshop designates Beyond Traditional Product Lines as a special theme. Traditional SPLE approaches rely on the basic assumptions that (a) the scope of the product line is clearly defined in advance and stays relatively stable and (b) SPLE activities are mainly performed within and controlled by one organization. These assumptions fall apart as soon as the product line starts to evolve or the SPLE value chains extend across organizational boundaries. PLEASE 2010 aims to investigate the implications of such cases on SPLE practices.

Skip Table Of Content Section
research-article
Opening up software product line engineering

The software industry is experiencing a shift towards more open processes, a globalized market and more active and engaged customers and end users. This change seems natural and inevitable, imposing necessary changes in how software product line ...

research-article
Integrating heterogeneous components in software supply chains

Numerous software product lines today are built from components supplied by different vendors. Companies situated in the middle of a software supply chain must configure and integrate components from their suppliers and offer (partially configured) ...

research-article
An experience report on the incremental adoption and evolution of an SPL in eHealth

This work presents an experience report on the evolutionary development of a software product line (SPL) in the eHealth domain. The effort was triggered by the concurrent development of two similar products and the ambition to reduce redundant ...

research-article
EvoFM: feature-driven planning of product-line evolution

Companies successfully applying product line approaches often follow a long-term strategy and need to plan product portfolios years ahead. For instance in the automotive industry, managers constantly make decisions about future product evolution, like "...

research-article
Software product line evolution: the Selecta system

The current technology gives little room for the different kinds of evolution needed for any software product line (SPL): evolution of the associated engineering environment, evolution of the market and SPL scope, evolution of the products and ...

research-article
SPLGraph: towards a graph-based formalism for software product lines

This paper presents SPLGraph a graph-based model for Software Product Lines, including (1) a formal definition; (2) an algorithm that applies configuration decisions to an SPLGraph thus yielding a product specific graph; (3) a set of patterns for ...

research-article
Feature link propagation across variability representations with Isabelle/HOL

When dealing with highly complex product lines it is usually indispensable to somehow subdivide the overall product line into several smaller, subordinate product lines and to define orthogonal views on the line's variability tailored to particular ...

research-article
Information needed for architecture decision making

This paper focuses on the business aspects of architecture decision making -- in particular information needed by managers and architects for making architecture investment decisions. We present the results of 19 interviews in an industrial organization ...

Contributors
  • The University of British Columbia
  • Science Foundation Ireland
  • Technical University of Darmstadt
  • IBM Research
  • University of Limerick

Recommendations