T. Ball and S. G. Eick. Software visualization in the large. IEEE Computer, 29(4):33--43, 1996.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....by results from our prior work [17] 18] where we converted a standalone AMS executable into a component that evolved overall system architecture resulting in a better maintenance platform for AMS, the feature rich legacy system that we used for our case study. While there are techniques[2][13] 15] 31] 32] to locate program features using execution slices, they are predominantly used for system debugging rather than evolution. A contribution of this paper is to provide a practical model for features that can be used in conjunction with slicing. Our methodology suggests using any ....

T. Ball, "Software visualization in the large", IEEE Computer, VOL 29 NO 4, Apr. 1996, pp. 33-43.

....better understanding of a program from its development history. The system attempts to synthesize views of the requirements of the software, the implementation technology, the development process and the organization of developers based on the version control system logs and the source code. Ball [1] describes a system that visualizes many di#erent aspects of software using three di#erent types of representation: Line representation shows program source at three scaling levels, giving both detail and overview. Pixel representation shows each line of code as an individual pixel. Hierarchical ....

T. Ball and S. G. Eick. Software visualization in the large. IEEE Computer, 29(4):33--43, 1996.

....faults in a program. 1. INTRODUCTION Attempts to reduce the number of delivered faults in software are estimated to consume 50 to 80 of the development and maintenance e#ort [4] Among the tasks required to reduce the number of delivered faults, debugging is one of the most time consuming [3, 15], and locating the errors is the most di#cult component of this debugging task (e.g. 16] Clearly, techniques that can reduce the time required to locate faults can have a significant impact on the cost and quality of software development and maintenance. Pan and Spa#ord analyzed the debugging ....

....of the Tarantula system in Continuous mode. nately, showing program source code as displayed in Figures 2 and 3 for any large system is problematic as it would require a tremendous amount of screen real estate. Thus, we utilize the visual mapping introduced by Eick et al. in the SeeSoft system [3, 6] to map each source code statement to a short, horizontal line of pixels. This zoomed away perspective lets more of the software system be presented on one screen. We have built a program visualization system, Tarantula, that implements this visual mapping. Tarantula is written in Java and ....

[Article contains additional citation context not shown here]

T. Ball and S. G. Eick. Software visualization in the large. Computer, 29(4):33--43, Apr. 1996.

....represent the nesting level. On top of each container the name of the associated file is visible. When manipulating a container in the 3D space, the name of the file always faces the camera. 1. Description Source Viewer 3D (sv3D) is a software visualization framework that builds on the SeeSoft [1, 2] metaphor. It brings a number of enhancements and extensions over SeeSoft type representations. In particular it creates 3D renderings of the raw data and various artifacts of the software system and their attributes can be mapped to the 3D metaphors at different abstraction levels. It implements ....

....tools have a variety of uses in assisting the user solving software engineering and comprehension tasks. sv3D can be used for all these tasks such as: fault localization [4] visualization of execution traces [6] source code browsing [3] impact analysis, evolution, complexity, and slicing [1], etc. In addition, by allowing visualization of additional information (via 3D) sv3D can be used for solving other more complex tasks. For example, in the case of Tarantula [4] using height instead of brightness would improve the visualization and make the user s task easier. At this point ....

Ball, T. and Eick, S., "Software Visualization in the Large", Computer, vol. 29, no. 4, April 1996, pp. 33-43.

....pictures to describe actions, one can view the tool as a software visualization system. Other work on software visualization typically involves the development of new visualization techniques independent of the application display whether they be visualizations of the source code itself [2] or perhaps visualizations of more abstract entities such as algorithms and data structures [5, 8] Some graphical applications use before after pictures as a way of describing the previous states of an application in a way readily understandable by the user. For example, the work on editable ....

....call is represented by a horizontal bar, whose color indicates the relevance of that function to the action. This dynamic visualization is similar to the static visualizing of source code where each line of code is shown as a line of pixels color coded to highlight some aspect of the code [2]. 8 6.3 Software Clustering Much of the design recovery literature involves software clustering. Software clustering attempts to automatically decompose software systems into meaningful subsystems to facilitate understanding of those systems (e.g. for maintenance tasks) or to reuse subsystems ....

T. Ball and S. G. Eick. Software visualization in the large. IEEE Computer, 29(4):33--43, 1996.

....to spectra based on more expensive profiling, such as path spectra [23] Other researchers have provided visualization techniques for testing artifacts. For example, Ball and Eick present a system for visualizing information, including testing information such as coverage, for large programs [3], and Telcordia Technologies has several tools that combine analysis and visualization of testing artifacts to help software maintainers [24] Although there have been some successes in using testing artifacts for software engineering tasks, this research is in its infancy. Additional research ....

T. Ball and S. G. Eick. Software visualization in the large. Computer, 29(4):33-43, April 1996.

....debugging, testing 1. INTRODUCTION Attempts to reduce the number of delivered faults 1 in software are estimated to consume 50 to 80 of the development and maintenance e ort [4] Among the tasks required to reduce the number of delivered faults, debugging is one of the most time consuming [3, 15], and locating the errors is the most dicult component of this debugging task (e.g. 16] Clearly, techniques that can reduce the time required to locate faults can have a signi cant impact on the cost and quality of software development and maintenance. 1 In our discussion, we use errors, ....

....suspicious statements in the program. Unfortunately, showing program source code as displayed in Figures 2 and 3 for any large system is problematic as it would require a tremendous amount of screen real estate. Thus, we utilize the visual mapping introduced by Eick et al. in the SeeSoft system[3, 6] to map each source code statement to a short, horizontal line of pixels. This zoomed away perspective lets more of the software system be presented on one screen. We have built a program visualization system, Tarantula, that implements this visual mapping. Tarantula is written in Java and ....

[Article contains additional citation context not shown here]

T. Ball and S. G. Eick. Software visualization in the large. Computer, 29(4):33-43, Apr. 1996.

....of delivered faults are estimated to consume 50 to 80 of the development and maintenance effort [2] Debugging is one of the most time consuming tasks required to reduce the number of delivered faults in a program. Thus, researchers have investigated techniques to assist with debugging (e.g. [1, 4]) However, these techniques often do not scale to large programs or they require extensive manual intervention. This lack of effective techniques hinders the development and maintenance process. Studies show that locating the errors 1 is the most difficult and time consuming component of the ....

....other program visualization views or supplement TARAN TULA s view with information to visually encode other program attributes such as control flow and calling relations. Along those lines, Ball and Eick created a visualization system that uses the SeeSoft representation to encode program slices [1]. We will explore the addition of program analysis information such as slices, into TARANTULA in the future. We are also investigating possible visualizations for higherlevel abstractions of programs and other techniques to aid in the scalability of our technique. 4. Conclusion This article ....

T. Ball and S. G. Eick. Software visualization in the large. Computer, 29(4):33--43, Apr. 1996.

....that data set and the implicit and explicit relationships between those components. Examples of this started with some of the earliest forms of visual display; the graph structure. Software visualisation tries to address the identified shortcomings of this approach (for example [1] 5] 6] [11] with an overview in [8] but also has to try and overcome the comfort factor of a familiar display, and the view that the representation of nodes and arcs should be suitable for all data that needs to be represented about software. There is plenty of evidence to show where the data used in this ....

T. Ball and S. G. Eick, "Software Visualization in the Large", IEEE Computer, pp33-43, April 1996.

....of something that has no inherent form. Therefore the aim is to visualise the intangible in an effective and useful way. Effective and useful here refers to the visualisation being able to increase the understanding of the user whilst reducing the perceived complexity. Ball and Eick [Ball96] recognise this problem when they write Software is intangible, having no physical shape or size. After it is written, code disappears into files kept on disks. and The invisible nature of software hides system complexity, Walker [Walk95] comments on the software being the ....

T. Ball and S. G. Eick, Software Visualization in the Large, IEEE Computer, pp3343, April

No context found.

T. Ball and S. G. Eick. Software visualization in the large. IEEE Computer, 29(4):33--43, 1996.

No context found.

T. Ball and S. G. Eick. Software visualization in the large. IEEE Computer, 29(4):33--43, 1996.

No context found.

Ball, T. and Eick, S. G., Software visualization in the large, Computer, Vol. 29, No. 4, Apr. 1996, pp. 33--43.

No context found.

T. Ball and S. G. Eick. Software visualization in the large. IEEE Computer, 29(4):33--43, 1996.

No context found.

T. Ball and S. G. Eick. Software visualization in the large. IEEE Computer, 29(4):33--43, April 1996.

No context found.

Ball, T. & Eick, S. (1996), `Software visualization in the large', IEEE Computer 29(4), 33--43.

No context found.

T. Ball and S. G. Eick. Software visualization in the large. IEEE Computer, 29(4):33--43, April 1996.

No context found.

T. Ball and S. Eick. Software visualization in the large. IEEE Computer, pages 33--43, 1996.

No context found.

T. Ball and S. G. Eick. Software visualization in the large. IEEE Computer, 29(4), April 1996.

No context found.

Thomas J. Ball and Stephen G. Eick. Software Visualization in the Large. In IEEE Computer, Vol 29, No. 4, April 1996, pages 33-43.

No context found.

Ball, T.A. and Eick, S.G. (1996). Software visualization in the large. IEEE Computer, 29(4), 33-43.

No context found.

T. Ball and S. G. Eick. Software visualization in the large. IEEE Computer, 29(4), 1996.

No context found.

Thomas Ball and Stephen G. Eick, "Software Visualization in the Large, " IEEE Computer, Vol. 29(4), April 1996.

No context found.

T. Ball. Software visualization in the large. IEEE Computer, 29(4):33--43, April 1996.

No context found.

T. Ball and S. G. Eick. Software visualization in the large. IEEE Computer, 29(4):33--43, 1996.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC