Easing the Transition to Software Mass Customization

Krueger, Charles W.

doi:10.1007/3-540-47833-7_25

Cited by 190 publications

(171 citation statements)

References 1 publication

Supporting

Mentioning

134

Contrasting

Unclassified

Order By: Relevance

“…There are several approaches for developing software Product Lines (PL) [10]: proactive, reactive, and extractive [18]. In the proactive approach, the organization analyzes, designs, and implements a fresh PL to support the full scope of products needed on the foreseeable horizon.…”

Section: Introductionmentioning

confidence: 99%

Extracting and Evolving Code in Product Lines with Aspect-Oriented Programming

Alves

Matos

Cole

et al. 2007

Transactions on Aspect-Oriented Software Development IV

View full text Add to dashboard Cite

Abstract. For some organizations, the proactive approach to product lines may be inadequate due to prohibitively high investment and risks. As an alternative, the extractive and the reactive approaches are incremental, offering moderate costs and risks, and therefore sometimes may be more appropriate. However, combining these two approaches demands a more detailed process at the implementation level. This paper presents a method and a tool for extracting a product line and evolving it, relying on a strategy that uses refactorings expressed in terms of simpler programming laws. The approach is evaluated with a case study in the domain of games for mobile devices, where variations are handled with aspect-oriented constructs.

show abstract

Section: Introductionmentioning

confidence: 99%

Extracting and Evolving Code in Product Lines with Aspect-Oriented Programming

Alves

Matos

Cole

et al. 2007

Transactions on Aspect-Oriented Software Development IV

View full text Add to dashboard Cite

show abstract

“…In the present work, we select three companies and describe and analyze them in-depth. Our selection represents a broad range of development scales from very small (two developers) to ultra-large (100 development teams); comprises domains that commonly use variability modeling (automotive, industrial applications/energy, and eCommerce [5]); and covers all product-line adoption strategies (proactive, extractive, and reactive [27]). In contrast to quantitative research, our goal is not too reach any statistically significant deductions, but to describe the practices that were successful in three heterogeneous cases.…”

Section: -What Are the Benefits (Rq2) And What Are The Challenges (Rqmentioning

confidence: 99%

Three Cases of Feature-Based Variability Modeling in Industry

Berger

Nair

Rublack

et al. 2014

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Large software product lines need to manage complex variability. A common approach is variability modeling-creating and maintaining models that abstract over the variabilities inherent in such systems. While many variability modeling techniques and notations have been proposed, little is known about industrial practices and how industry values or criticizes this class of modeling. We attempt to address this gap with an exploratory case study of three companies that apply variability modeling. Among others, our study shows that variability models are valued for their capability to organize knowledge and to achieve an overview understanding of codebases. We observe centralized model governance, pragmatic versioning, and surprisingly little constraint modeling, indicating that the effort of declaring and maintaining constraints does not always pay off.

show abstract

“…Consequently, an adoption model needs to take into consideration these aspects, if not all at least most of them. The adoption models focusing on only certain aspects are not discussed in this research, for example the ones where adoption is based on legacy products [32], architecture [33,34], organizational structure [27], or separation of concerns [35].…”

Section: Software Product Line Adoption Modelsmentioning

confidence: 99%

Software Product Line Adoption – Guidelines from a Case Study

Kuvaja

Similä

Hanhela³

2011

Software Engineering Techniques

View full text Add to dashboard Cite

Abstract. It is possible to proceed with software product line adoption only once without major reinvestments and loss of time and money. In the literature, reported experiences of using the adoption models are not to be found, and especially the suitability of the models has not been reported. The purpose of this research is to compare known adoption models by formulating general evaluation criteria for the selection of an adoption model. Next an adoption model is selected for empirical research based on the context of a multimedia unit of a global telecommunication company. The empirical part consists of a case study analyzing the present state of adoption and producing plans for proceeding with the adoption. The research results can be utilized when selecting an adoption model for an empirical case and adopting a software product line in a software intensive organization.

show abstract

Easing the Transition to Software Mass Customization

Cited by 190 publications

References 1 publication

Extracting and Evolving Code in Product Lines with Aspect-Oriented Programming

Extracting and Evolving Code in Product Lines with Aspect-Oriented Programming

Three Cases of Feature-Based Variability Modeling in Industry

Software Product Line Adoption – Guidelines from a Case Study

Contact Info

Product

Resources

About