A Feature-Driven Requirements Engineering Approach for Software Product Lines

Oliveira, Raphael Pereira de; Insfrán, Emilio; Abrahão, Silvia; González-Huerta, Javier; Blanes, David; Cohen, Sholom; Almeida, Eduardo Santana de

doi:10.1109/sbcars.2013.11

Cited by 10 publications

(11 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Finally, the template presented by Oliveira et al (2013) is an adaptation of Eriksson et al 's template ). However, unlike Eriksson et al 's template, Oliveira et al suggest that the features names should be clearly specified in the use case through the element named "Associated feature" and that the variations can be related to alternative scenarios within the use case.…”

Section: Results Related To Rq1mentioning

confidence: 99%

“…The Specific Section is present in two templates (Gomaa 2004;Nguyen 2009) while the Alternative Scenarios is used in one template (Oliveira et al 2013). Both these template structures describe the SPL variability in a use case without affecting the description of the main use case scenario.…”

Section: Results Related To Rq2mentioning

confidence: 99%

“…In the SPL paradigm, the requirements engineering activity needs to cope with common and variable requirements for the whole set of products in the family (Oliveira et al 2013). The SPL requirements should then be modeled from the reuse perspective by explicitly representing the commonality and variability information (Alves et al 2010).…”

Section: Introductionmentioning

confidence: 99%

“…In the SPL paradigm is important to note that the use cases model needs to be adapted to incorporate the mechanisms of variability (Oliveira et al 2013). Thus, there are proposals for the description of SPL variability in the use cases model with 'include' and 'extend' relationships (Azevedo et al 2012;Bragança and Machado 2006;Gomaa 2004).…”

Section: Introductionmentioning

confidence: 99%

“…In the literature, there have been different proposals for templates for textual use case descriptions of Software Product Lines, such as (Gallina and Guelfi 2007;Gomaa 2004;Oliveira et al 2013). Other studies have compared some of these templates (Bonifácio and Borba 2009;Santos et al 2013).…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Templates for textual use cases of software product lines: results from a systematic mapping study and a controlled experiment

Santos

Andrade

Neto

2015

J Softw Eng Res Dev

View full text Add to dashboard Cite

Use case templates can be used to describe functional requirements of a Software Product Line. However, to the best of our knowledge, no efforts have been made to collect and summarize these existing templates and no empirical evaluation of the use cases' comprehensibility provided by these templates has been addressed yet. The contributions of this paper are twofold. First, we present a systematic mapping study about the SPL variability description using textual use cases. From this mapping, we found twelve SPL use case templates and observed the need not only for the application of these templates in real SPL but also for supporting tools. Secondly, this work presents an evaluation of the comprehensibility of SPL use cases specified in these templates through a controlled experiment with 48 volunteers. The results of this experiment show that the specification of variabilities in the steps' numeric identifiers of the textual use cases is better to the use case understanding than the other approaches identified. We also found evidence that the specification of variabilities at the end of the use cases favors the comprehension of them and the use of questions associated to the variation points in the use cases improves the understanding of use cases. We conclude that each characteristic of the existing templates has an impact on the SPL use case understanding and this should be taken into account when choosing one.

show abstract

Section: Results Related To Rq1mentioning

confidence: 99%