A Framework for Software Architecture Visualisation Assessment

Use policyThe full-text may be used and/or reproduced, and given to third parties in any format or medium, without prior permission or charge, for personal research or study, educational, or not-for-prot purposes provided that:• a full bibliographic reference is made to the original source • a link is made to the metadata record in DRO • the full-text is not changed in any way The full-text must not be sold in any format or medium without the formal permission of the copyright holders.Please consult the full DRO policy for further details. Abstract-In order to characterize and improve software architecture visualization practice, the paper derives and constructs a qualitative framework, with seven key areas and 31 features, for the assessment of software architecture visualization tools. The framework is derived by the application of the Goal Question Metric paradigm to information obtained from a literature survey and addresses a number of stakeholder issues. The evaluation is performed from multiple stakeholder perspectives and in various architectural contexts. Stakeholders can apply the framework to determine if a particular software architecture visualization tool is appropriate to a given task. The framework is applied in the evaluation of a collection of six software architecture visualization tools. The framework may also be used as a design template for a comprehensive software architecture visualization tool.

show abstract

“…The framework can also be used as design guidelines for an "ideal" tool. A preliminary version of these results was presented in [10].…”

Section: Results Summary and Contributionmentioning

confidence: 99%

Software Architecture Visualization: An Evaluation Framework and Its Application

Gallagher

Hatch

Munro

2008

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

show abstract

“…Visualizing the architecture of software [93] is one of the most important topics in the visualization of software field [86], [94], [95], [96]. Object-oriented software is generally structured hierarchically, with packages containing subpackages, recursively, and with classes structured by methods and attributes.…”

Section: Architecture Visualizationmentioning

confidence: 99%

Visualization of the Static Aspects of Software: A Survey

Caserta

Zendra

2011

IEEE Trans. Visual. Comput. Graphics

113

View full text Add to dashboard Cite

Abstract-Software is usually complex and always intangible. In practice, the development and maintenance processes are timeconsuming activities mainly because software complexity is difficult to manage. Graphical visualization of software has the potential to result in a better and faster understanding of its design and functionality, thus saving time and providing valuable information to improve its quality. However, visualizing software is not an easy task because of the huge amount of information comprised in the software. Furthermore, the information content increases significantly once the time dimension to visualize the evolution of the software is taken into account. Human perception of information and cognitive factors must thus be taken into account to improve the understandability of the visualization. In this paper, we survey visualization techniques, both 2D-and 3D-based, representing the static aspects of the software and its evolution. We categorize these techniques according to the issues they focus on, in order to help compare them and identify the most relevant techniques and tools for a given problem.

show abstract

“…The two criteria roughly correspond to our Goals and Techniques axes. Gallagher et al propose a framework to assess architectural visualization tools and compare a couple of tools [45]. Gueheneuc et al present a comparative framework for design recovery tools and compared three approaches [55].…”

Section: Taxonomy Axesmentioning

confidence: 99%

“…Supporting visualization tools: A lot of approaches offer (architectural) views or use visualizations as output [45] such as ArchVis [62]. As we mentioned earlier, several tools such as Rigi [113,173], Shrimp/Creole [153,177], GraphViz [47] or CodeCrawler [92] are used to visualize graph representations of software views [42,76,84,128,134,139,140].…”

Section: A Visual Software Viewsmentioning

confidence: 99%

Software Architecture Reconstruction: A Process-Oriented Taxonomy

Ducasse

Pollet

2009

IIEEE Trans. Software Eng.

274

153

View full text Add to dashboard Cite

Abstract-To maintain and understand large applications, it is important to know their architecture. The first problem is that unlike classes and packages, architecture is not explicitly represented in the code. The second problem is that successful applications evolve over time, so their architecture inevitably drifts. Reconstructing the architecture and checking whether it is still valid is therefore an important aid. While there is a plethora of approaches and techniques supporting architecture reconstruction, there is no comprehensive software architecture reconstruction state of the art and it is often difficult to compare the approaches. This article presents a state of the art in software architecture reconstruction approaches.

show abstract

A Framework for Software Architecture Visualisation Assessment

Cited by 8 publications

References 11 publications

Software Architecture Visualization: An Evaluation Framework and Its Application

Software Architecture Visualization: An Evaluation Framework and Its Application

Visualization of the Static Aspects of Software: A Survey

Software Architecture Reconstruction: A Process-Oriented Taxonomy

Contact Info

Product

Resources

About