Experiences in Software Product Families: Problems and Issues During Product Derivation

Deelstra, Sybren; Sinnema, Marco; Bosch, Jan

doi:10.1007/978-3-540-28630-1_10

Cited by 74 publications

(39 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The case for formal and refinement approaches to SPLE is reinforced by an industrial experience analysis [15] of EU-IST project ConIPF [38], where product-line infrastructure failed to deliver the time and effort savings originally hoped for. In this iterative component-based approach including significant human interaction, it was found that false positives in component selection, human errors in resolving variabilities, unforseen later consequences of early variant selection, problems in resolving provided/required component interfaces were all excessive.…”

Section: Related Work In Contextmentioning

confidence: 99%

Rigorous engineering of product-line requirements: A case study in failure management

Snook

Poppleton

Johnson³

2008

Information and Software Technology

View full text Add to dashboard Cite

We consider the failure detection and management function for engine control systems as an application domain where product line engineering is indicated. The need to develop a generic requirement set -for subsequent system instantiation -is complicated by the addition of the high levels of verification demanded by this safety-critical domain, subject to avionics industry standards. We present our case study experience in this area as a candidate method for the engineering, validation and verification of generic requirements using domain engineering and Formal Methods techniques and tools. For a defined class of systems, the case study produces a generic requirement set in UML and an example system instance. Domain analysis and engineering produce a validated model which is integrated with the formal specification/ verification method B by the use of our UML-B profile. The formal verification both of the generic requirement set, and of a simple system instance, is demonstrated using our U2B, ProB and prototype Requirements Manager tools. This work is a demonstrator for a tool-supported method which will be an output of EU project RODIN 1 . The use of existing and prototype formal verification and support tools is discussed. The method, developed in application to this novel combination of product line, failure management and safety-critical engineering, is evaluated and considered to be applicable to a wide range of domains.

show abstract

Section: Related Work In Contextmentioning

confidence: 99%

Rigorous engineering of product-line requirements: A case study in failure management

Snook

Poppleton

Johnson³

2008

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…Although some case studies describe positive results [ADH + 00, CN02] (sometimes from a general perspective) there is also the awareness that in the presence of tens of thousands of variation points there can be a large number of human errors during product derivation, due to complexity of the models (see case study in [DSB04]). The latter results support the criticism put forward in Sect.…”

Section: Application Designmentioning

confidence: 99%

Product Lines for Digital Information Products

2007

Wirtsch. Inform.

View full text Add to dashboard Cite

“…Since the final goal of SPLs is to enable organizations to deliver quality products within shortened development cycles, we could assume that PD is key to SPL approaches and has been exhaustively studied in order to unleash the full potential of the product-line paradigm. In fact, this was not the case and research [10] has shown that this process can be tedious and error-prone. Therefore, several automated product derivation approaches [44,18,23,19,8] have been proposed to assist product engineers in this task; most of them use model-driven techniques to derive products according to choices made by product engineers on the basis of a decision model.…”

Section: Introductionmentioning

confidence: 99%

Reconciling Automation and Flexibility in Product Derivation

Perrouin

Klein

Guelfi

et al. 2008

2008 12th International Software Product Line Conference

View full text Add to dashboard Cite

Product derivation, i.e. reusing core assets to build products, did not receive sufficient attention from the productline community, yielding a frustrating situation. On the one hand, automated product derivation approaches are inflexible; they do not allow products meeting unforeseen, customer-specific, requirements. On the other hand, approaches that consider this issue do not provide adequate methodological guidelines nor automated support.This paper proposes an integrated product derivation approach reconciling the two views to offer both flexibility and automation. First, we perform a pre-configuration of the product by selecting desired features in a generic feature model and automatically composing their related product-line core assets. Then, we adapt the pre-configured product to its customer-specific requirements via derivation primitives combined by product engineers and controlled by constraints that flexibly set product line boundaries. Our process is supported by the Kermeta metamodeling environment and illustrated through an example.

show abstract

Experiences in Software Product Families: Problems and Issues During Product Derivation

Cited by 74 publications

References 15 publications

Rigorous engineering of product-line requirements: A case study in failure management

Rigorous engineering of product-line requirements: A case study in failure management

Product Lines for Digital Information Products

Reconciling Automation and Flexibility in Product Derivation

Contact Info

Product

Resources

About