Integration of feature models: A systematic mapping study

Bischoff, Vinícius; Farias, Kleinner; Gonçales, Lucian José; Barbosa, Jorge Luís Victória

doi:10.1016/j.infsof.2018.08.016

Cited by 20 publications

(11 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Fifth, it would not make sense to consider investigating duplicate studies (EC5), or not addressing the subject of effort estimation (EC6). More importantly, these EC have already been validated in previous studies, such as [11,21,28,29].…”

Section: Exclusion and Inclusion Criteria (Ic)mentioning

confidence: 79%

“…These databases were chosen because of their elevated number of studies stored. Moreover, they have been widely used in previous systematic mapping studies [11,[21][22][23].…”

Section: Search Strategymentioning

confidence: 99%

“…This protocol addresses steps, claimed as essential in [18][19][20], to plan and create a systematic mapping of the literature. Moreover, our study protocol is based on previously validated systematic mapping studies [12,[21][22][23]. This article makes use of systematic mapping study as the methodology because it minimises bias when compared to single literature reviews, thus getting more reliable findings [24].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Software development effort estimation: a systematic mapping study

2020

Self Cite

View full text Add to dashboard Cite

The field of software-development effort estimation explores ways of defining effort through prediction approaches. Even though this field has a crucial impact on budgeting and project planning in industry, the number of works classifying and examining currently available approaches is still small. This article, therefore, presents a comprehensive overview of these approaches, and pinpoints research gaps, challenges and trends. A systematic mapping of the literature was designed and performed based on well-established practical guidelines. In total, 120 primary studies were selected, analysed and categorised, after applying a careful filtering process from a sample of 3746 candidate studies to answer six research questions. Over 70% of the selected studies adopted multiple effort estimation approaches; over 45% adopted evaluation research as a research method; over 90% of the participants were students, rather than professionals; most studies had their quality assessed as high, and were most commonly published in journals. Our study benefits practitioners and researchers by providing a body of knowledge about the current literature, serving as a starting point for upcoming studies. This article reports challenges worth investigating, regarding the use of cognitive load and team interaction. 2 Planning This section aims to outline our review protocol. Fig. 1 introduces the adopted systematic mapping process, which is formed by three

show abstract

Section: Exclusion and Inclusion Criteria (Ic)mentioning

confidence: 79%

“…These databases were chosen because of their elevated number of studies stored. Moreover, they have been widely used in previous systematic mapping studies [11,[21][22][23].…”

Section: Search Strategymentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Software development effort estimation: a systematic mapping study

2020

Self Cite

View full text Add to dashboard Cite

show abstract

“…These constant changes made by different developer profiles turn legacy applications into monolithic ones. Typically, these changes impact on various features of systems under maintenance [3], and developers often have to compare different versions of system design created [12]. Empirical studies demonstrate that these integrations and maintenance are timeconsuming and error prone [5] [8][9] [10].…”

Section: Introductionmentioning

confidence: 99%

Mind Overflow: A Process Proposal for Decomposing Monolithic Applications in Microservices

Pereira¹,

Farias²

2020

IJCA

Self Cite

View full text Add to dashboard Cite

Constant changes made by different developer profiles turn legacy applications into monolithic ones. Although it is a known issue, little has been done to mitigate it. This paper proposes Mind Overflow, a process to guide the decomposition of a monolithic application to a microservice architecture. With Mind Overflow, researchers and developers benefit from the use of consolidated design patterns, architectures, and technologies through a comprehensive decomposition workflow. The case study showed promising results, indicating that Mind Overflow is feasible to break down monolithic to a microservice-based architecture, including reducing cyclomatic complexity and producing highly cohesive microservices.

show abstract

“…At some point, it is necessary to combine these models to produce a 'big picture' view of the overall architecture. For this reason, a significant body of research has been done in the field of collaborative software modelling [4], merge conflicts [5], model synchronisation [6], integration of heterogeneous models [7], and integration of feature models [8].…”

Section: Introductionmentioning

confidence: 99%

UML2Merge: a UML extension for model merging

et al. 2019

Self Cite

View full text Add to dashboard Cite

Model merging plays a chief role in many software engineering activities, e.g. evolving Unified Modelling Language (UML) models for adding new features. Software developers may evolve UML models using merge relationships. However, given the growing heterogeneity of merge strategies and the UML limitations for expressing merge relationship, it is particularly challenging for them to specify merge relationships. Consequently, developers, end up expressing improperly merge relationships. Today, the UML can neither specify the semantics nor the order in which merge relationships must be performed. Developers are unable to specify the semantics and order in which merge relationships must be performed. This study, therefore, proposes UML2Merge, which is a UML extension for expressing merge relationship. The UML2Merge was evaluated through an empirical study with 10 participants for investigating its effects on the merge effort, the correctness of merge relationships, and the participant's acceptance. The collected data suggest that the UML2Merge is proper to express merge relationships by requiring a low merge effort, producing elevated correctness of merge relationships, and having a high acceptance of the participants. The results are encouraging and show the potential for using UML2Merge to express the evolution of UML models through merge relationships.

show abstract

Integration of feature models: A systematic mapping study

Cited by 20 publications

References 25 publications

Software development effort estimation: a systematic mapping study

Software development effort estimation: a systematic mapping study

Mind Overflow: A Process Proposal for Decomposing Monolithic Applications in Microservices

UML2Merge: a UML extension for model merging

Contact Info

Product

Resources

About