Architecture Recovery. When it comes to integrating a set of existing similar variants on the way towards an SPL, it is essential to abstract a common architecture. This visualization abstracts from the variants' component architecture to highlight the variance presence. The component diagram depicts which modules are present in several variants (list of names) and to which extent the module is similarly implemented (bar chart). Figure credits [S5].

Contexts in source publication

Context 1

... Building a platform architecture out of existing variants is error-prone and tedious. Fig. 5 introduces a visualization that abstracts and aggregates this information. Commonalities and variabilities among variant architectures are captured from two perspectives: variance presence (i.e., if the existence of the module is variable or not) and variance realization (i.e., if the implementation of the module is different across ...

Context 2

... chart' (see Fig. 8) [S8]; 'nodelink diagram ' and 'tabular/matrix' [S34,S40]; 'bar chart', 'heatmap' and 'treemap' (see Fig. 3) [S3]; 'tabular/matrix ' and 'heatmap' [S16]; 'bar chart' and 'nodelink diagram' (see Fig. 1) [S1]; 'nodelink diagram' and 'word cloud' (see Fig. 7) [S7]; 'tabular/matrix', 'bar chart' and 'enriched software diagram' (see Fig. 5) [S5]; or 'alluvial diagram ' and 'treemap' [S23]. Table 8 outlines the results. Nearly half of the primary sources (44%) do not support any kind of interaction but just provide static diagrams. For those supporting some interaction, 'abstract/elaborate' is the most common. This may be due to the different levels of abstraction present ...