Skip to content
Free planNo credit card requiredStart writing

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “Software visualization”

Software Visualization

Matteo Migliavacca · 2008

Un immagine vale più di mille parole?Guardando la situazione attuale dei tool usati dal mondo dell’ingegneria del software si direbbe forse di no. Esistono tecnologie e ritrovati, sviluppati nel campo della Software Visualization che possano rivoluzionare il modo tradizionale di interazione con il software? Questa passeggiata nel mondo della Software Visualization cerca di rispondere a queste domande, e speriamo faccia nascere curiosità e interesse nei confronti di un campo tanto affascinante 1. INTRODUZIONE L’utilizzo della grafica come mezzo per lo sviluppo del software è un campo di ricerca non affatto nuovo, ebbe infatti le sue origini nel 1960 ma divenne un settore di ricerca consolidato negli anni 80. L’interesse verso le sue tematiche

Cited by 0

Software visualization

S. Diehl · Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005. · 2005

Cited by 32

Software visualization

Li, PeiLing · Spectrum Research Repository (Concordia University) · 2003

Software visualization is a significant force in software engineering. As the sizes of software systems are becoming larger and more complex, program comprehension is becoming more difficult. The tasks of program comprehension involve implementation, maintenance, testing, debugging, mental model construction and verification. Software visualization is one promised way to support the tasks of program comprehension. Through software visualization, graphics and animations are built to help illustrate and present the computer program. In recent years, many related visualization techniques have been developed and used to build visualization tools. The major goal of visualization tools is to support program comprehension.

Cited by 0

Software visualization

Ploeg, A.J. (Atze) van der · Data Archiving and Networked Services (DANS) · 2012

Cited by 0

Matlab Visualization Software

Artur Saudabayev, Atakan Huseyin Varol, Zhanibek Rysbek et al. · Figshare · 2017

Matlab software for visualizing action camera, depth and inertial motion data channels.

Cited by 0Open access

Matlab Visualization Software

Saudabayev, Artur, Varol, Atakan Huseyin, Rysbek, Zhanibek et al. · Figshare · 2018

Matlab software for visualizing action camera, depth and inertial motion data channels.

Cited by 0Open access

Software Evolution Visualization

Voinea, L., Telea, A. C., Wijk, J. J. van · University of Groningen research database (University of Groningen / Centre for Information Technology) · 2005

Cited by 0

Software evolution visualization

Lucian Voinea · Data Archiving and Networked Services (DANS) · 2007

Software has today a large penetration in all infrastructure levels of the society. This penetration took place rapidly in the last two decades and continues to increase. In the same time, however, the software industry gets confronted with two increasingly serious challenges: complexity and evolution. The size of software applications is growing larger. This leads to a steep increase in complexity. Additionally, the change in requirements and available technologies leads to softwaremodifications. As a result, a huge amount of code needs to be maintained and updated every year (i.e. the legacy systems problem). Software visualization is a very promising solution to the abovementioned challenges of the software industry. It is a specialized branch of information visualization, which visualizes artifacts related to software and its development process. In this thesis we try to use visualization of software evolution to get insight in the development context of software and in its evolution trends. The main question we try to answer with this is: "How to enable users to get insight in the evolution of a software system?" Our final goal is to improve both software understanding and decision making during the maintenance phase of large software projects. We start by positioning the thesis in the context of related research in the field of both software evolution analysis and visualization. Then we perform an analysis of the software evolution domain to formalize the problems specific to this field. To this end, we propose a generic system evolution model and a structure based meta-model for software description. Consequently, we use these models to give a formal definition of software evolution. Next we propose a visualization model for software evolution, based on the previously introduced software evolution model. The visualization model consists of a number of steps with specific guidelines for building visual representations. Then we present three applications that make use of the proposed visualization model to support real life software evolution analysis scenarios. These applications cover the most commonly used software description models in industry: file as a set of code lines, project as a set of files, and project as a unitary entity. For each application, we formulate relevant use cases, present specific implementation aspects, and discuss results of use case evaluation experiments. We also propose in this thesis a novel visualization of data exchange processes in Peer-to-Peer networks. While this does not address software evolution, it tackles comparable issues, e.g., the dynamic evolution of a set of interrelated data artifacts. The aim of presenting this visualization is twofold. First, we illustrate how to visualize different types of software-related data than purely software source code. Secondly, we show that the visual and interaction techniques that we have developed in the context of software evolution visualization can be put to a good use for other applications as well. We conclude the thesis with an inventory of reoccurring problems and solutions we have discovered in the visualization of software evolution. Additionally, we identify generic issues that transcend the border of the software evolution domain and we present them together with a set of recommendation for their broader applicability. Finally, we outline the remaining open issues, and the possible research directions that can be followed to address them.

Cited by 7Open access

1 Software Visualization

Information Visualization, Carsten Görg, From John Stasko et al. · 2008

“The use of the crafts of typography, graphic design, animation, and cinematography with modern humancomputer interaction and computer graphics technology to facilitate both the human understanding and effective use of computer software.” Price, Baecker and Small, ‘98

Cited by 0

Little Manila Visualization Little Manila Visualization Software Program Software Program

Salyers, Josh, Thomasson, Danielle, Sabbatino, Kyle et al. · Scholarly Commons (University of the Pacific) · 2017

This 3d simulation is built using gaming software. The graphics quality and download time can vary significantly based on the specification of the computer running this program. Instructions:Click on the Download button and save the .zip file to your computer. It will begin to download. (This can take a while initially). Once the file has downloaded, unzip the folder and click on the .exe file to play the game. Version: The current version is only compatible with Windows operating system.

Cited by 0

ABSTRACT Interactive Software Visualization

2009

A software architecture is an abstraction of a software system, which is indispensable for many software engineering tasks. Unfortunately, in many cases architectural information is not available, outdated, or inappropriate for the task at hand. Software architecture reconstruction concerns obtaining architectural information from an existing system. Currently, this process is unstructured, requires much manual effort, leads to results that are hard to understand, and does not provide quantitative information on software quality aspects. The RECONSTRUCTOR project aims at raising the state of the art in software architecture reconstruction. My research within RECONSTRUCTOR focuses on interactive visualization of software systems and it is basically concerned with the following questions: “How can architectural information, represented in different, interrelated views, be visualized and manipulated?” and “How can the visualization support the iterative reconstruction process and help to interpret and validate the findings of a software architecture evaluation?” 1

Cited by 0

Software Visualization: An Overview

Luis M. Gómez-Henríquez · 2001

Keywords:
\nVisualization, Software Visualization, Program
\nDebugging, Performance Debugging
\n
\nThis article provides a general overview of software visualization. To that end, we first present the concept
\nof visualization and its features, and later we summarize some of its main applications in Computer Science.
\nThe main part of this article is devoted to describing the general discipline of software visualization, by
\ndefining it and its main problems and uses. Throughout the paper we will refer to some of the most
\noutstanding actual systems which we think are suitable to illustrate the corresponding concept.
\n
\nThe objective of this paper is mainly to give an introduction,
\nproviding an overall view of SV discipline. In order to meet this
\ngoal, we try to generalize the most significant aspects of real
\nSV systems instead of merely describing their particular features.
\nThis article contains a brief summary of our knowledge
\non the matter, which began with our experience in the design
\nand development of Vestal [Tomás et al. 91] for Ada concurrent
\nprograms and VisAndOr [Carro et al. 93] which visualizes
\nparallel execution of Prolog programs. Both systems and some
\ntheoretical work converged on our Ph. D. Thesis [Gómez 95].
\nIn 1998, the first book devoted to SV was published:
\nSoftware
\nVisualization: Programming as Multimedia Experience
\n[Stasko et al. 98]. However, this book, in our humble opinion,
\nis no more than a compilation of papers about specific SV tools.
\nOnly the brief section introductions have some “systematic”
\ncontent.

Cited by 0