Proceedings of the 8th ACM International Conference on Aspect-Oriented Software Development 2009
DOI: 10.1145/1509239.1509258
|View full text |Cite
|
Sign up to set email alerts
|

Modeling scenario variability as crosscutting mechanisms

Abstract: Variability management is a common challenge for Software Product Line (SPL) adoption, since developers need suitable mechanisms for specifying and implementing variability that occurs at different SPL artifacts (requirements, design, implementation, and test). In this paper, we present a novel approach for use case scenario variability management, enabling a better separation of concerns between languages used to manage variabilities and languages used to specify use case scenarios. The result is that both re… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
45
0
1

Year Published

2010
2010
2020
2020

Publication Types

Select...
5
3
2

Relationship

0
10

Authors

Journals

citations
Cited by 46 publications
(46 citation statements)
references
References 18 publications
0
45
0
1
Order By: Relevance
“…Bonifácio et al [20,18] propose a framework for modeling the composition process of scenario variability mechanisms (MSVCM). They provide a weaver (configurator) that takes a PL use case model, a feature model, a product configuration, and configuration knowledge as input.…”
Section: )mentioning
confidence: 99%
“…Bonifácio et al [20,18] propose a framework for modeling the composition process of scenario variability mechanisms (MSVCM). They provide a weaver (configurator) that takes a PL use case model, a feature model, a product configuration, and configuration knowledge as input.…”
Section: )mentioning
confidence: 99%
“…Several configuration tools for scenario-based requirements have been proposed in the literature [2,3,4,8,6,7,16]. Most of these require that feature models be manually traced to requirements by analysts.…”
Section: Related Workmentioning
confidence: 99%
“…Many proposed use case-driven configuration approaches [5,6,16,18,17,2] require that feature models be traced to use case diagrams and specifications. The analysts need to establish traces between feature models and use cases.…”
Section: Related Workmentioning
confidence: 99%