Your English writing platform
Discover LudwigExact(5)
(IC1) the study presents a template for textual use cases description of an SPL.
For this mapping study, we defined just one inclusion criterion: (IC1) the study presents a template for textual use cases description of an SPL.
(EC1) the study is not written in English; (EC2) the study is just published as an abstract; (EC3) the study does not contain a template for textual use cases description with focus on an SPL; and.
Therefore, the template used for textual use cases in the SPL paradigm should allow the specification of "small variations" (Gomaa 2004) (fine-grained variation), which can affect just one or two lines in the use case description.
On the other hand, we defined four exclusion criteria: (EC1) the study is not written in English; (EC2) the study is just published as an abstract; (EC3) the study does not contain a template for textual use cases description with focus on an SPL; and (EC4) Duplicate use case template.
Similar(55)
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).
In a previous work (Santos et al. 2014), we identified and classified nine templates for textual use case descriptions of Software Product Lines through a Systematic Mapping (SM) (Kitchenham and Charters 2007).
However, to the best of our knowledge, there has not been a systematic effort to collect and summarize the existing templates for textual use case descriptions in the SPL paradigm and there is no empirical assessment of the SPL use cases' comprehensibility provided by these use case templates.
Then, the research questions used were: RQ1: Which are the templates for the textual use cases of an SPL? RQ2: How could SPL variability be modeled in textual use cases?
RQ3: Which variability types can be modeled in textual use cases of an SPL? RQ1: Which are the templates for the textual use cases of an SPL? RQ2: How could SPL variability be modeled in textual use cases?
Table 6 presents the results for the category Variability Type Supported, regarding which variability types can be modeled in textual use cases of an SPL.
Write better and faster with AI suggestions while staying true to your unique style.
Since I tried Ludwig back in 2017, I have been constantly using it in both editing and translation. Ever since, I suggest it to my translators at ProSciEditing.

Justyna Jupowicz-Kozak
CEO of Professional Science Editing for Scientists @ prosciediting.com