Managing Variability in Software Product Lines
Published 1 January 2000
Jilles van Gurp, Jan Bosch, Mikael Svahnberg
Citations158
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
A conceptual framework of terminology for the concept of variability is provided and how variability can be managed in Software Product Lines is discussed.
Abstract
Software Product Lines are large systems intended for reuse in concrete products. As such these large systems provide reusable architecture and implementation that the individual products have in common. The differences between the product are left open. We refer to these open spots as variability points. In this article we provide a conceptual framework of terminology for the concept of variability and we discuss how variability can be managed in Software Product Lines.
Keywords
Computer Science
Design Patterns: Elements of Reusable Object-Oriented Software
21,864 Citations1994Erich Gamma, Richard F. Helm +2 more
The book is an introduction to the idea of design patterns in software engineering, and a catalog of twenty-three common patterns, which most experienced OOP designers will find out they've known about patterns all along.
Component software beyond object oriented programming
4,644 Citations2002Clemens Szyperski
Anyone responsible for developing software strategy, evaluating new technologies, buying or building software will find Clemens Szyperski's objective and market-aware perspective of this new area invaluable.
Feature-Oriented Domain Analysis (FODA) Feasibility Study
4,194 Citations1990Kyo C. Kang, Sholom Cohen +3 more
This report will establish methods for performing a domain analysis and describe the products of the domain analysis process, and provide a domain analysis of window management system software.
Medical Entomology and ZoologyDesign and Use of Software Architectures: Adopting and Evolving a Product-Line Approach
1,172 Citations2000Jan Bosch
This chapter discusses Software Architecture and Product Lines and the design of Software Architectures and its transformation into Family-Based System Development.
Journal of Object-oriented ProgrammingDesigning reusable classes
1,133 Citations1988Ralph E. Johnson, Brian Foote
This paper describes what it is like to design systems in Smalltalk and how classes are developed so that they will be reusable.
Software reuse architecture, process, and organization for business success
931 Citations2002Martin Griss
Hewlett-Packard's software reuse practice and adoption experience, and a systematic approach to component-based software engineering based on object-oriented business and system modeling are described.
ACM Transactions on Software Engineering and MethodologyFour dark corners of requirements engineering
727 Citations1997Pamela Zave, Michael Jackson
It is shown that all descriptions involved in requirements engineering should be descriptions of the environment, and certain control information is necessary for sound requirements engineering, and the close association between domain knowledge and refinement of requirements is explained.
ACM Transactions on Software Engineering and MethodologyThe design and implementation of hierarchical software systems with reusable components
605 Citations1992Don Batory, Sean O’Malley
A domain-independent model of hierarchical software system design and construction that is based on interchangeable software components and large-scale reuse that is a blueprint for achieving software component technologies in many domains is presented.
Integrating feature modeling with the RSEB
485 Citations2002Martin Griss, John Favaro +1 more
Journal of Software Maintenance Research and PracticeEvolution in software product lines: two cases
119 Citations1999Mikael Svahnberg, Jan Bosch
Three types of lessons learned about evolution in software product lines are learned: three evolution categories are predominant, three other categories are less significant but still common, and seven guidelines for software product-line evolution emerge.
Lecture notes in computer scienceImplementing Product-Line Features with Component Reuse
106 Citations2000Martin Griss
This paper outlines a proposed path from the set of common and variable features supporting a product-line, to the reusable elements to be combined into customized feature-oriented components and frameworks to implement the products.
Product-line architectures in industry
103 Citations1999Jan Bosch
A case study investigating the experiences from using product-line architectures is presented involving two Swedish companies, Axis Communications AB and Securitas Larm AB, and identifies a collection of problems and issues.
Lecture notes in computer scienceDevelopment and Evolution of Software Architectures for Product Families
89 Citations1998Frank van der Linden
The paper presents a so-called COMSOFT framework of communication software development model based on object oriented architecture and design patterns that supports reuse in all phases of the development process and is intended to be generic with respect to the family of telecontrol protocols.
Journal of Systems and SoftwareInvestments in reusable software. A study of software reuse investment success factors
63 Citations1998David C. Rine, Robert Michael Sonnemann
This research supports the thesis that there is a set of success factors which are common across organizations and have some predictability relationships to software reuse and investigates if software reuse had a predictive relationship to productivity and quality.
FIWFeature Requirements Models: Understanding Interactions.
48 Citations1997John P. Gibson
This paper states that many of the problems which arise when features combine are due to badly developed requirements models for individual features, and shows how good requirements models could resolve the problems that arise when combining features.
Information and Software TechnologyAn empirical study of a software reuse reference model
45 Citations2000David C. Rine, Nader Nada
The research thesis is that software development based on a software reuse reference model improves the competitive edge and time-to-market of many software development enterprises.
IFIP advances in information and communication technologyEvolution and Composition of Reusable Assets in Product-Line Architectures: A Case Study
44 Citations1999Jan Bosch
A case study investigating the experiences from evolution and modification of reusable assets in product-line architectures is presented involving two Swedish companies, Axis Communications AB and Securitas Larm AB, identifying problems related to multiple versions of reusable Assets, dependencies between assets and the use of assets in new contexts.
Characterizing Evolution in Product Line Architectures
18 Citations1999Mikael Svahnberg, Jan Bosch
This paper develops categorizations for the evolution of requirements, the product-line architecture and product- line architecture components and analyzes and presents the relations between these categorizations.
Lecture notes in computer scienceAn Integral Hierarchy and Diversity Model for Describing Product Family Architectures
5 Citations1998P. van den Hamer, Frank van der Linden +2 more
This paper presents a model which can be used to describe and manage architectures in a number of product family-oriented design processes and believes that the use of such models can promote the overall optimisation of product families and can facilitate validation of architectural decisions.