On the refinement of use case models with variability support

Abstract

Modeling software product lines shall imply modeling from different perspectives with different modeling artifacts such as use case diagrams, component diagrams, class diagrams, activity diagrams, sequence diagrams and others. In this paper, we elaborate on use cases for modeling product lines and we explore them from the perspective of variability by working with the unified modeling language (UML) «extend» relationship. We also explore them from the perspective of detail by (functionally) refining use cases with «extend» relationships between them. This paper's intent is to provide for comprehension about use case modeling with functional refinement when variability is present.

More Accurate Cost Estimation for Internet of Things Projects by Adaptation of Use Case Points Methodology

“…Several modifications have been proposed to improve the UCP method, including the use of extension associations to improve calculation accuracy [19] and the calculation of sub-components using the Extended UCP and Modified UCP methods [20], [15], [21]. Other modifications focus on scenario decomposition and the identification of transactions and events within scenarios [22], [23], [24], [25].…”

Requirements modeling languages for software product lines: A systematic literature review

“…[49] Define a domain ontology called Kumbang for modeling variability in SPL. [72] It provides a formalization and understanding of the use case modeling activity with support for variability and functional refinement. [73] SimPL methodology provides a notation and a set of guidelines for modelling commonalities and variabilities in ICS families.…”

Applying product line Use case modeling in an industrial automotive embedded system: Lessons learned and a refined approach

“…Maßen and Lichter [23] propose two new relations to represent alternative and optional use cases in UML use case diagrams, without any support for expressing variation points. Azevedo et al [24] [10] explore the use of the UML 'extend' relation with the new stereotypes 'alternative', 'specialization' and 'option' to distinguish variability types. The 'alternative' and 'specialization' are applied to the 'extend' relation while the 'option' is applied to use cases that represent options.…”