A systematic mapping study of information visualization for software product line engineering

Lopez-Herrejon, Roberto E.; Illescas, Sheny; Egyed, Alexander

doi:10.1002/smr.1912

Cited by 32 publications

(43 citation statements)

References 84 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The D3.js 7 library is used as the visualization support in the symfinder toolchain. Although we considered using the visualization capabilities of Neo4j and other visualization forms used in SPL engineering [38], we decided for D3.js as it allows to visualize not only graphs but also a plethora of chart types. We were able to consider them before devising the current form of visualization, and this could also help for future evolutions of the toolchain.…”

Section: Visualizationmentioning

confidence: 99%

“…Regarding the visualization, a recent mapping study shows that there are several approaches and tools for information visualization in SPL engineering [38]. The most common visualized artifacts are feature models, which use trees or graphs.…”

Section: Related Workmentioning

confidence: 99%

“…Some visualizations for feature-file tracing have been also proposed [5], but they are very specific. In general, excluding the configuration process [47,52], it is well recognized that the majority of the tools in SPL engineering use ad hoc visualization techniques or use the available functionalities inside Eclipse [38]. In contrast, our visualization tends to display, after filtering, trees -which are actually disconnected graphs -conform to the nature of vp-s, variants, and their relationships.…”

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Identifying and Visualizing Variability in Object-Oriented Variability-Rich Systems

Tërnava

Mortara

Collet

2019

Proceedings of the 23rd International Systems and Software Product Line Conference - Volume A

View full text Add to dashboard Cite

In many variability-intensive systems, variability is implemented in code units provided by a host language, such as classes or functions, which do not align well with the domain features. Annotating or creating an orthogonal decomposition of code in terms of features implies extra effort, as well as massive and cumbersome refactoring activities. In this paper, we introduce an approach for identifying and visualizing the variability implementation places within the main decomposition structure of object-oriented code assets in a single variability-rich system. First, we propose to use symmetry, as a common property of some main implementation techniques, such as inheritance or overloading, to identify uniformly these places. We study symmetry in different constructs (e.g., classes), techniques (e.g., subtyping, overloading) and design patterns (e.g., strategy, factory), and we also show how we can use such symmetries to find variation points with variants. We then report on the implementation and application of a toolchain, symfinder, which automatically identifies and visualizes places with symmetry. The publicly available application to several large open-source systems shows that symfinder can help in characterizing code bases that are variability-rich or not, as well as in discerning zones of interest w.r.t. variability. CCS CONCEPTS• Software and its engineering → Software product lines; Object oriented development; Reusability. KEYWORDSIdentifying software variability, visualizing software variability, object-oriented variability-rich systems, tool support for understanding software variability, software product line engineering

show abstract

Section: Visualizationmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Identifying and Visualizing Variability in Object-Oriented Variability-Rich Systems

Tërnava

Mortara

Collet

2019

Proceedings of the 23rd International Systems and Software Product Line Conference - Volume A

View full text Add to dashboard Cite

show abstract

“…Figure 2). After considering the visualization capabilities of Neo4j and 1 https://neo4j.com/developer/cypher/ other visualization forms used in SPL engineering [13], we decided to use the D3.js 2 library as the visualization support, so that only a Web browser is needed to visualize the vp-s graph.…”

Section: Web-based Visualizationmentioning

confidence: 99%

symfinder

Mortara

Tërnava

Collet

2019

Proceedings of the 23rd International Systems and Software Product Line Conference - Volume B

View full text Add to dashboard Cite

“…This situation motivates the authors to undertake this systematic mapping study on factors, so‐called “SPI inhibitors,” which undermine the success of SPI initiatives. Since the introduction of Evidenced‐based Software Engineering and subsequently following the guidelines for conducting systematic reviews, presence of secondary studies in software engineering domain has grown over the years . These studies are classified as systematic literature reviews (SLR) and systematic mapping studies (SMS).…”

Section: Introductionmentioning

confidence: 99%

Investigating the factors which impact SPI implementation initiatives in software SMEs—A systematic map and review

Sharma

Sangal

2019

J Software Evolu Process

View full text Add to dashboard Cite

Context: For successful initiation of software process improvement (SPI) initiatives in software SMEs, it is vital for the practitioners to have deep understanding of various SPI inhibitors.Objective: The paper has the following objectives: investigate factors which impact SPI implementation initiatives in software SMEs, synthesize available evidence, identify gaps between existing approaches available in the literature, and to develop the taxonomy of the factors.Methods: Database search and snowballing procedure are adapted to perform the systematic mapping and review, which includes 105 primary studies published between 2002 and 2018. Also, we reviewed the empirical studies for their rigor and relevance.Results: A total of 16 inhibitors have been identified and are grouped into PMBOK knowledge areas framework. From the rigor and relevance scores, it is observed that despite the research has been conducted in an industrial context, it lacks rigor (mean = 1.79) and thus hinders the possibility of generalizing the results. This calls for more studies with thorough empirical analysis and validation using adequate statistical tests. Conclusions:The results can help the practitioners to understand the dynamics of factors, which undermine SPI implementation in software SMEs and also to assist them in the development of effective control and mitigation strategies. KEYWORDS Global Software Development, software process improvement, SPI factors, systematic literature review, systematic mapping 1 | INTRODUCTION Increasingly, many software organizations have taken up global sourcing of software activities, primarily because of the considerable benefits.However, there are various challenges linked with global sourcing, predominantly with respect to software process improvement (SPI). 1-3 In the previous two decades, significant research work has been undertaken by the researchers on the development of standards and model frameworks to boost up SPI process in software SMEs. In spite of the presence of models such as Capability Maturity Model Integration (CMMI), MoProSoft, ISO/IEC 15504, and ISO/IEC 12207, the success rate of SPI implementation in SMEs is quite low. 3,4 Ngwenyama and Nielsen 4 described that about 70% of the organizations fail in the successful implementation of process improvement initiatives, and the major cause of this failure is the inadequate emphasis paid towards the process improvement. SPI literature encompasses numerous case studies on SPI programs, which have been realized by software companies, among other things, to improve quality and pace of their software projects. 5,6 Generally, SPI is deemed extremely significant for companies of all sorts and sizes. 7 But, it is also a risky attempt, which involves both cost and effort, as evident from literature studies being undertaken by researchers in software enterprises. [5][6][7][8][9][10] For successful initiation of SPI program software, SMEs transform their processes to meet the requirements of process reference models they wish to employ. [10][11]...

show abstract

A systematic mapping study of information visualization for software product line engineering

Cited by 32 publications

References 84 publications

Identifying and Visualizing Variability in Object-Oriented Variability-Rich Systems

Identifying and Visualizing Variability in Object-Oriented Variability-Rich Systems

symfinder

Investigating the factors which impact SPI implementation initiatives in software SMEs—A systematic map and review

Contact Info

Product

Resources

About