The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.06 - November/December (2010 vol.27)
pp: 46-53
Alexandru Telea , University of Groningen, Groningen
Lucian Voinea , SolidSource BV, Eindhoven
Hans Sassenburg , SE-CURE, Lenk
ABSTRACT
Many visualization tools offer software professionals insights to large-scale system architectures. However, despite recent advances in the software-visualization field and significant investments in constructing effective tools, few of these tools have a prominent effect on the software industry. The authors analyze the possible causes of this state of affairs, based on their industry experience. They argue for framing visualization tool adoption in a lean development setting as a value-added versus waste proposition. They examine this model for three types of potential visualization stakeholders: technical users, project managers, and consultants. For each stakeholder type, they observe different values and waste definitions and derive potential adoption guidelines for visualization tools. The Web extra is an erratum that contains a correction to Figure 1's Rigi URL.
INDEX TERMS
software engineering, software tools, visualization
CITATION
Alexandru Telea, Lucian Voinea, Hans Sassenburg, "Visual Tools for Software Architecture Understanding: A Stakeholder Perspective", IEEE Software, vol.27, no. 6, pp. 46-53, November/December 2010, doi:10.1109/MS.2010.115
REFERENCES
1. K. Gallagher, A. Hatch, and M. Munro, "Software Architecture Visualization: An Evaluation Framework and Its Application," IEEE Trans. Visualization and Computer Graphics vol. 34, no. 2, 2008, pp. 260–270.
2. M. Lanza and R. Marinescu, Object-Oriented Metrics in Practice—Using Software Metrics to Characterize, Evaluate, and Improve the Design of Object-Oriented Systems, Springer, 2008.
3. S. Diehl, Software Visualization—Visualizing the Structure, Behaviour, and Evolution of Software Springer, 2007.
4. K.D. Babu, P. Govindarajulu, and A.A. Kumari, "Development of a Conceptual Tool for Complete Software Architecture Visualization: DArch," Int'l J. Computer Science and Network Security, vol. 9, no. 4, 2009, pp. 277–286.
5. S. Charters, N. Thomas, and M. Munro, "The End of the Line for Software Visualization?" Proc. 2nd IEEE Int'l Workshop Visualizing Software for Understanding and Analysis (Vissoft 03), IEEE CS Press, 2003, pp. 27–35.
6. S.P. Reiss, "The Paradox of Software Visualization," Proc. 3rd IEEE Int'l Workshop Visualizing Software for Understanding and Analysis (Vissoft 05), IEEE CS Press, 2005, pp. 59–63.
7. A. Bessey et al., "A Few Billion of Lines of Code Later: Using Static Analysis to Find Bugs in the Real World, Comm. ACM, vol. 53, no. 2, 2010, pp. 66–75.
8. M. Poppendieck and T. Poppendieck, Lean Software Development: An Agile Toolkit for Software Development Managers, Addison-Wesley, 2006.
9. M. Sensalire, P. Ogao, and A. Telea, Model-Based Analysis of Adoption Factors for Software Visualization Tools in Corrective Maintenance, tech. report SVCG-RUG-10-2010, Univ. of Groningen, the Netherlands, 2010; www.cs.rug.nl/~alext/PAPERSSen10.pdf.
10. A. Telea and L. Voinea, "A Tool for Optimizing the Build Performance of Large Software Code Bases," Proc. IEEE Conf. Software Maintenance and Reengineering (CSMR 10), IEEE CS Press, 2010, pp. 323–325.
11. L. Voinea and A. Telea, "Visual Querying and Analysis of Large Software Repositories," Empirical Software Eng., vol. 14, no. 3, 2009, pp. 316–340.
12. A. Telea and L. Voinea, "Case Study: Visual Analytics in Software Product Assessments," Proc. 5th IEEE Int'l Workshop Visualizing Software for Understanding and Analysis (Vissoft 09), IEEE CS Press, 2009, pp. 65–72.
6 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool