Design and use of software architectures - adopting and evolving a product-line approach

By Jan Bosch. 2000

1,421 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/6d41ef098cbe439a33535ce1a2399d2cec7508c1

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

Formalizing cardinality-based feature models and their specialization (2005, background): “Later, feature models play a central role in the development of a system family architecture, which has to realize the variation points specified in the feature models (Czarnecki and Eisenecker, 2000; Bosch, 2000).”
An Overview of Feature-Oriented Software Development (2009, background): “Bosh [35]: “a logical unit of behaviour specified by a set of functional and non-functional requirements””
Staged configuration through specialization and multilevel configuration of feature models (2005, background): “In product-line design, the points and ranges of variation captured in feature models need to be mapped to a common product-line architecture (Czarnecki and Eisenecker, 2000; Bosch, 2000).”
A taxonomy of variability realization techniques (2005, methodology): “rather large field of research (see for example Reference [3] or [ 4 ]), but it is outside of the scope of this paper to investigate it”
Variability management in software product lines: a systematic review (2009, background): “Software Product Line Engineering (SPLE) intends to develop software-intensive systems using platforms and mass customisation [1] [2].”
Staged Configuration Using Feature Models (2004, background): “Later, feature models play a central role in the development of a system family architecture, which has to realize the variation points specified in the feature models [2, 3].”
On the notion of variability in software product lines (2001, background): “In this section we suggest that features are a useful abstraction for doing so. In [ 5 ], we define features as follows: “a logical unit of behavior that is specified by a set of functional and quality requirements “. The point of view taken in this book is that a feature is a construct used to grou”
Feature-Oriented Software Product Lines (2013, unknown): “Another collection of books is concerned with techniques to implement software product lines, including generative programming (Czarnecki and Eisenecker 2000), software architecture (Bosch 2000), aspect-oriented, and model-driven engineering (Rashid et al.”
A survey on engineering approaches for self-adaptive systems (2015, background): “, [40], [43], [54], [52], [55], [56], [57], [58]).”