Analyzing the Convenience of Adopting a Product Line Engineering Approach

Rincón, Luisa; Mazo, Raúl; Salinesi, Camille

doi:10.1145/3307630.3342418

Cited by 3 publications

(5 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Seven of the nine participants responded they would recommend APPLIES and all participants that responded the questionnaire would use it ( ≥ 4). All these results are consistent with what had been found in previous evaluations of APPLIES as can be corroborated in our previous work [14,16,17].…”

Section: Rq1 How Useful Do Practitioners Perceivesupporting

confidence: 93%

“…This finding could indicate that APPLIES has adoption drivers that are unhelpful in supporting companies to differentiate when they have reasons to adopt PLE. We reported a similar finding in [17] when people from a software company suggested that APPLIES included factors that many companies would like to achieve even if they do not need a PLE approach. Therefore, the adoption drivers proposed should be reviewed to verify their pertinence.…”

Section: Rq4 Improvementssupporting

confidence: 64%

“…The format for capturing responses remained the same across all versions of APPLIES for the motivation part, but modified in this evaluation for the preparation part. This result is positive because while in previous evaluations (see [14,16,17]) negative comments were received on the format used to capture responses, in this evaluation no negative comments were received on this regard.…”

Section: Operationmentioning

confidence: 58%

See 2 more Smart Citations

A multi-company empirical evaluation of a framework that evaluates the convenience of adopting product line engineering

Rincón

Mazo

Salinesi

2020

Proceedings of the 24th ACM International Systems and Software Product Line Conference - Volume B

Self Cite

View full text Add to dashboard Cite

Companies considering adopting a product line engineering approach should ideally analyze the pros and cons to determine the sound reasons for this decision. In order to support this analysis, in previous work we proposed the APPLIES evaluation framework. This framework provides information to evaluate the convenience of adopting a product line engineering approach. This paper presents an empirical evaluation of APPLIES. This experience includes 18 potential practitioners that used the framework to evaluate the convenience of adopting product line engineering in 19 different companies. The collected evidence was used to evaluate the perceived usefulness, intention to use and ease of use of APPLIES. The results presented increase confidence that APPLIESis a useful tool, but also identify some possibilities for improvement. In addition, four categories for classifying potential adopters of product line engineering emerged during the analysis of the results: unprepared adopter, potential adopter, ready adopter, and unmotivated adopter. These categories could be useful to classify companies that are considering adopting product line engineering. CCS CONCEPTS • General and reference → Empirical studies; • Software and its engineering → Software product lines.

show abstract

Section: Rq1 How Useful Do Practitioners Perceivesupporting

confidence: 93%

Section: Rq4 Improvementssupporting

confidence: 64%

Section: Operationmentioning

confidence: 58%

See 1 more Smart Citation

A multi-company empirical evaluation of a framework that evaluates the convenience of adopting product line engineering

Rincón

Mazo

Salinesi

2020

Proceedings of the 24th ACM International Systems and Software Product Line Conference - Volume B

Self Cite

View full text Add to dashboard Cite

show abstract

“…Several researchers have been concerned with scoping, planning, decision-making, and measuring the maturity of a product line (Tüzün et al 2015;Kalender et al 2013;Schmid et al 2005;Marchezan et al 2019;Ahmed et al 2007;Niemelä et al 2004;Bosch 2002;Ahmed and Capretz 2011;Koziolek et al 2016;Rincón et al 2019;. PuLSE (Bayer et al 1999) is arguably one of the most detailed of such methods, considering various aspects of planning, adopting, and developing a product line.…”

Section: Scoping and Assessment Techniques For Splementioning

confidence: 99%

“…Similarly, Rincón et al (2019) assess to what extent their recently proposed APPLIES framework (Rincón et al 2018) for deciding on the adoption of SPLE is useful in industry. Rincón et al focus on similar research questions as we do, reporting to what extent their framework is perceived useful, what improvements the organization achieved, and what lessons they learned-based on two workshops with employees of the organization.…”

Section: Planning Sple Adoptionmentioning

confidence: 99%

Software product-line evaluation in the large

et al. 2021

View full text Add to dashboard Cite

Software product-line engineering is arguably one of the most successful methods for establishing large portfolios of software variants in an application domain. However, despite the benefits, establishing a product line requires substantial upfront investments into a software platform with a proper product-line architecture, into new software-engineering processes (domain engineering and application engineering), into business strategies with commercially successful product-line visions and financial planning, as well as into re-organization of development teams. Moreover, establishing a full-fledged product line is not always possible or desired, and thus organizations often adopt product-line engineering only to an extent that deemed necessary or was possible. However, understanding the current state of adoption, namely, the maturity or performance of product-line engineering in an organization, is challenging, while being crucial to steer investments. To this end, several measurement methods have been proposed in the literature, with the most prominent one being the Family Evaluation Framework (FEF), introduced almost two decades ago. Unfortunately, applying it is not straightforward, and the benefits of using it have not been assessed so far. We present an experience report of applying the FEF to nine medium- to large-scale product lines in the avionics domain. We discuss how we tailored and executed the FEF, together with the relevant adaptations and extensions we needed to perform. Specifically, we elicited the data for the FEF assessment with 27 interviews over a period of 11 months. We discuss experiences and assess the benefits of using the FEF, aiming at helping other organizations assessing their practices for engineering their portfolios of software variants.

show abstract