scispace - formally typeset
Search or ask a question
Author

Günter Böckle

Bio: Günter Böckle is an academic researcher from Siemens. The author has contributed to research in topics: Software product line & Software development. The author has an hindex of 10, co-authored 17 publications receiving 2199 citations.

Papers
More filters
Journal ArticleDOI
TL;DR: This software product line cost model can calculate the costs and benefits (and hence the ROI) that the authors can expect to accrue from various product line development situations.
Abstract: Product line engineering has become an important and widely used approach for efficiently developing portfolios of software products. The idea is to develop a set of products as a single, coherent development task from a core asset base (sometimes called a platform), a collection of artifacts specifically designed for use across a portfolio. This approach produces order-of-magnitude economic improvements compared to one-at-a-time software system development. Because the product line approach isn't limited to specific technical properties of the planned software but rather focuses on economic characteristics, high return on investment has become the anthem of the approach's protagonists. Our software product line cost model can calculate the costs and benefits (and hence the ROI) that we can expect to accrue from various product line development situations. It's also straightforward and intuitive.

182 citations

Book ChapterDOI
19 Aug 2002
TL;DR: How to perform the transition to product line engineering and the various strategies for such a transition are described and an adoption plan and how to institutionalize product line Engineering in an organization are described.
Abstract: The strengths of product line engineering have been described before. But how can an organization make the move from developing one-of products to product line engineering without major interruptions in the day-today work? This paper describes how to perform the transition to product line engineering and lists the various strategies for such a transition. It also describes how to create an adoption plan and how to institutionalize product line engineering in an organization.

44 citations

Journal Article
TL;DR: A first-order cost model is presented that describes the costs associated with developing products in a product line organization and addresses a number of issues that are addressed as a set of scenarios.
Abstract: In this paper we present a first-order cost model that describes the costs associated with developing products in a product line organization. The model addresses a number of issues that we present as a set of scenarios. The goal of this work is to develop models of varying granularity that support a manager's decision-making needs at a variety of levels. The basis of these models is the relationships among the artifacts of the product line.

34 citations

Book ChapterDOI
03 Oct 2001
TL;DR: This paper formulates and discusses 7 hypotheses on how the promised advantages would look like in a quantitative way and is meant to be a starting point for discussion on how to quantify which product line benefits and how they can be measured.
Abstract: Software product lines promise benefits like development and maintenance effort reduction, time to market decrease, and quality improvement, all resulting from planned and systematic reuse of common core assets. However, very little quantitative data has been measured so far to prove these promises. This paper formulates and discusses 7 hypotheses on howthe promised advantages would look like in a quantitative way. It is meant to be a starting point for discussion on how to quantify which product line benefits and how they can be measured.

33 citations


Cited by
More filters
Book
01 Jan 2004
TL;DR: The confluence of component based development, model driven development and software product lines forms an approach to application development based on the concept of software factories, which promises greater gains in productivity and predictability than those produced by incremental improvements to the current paradigm of object orientation.
Abstract: The confluence of component based development, model driven development and software product lines forms an approach to application development based on the concept of software factories. This approach promises greater gains in productivity and predictability than those produced by incremental improvements to the current paradigm of object orientation, which have not kept pace with innovation in platform technology. Software factories promise to make application assembly more cost effective through systematic reuse, enabling the formation of supply chains and opening the door to mass customization.

784 citations

Journal ArticleDOI
TL;DR: The AHEAD (algebraic hierarchical equations for application design) model is presented, that shows how step-wise refinement scales to synthesize multiple programs and multiple noncode representations, and a tool set that supports AHEAD is reviewed.
Abstract: Step-wise refinement is a powerful paradigm for developing a complex program from a simple program by adding features incrementally. We present the AHEAD (algebraic hierarchical equations for application design) model that shows how step-wise refinement scales to synthesize multiple programs and multiple noncode representations. AHEAD shows that software can have an elegant, hierarchical mathematical structure that is expressible as nested sets of equations. We review a tool set that supports AHEAD. As a demonstration of its viability, we have bootstrapped AHEAD tools from equational specifications, refining Java and nonJava artifacts automatically; a task that was accomplished only by ad hoc means previously.

776 citations

Journal ArticleDOI
TL;DR: A theoretical model that centres on two drivers behind boundary resources design and use – resourcing and securing – and how these drivers interact in third‐party development is proposed and applied to a detailed case study of Apple's iPhone platform.
Abstract: Prior research documents the significance of using platform boundary resources e.g. application programming interfaces for cultivating platform ecosystems through third-party development. However, there are few, if any, theoretical accounts of this relationship. To this end, this paper proposes a theoretical model that centres on two drivers behind boundary resources design and use - resourcing and securing - and how these drivers interact in third-party development. We apply the model to a detailed case study of Apple's iPhone platform. Our application of the model not only serves as an illustration of its plausibility but also generates insights about the conflicting goals of third-party development: the maintenance of platform control and the transfer of design capability to third-party developers. We generate four specialised constructs for understanding the actions taken by stakeholders in third-party development: self-resourcing, regulation-based securing, diversity resourcing and sovereignty securing. Our research extends and complements existing platform literature and contributes new knowledge about an alternative form of system development.

646 citations

Proceedings ArticleDOI
11 Sep 2006
TL;DR: In this paper, a formal semantics for feature diagrams is defined at the free feature diagrams (FFD) level, which provides unambiguous definition for all the surveyed feature diagrams variants in one shot.
Abstract: Feature diagrams (FD) are a family of popular modelling languages used for engineering requirements in software product lines. FD were first introduced by Kang as part of the FODA (feature oriented domain analysis) method back in 1990, Since then, various extensions of FODA FD were devised to compensate for a purported ambiguity and lack of precision and expressiveness. However, they never received a proper formal semantics, which is the hallmark of precision and unambiguity as well as a prerequisite for efficient and safe tool automation, In this paper, we first survey FD variants. Subsequently, we generalize the various syntaxes through a generic construction called free feature diagrams (FFD). Formal semantics is defined at the FFD level, which provides unambiguous definition for ail the surveyed FD variants in one shot. All formalisation choices found a clear answer in the original FODA FD definition, which proved that although informal and scattered throughout many pages, it suffered no ambiguity problem. Our definition has several additional advantages: it is formal, concise and generic. We thus argue that it contributes to improve the definition, understanding, comparison and reliable implementation of FD languages

459 citations

Journal ArticleDOI
TL;DR: A classification of product-line analyses is proposed to enable systematic research and application in software-product-line engineering and develops a research agenda to guide future research on product- line analyses.
Abstract: Software-product-line engineering has gained considerable momentum in recent years, both in industry and in academia. A software product line is a family of software products that share a common set of features. Software product lines challenge traditional analysis techniques, such as type checking, model checking, and theorem proving, in their quest of ensuring correctness and reliability of software. Simply creating and analyzing all products of a product line is usually not feasible, due to the potentially exponential number of valid feature combinations. Recently, researchers began to develop analysis techniques that take the distinguishing properties of software product lines into account, for example, by checking feature-related code in isolation or by exploiting variability information during analysis. The emerging field of product-line analyses is both broad and diverse, so it is difficult for researchers and practitioners to understand their similarities and differences. We propose a classification of product-line analyses to enable systematic research and application. Based on our insights with classifying and comparing a corpus of 123 research articles, we develop a research agenda to guide future research on product-line analyses.

444 citations