Automating Mappings between Use Case Diagrams and Feature Models for Software Product Lines

Braganca,; Machado,

doi:10.1109/spline.2007.17

Cited by 25 publications

(5 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Considerable research has already been devoted to documenting variability in use cases. Many approaches propose using variability models, e.g., feature models, that are traced to use case specifications and diagrams ( Alferez et al, 2008;Eriksson et al, 20 05, 20 09;Buhne et al, 20 06;Braganca and Machado, 2007;Griss et al, 1998 ). With the PL extensions, our method enables analysts to document variability directly in use case diagrams and specifications.…”

Section: Discussionmentioning

confidence: 99%

Change Impact Analysis for Evolving Configuration Decisions in Product Line Use Case Models

Hajri

Göknil

Briand

et al. 2019

2019 IEEE/ACM 10th International Symposium on Software and Systems Traceability (SST)

View full text Add to dashboard Cite

Product Line Engineering is becoming a key practice in many software development environments where complex systems are developed for multiple customers with varying needs. In many business contexts, use cases are the main artifacts for communicating requirements among stakeholders. In such contexts, Product Line (PL) use cases capture variable and common requirements while use case-driven configuration generates Product Specific (PS) use cases for each new customer in a product family. In this paper, we propose, apply, and assess a change impact analysis approach for evolving configuration decisions in PL use case models. Our approach includes: (1) automated support to identify the impact of decision changes on prior and subsequent decisions in PL use case diagrams and (2) automated incremental regeneration of PS use case models from PL use case models and evolving configuration decisions. Our tool support is integrated with IBM Doors. Our approach has been evaluated in an industrial case study, which provides evidence that it is practical and beneficial to analyze the impact of decision changes and to incrementally regenerate PS use case models in industrial settings.

show abstract

Section: Discussionmentioning

confidence: 99%

Change Impact Analysis for Evolving Configuration Decisions in Product Line Use Case Models

Hajri

Göknil

Briand

et al. 2019

2019 IEEE/ACM 10th International Symposium on Software and Systems Traceability (SST)

View full text Add to dashboard Cite

show abstract

“…Braganca and Machado [15] describe an approach for automating the transformation of UML use cases into FMs. In their work, each use case is mapped to a feature.…”

Section: Documentation Of Mined Features In Splmentioning

confidence: 99%

“…Our work addresses the problem of documenting features mined from several variants of a software system. Our mined feature implementations are sets of source code elements that are more formal artifacts than the product descriptions used in [21] and give complementary information as compared to use-case diagrams [15]. Our approach relies on commonality and variability across the variants to apply information retrieval methods more e±ciently than in a single software system.…”

Section: Synthesismentioning

confidence: 99%

“…As previously mentioned, we aim at documenting mined feature implementations by using use-case diagrams that document a set of software variants. We rely on the same assumption as in the work of [15] stating that each use case corresponds to a feature. The feature documentation process uses lexical similarity to identify which use-case best characterizes the name and description of each feature implementation.…”

Section: The Feature Documentation Processmentioning

confidence: 99%

See 1 more Smart Citation

Automatic Documentation of [Mined] Feature Implementations from Source Code Elements and Use-Case Diagrams with the REVPLINE Approach

Al-Msie’deen

Huchard

Seriai

et al. 2014

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

International audienceCompanies often develop a set of software variants that share some features and differ in other ones to meet specific requirements. To exploit the existing software variants as a Software Product Line (SPL), a Feature Model of this SPL must be built as a first step. To do so, it is necessary to define and document the optional and mandatory features that compose the variants. In our previous work, we mined a set of feature implementations as identified sets of source code elements. In this paper, we propose a complementary approach, which aims to document the mined feature implementations by giving them names and descriptions, based on the source code elements that form feature implementations and the use-case diagrams that specify software variants. The novelty of our approach is its use of commonality and variability across software variants, at feature implementation and use-case levels, to run Information Retrieval methods in an efficient way. Experiments on several real case studies (Mobile media and ArgoUML-SPL) validate our approach and show promising results

show abstract

“…No método PLUSS (Eriksson et al 2005), cada feature pode estar associada a um caso de uso, um cenário alternativo ou um passo específico. Bragança et al (2007) apresentaram um método para automatizar a transformação de casos de uso da UML em modelo de features.…”

Section: Trabalhos Relacionadosunclassified

Elaboração de Especificações de Casos de Uso para Linhas de Produto de Software Baseada em Fragmentos

Alencar

Araujo

Schmitz

et al. 2009

Anais Do III Simpósio Brasileiro De Componentes, Arquiteturas E Reutilização De Software (SBCARS 2009)

View full text Add to dashboard Cite

Casos de uso são largamente utilizados na elicitação e especificação de requisitos funcionais de sistemas de informação. Entretanto, escrever especificações textuais de casos de uso para Linhas de Produto de Software é uma tarefa trabalhosa e o modelo resultante pode se tornar sobrecarregado para o uso prático. Para superar esses problemas, é proposto um método que possui duas fases: na primeira fase, um conjunto de fragmentos de casos de uso do domínio é elaborado a partir da análise dos requisitos comuns e variáveis da linha de produto; na segunda fase, descrições textuais de casos de uso para uma dada aplicação podem ser rapidamente produzidas através da composição e personalização desses fragmentos.

show abstract

Automating Mappings between Use Case Diagrams and Feature Models for Software Product Lines

Abstract: Abstract

Cited by 25 publications

References 9 publications

Change Impact Analysis for Evolving Configuration Decisions in Product Line Use Case Models

Change Impact Analysis for Evolving Configuration Decisions in Product Line Use Case Models

Automatic Documentation of [Mined] Feature Implementations from Source Code Elements and Use-Case Diagrams with the REVPLINE Approach

Elaboração de Especificações de Casos de Uso para Linhas de Produto de Software Baseada em Fragmentos

Contact Info

Product

Resources

About