Academic literature on the topic 'Source code visualization'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Source code visualization.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Source code visualization"

1

Jakobsen, Mikkel Rønne, and Kasper Hornbæk. "Transient or permanent fisheye views: A comparative evaluation of source code interfaces." Information Visualization 11, no. 2 (July 18, 2011): 151–67. http://dx.doi.org/10.1177/1473871611405643.

Full text
Abstract:
Transient use of information visualization may support specific tasks without permanently changing the user interface. Transient visualizations provide immediate and transient use of information visualization close to and in the context of the user’s focus of attention. Little is known, however, about the benefits and limitations of transient visualizations. We describe an experiment that compares the usability of a fisheye view that participants could call up temporarily, a permanent fisheye view, and a linear view: all interfaces gave access to source code in the editor of a widespread programming environment. Fourteen participants performed varied tasks involving navigation and understanding of source code. Participants used the three interfaces for between four and six hours in all. Time and accuracy measures were inconclusive, but subjective data showed a preference for the permanent fisheye view. We analyse interaction data to compare how participants used the interfaces and to understand why the transient interface was not preferred. We conclude by discussing seamless integration of fisheye views in existing user interfaces and future work on transient visualizations.
APA, Harvard, Vancouver, ISO, and other styles
2

Al-Msie'deen, R. A. "Tag Clouds for Object-Oriented Source Code Visualization." Engineering, Technology & Applied Science Research 9, no. 3 (June 8, 2019): 4243–48. http://dx.doi.org/10.48084/etasr.2706.

Full text
Abstract:
Software visualization helps software engineers to understand and manage the size and complexity of the object-oriented source code. The tag cloud is a simple and popular visualization technique. The main idea of the tag cloud is to represent tags according to their frequency in an alphabetical order where the most important tags are highlighted via a suitable font size. This paper proposes an original approach to visualize software code using a tag cloud. The approach exploits all software identifier names to visualize software code as a tag cloud. Experiments were conducted on several case studies. To validate the approach, it is applied on NanoXML and ArgoUML. The results of this evaluation validate the relevance and the performance of the proposed approach as all tag names and their frequencies were correctly identified. The proposed tag cloud visualization technique is a helpful addition to the software visualization toolkit. The extracted tag cloud supports software engineers as they filter and browse data.
APA, Harvard, Vancouver, ISO, and other styles
3

Kadar, Rozita, Jamal Othman, and Naemah Abdul Wahab. "Survey on Ontology-Based Visualization Techniques towards Program Comprehension Application." Journal of Computing Research and Innovation 3, no. 1 (October 17, 2018): 19–29. http://dx.doi.org/10.24191/jcrinn.v3i1.66.

Full text
Abstract:
A key challenge to software maintainers during performing the software maintenance is to comprehend a source code. Source code plays an important role in aiding software maintainers to get conversant with a software system since some system documentations are often unavailable or outdated. Although there are many researches that have discussed the different strategies and techniques to overcome the program comprehension problem, there exists only a shallow knowledge about the challenges software maintainers face when trying to understand a software system through reading source code. In order to make source code more comprehensible, it needs to make an enhancement regarding to the source code presentation by transforming it into a different view. From the literature review, we found that there are lacks of study that consider the use of knowledge representation to represent source code. Hence, the aim of this work is to review the existing techniques for source code representation based on knowledge representation that could help developers to reduce the amount of their effort needed to understand a source code.
APA, Harvard, Vancouver, ISO, and other styles
4

Luo, Yi, and Yanying Han. "Source Code Visualization in Linux Environment Based on Hierarchica Layout Algorithm." Information Technology Journal 12, no. 8 (April 1, 2013): 1522–30. http://dx.doi.org/10.3923/itj.2013.1522.1530.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

ISHIDA, Naoto, Takashi ISHIO, Yuta NAKAMURA, Shinji KAWAGUCHI, Tetsuya KANDA, and Katsuro INOUE. "Visualization of Inter-Module Dataflow through Global Variables for Source Code Review." IEICE Transactions on Information and Systems E101.D, no. 12 (December 1, 2018): 3238–41. http://dx.doi.org/10.1587/transinf.2018edl8104.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Ovchinnikova, Viktoria. "Obtaining and Visualization of the Topological Functioning Model from the UML Model." Applied Computer Systems 18, no. 1 (December 1, 2015): 43–51. http://dx.doi.org/10.1515/acss-2015-0018.

Full text
Abstract:
Abstract A domain model can provide compact information about its corresponding software system for business people. If the software system exists without its domain model and documentation it is time-consuming to understand its behavior and structure only from the code. Reverse Engineering (RE) tools can be used for obtaining behavior and structure of the software system from source code. After that the domain model can be created. A short overview and an example of obtaining the domain model, Topological Functioning Model (TFM), from source code are provided in the paper. Positive and negative effects of the process of TFM backward derivation are also discussed.
APA, Harvard, Vancouver, ISO, and other styles
7

Wan, Ying, Chuan Qi Tan, Zhi Gang Wang, Guo Qiang Wang, and Xiao Jin Hong. "An Effective Visual System for Static Analysis of Source Code." Advanced Materials Research 433-440 (January 2012): 5453–58. http://dx.doi.org/10.4028/www.scientific.net/amr.433-440.5453.

Full text
Abstract:
In the software development lifecycle, code static analysis takes an important part in building secure software. To help discover the potential security issues in source code, large numbers of static analysis tools are developed. But the results generated by them display in the form of pure text, so it is time-consuming for developers to analyze these text messages, and it is difficult for developers to concentrate on the most interesting defects in huge data. In this paper, we have developed a visualization system oriented to Java source code, which presents the results in graphics from a developer’s point of view, to help developers to analysis code defects. A novel layout is proposed to visualize software source code in a hierarchy way, which shows the physical structure of the software. A visual overview and powerful interaction is provided in this system which allows the developer to focus on the most pressing defects within huge volumes of source code.
APA, Harvard, Vancouver, ISO, and other styles
8

Cruz, da, Rangel Henriques, and João Varanda. "Constructing program animations using a pattern based approach." Computer Science and Information Systems 4, no. 2 (2007): 97–114. http://dx.doi.org/10.2298/csis0702097c.

Full text
Abstract:
The aim of this paper is to discuss how our pattern-based strategy for the visualization of data and control flow can effectively be used to animate the program and exhibit its behavior. That result allows us to propose its use for Program Comprehension. The animator uses well known compiler techniques to inspect the source code in order to extract the necessary information to visualize it and understand program execution. We convert the source program into an internal decorated (or attributed) abstract syntax tree and then we visualize the structure by traversing it, and applying visualization rules at each node according to a pre-defined rule-base. In order to calculate the next step in the program execution, a set of rewriting rules are applied to the tree. The visualization of this new tree is shown and the program animation is constructed using an iterative process. No changes are made in the source code, and the execution is simulated step by step. Several examples of visualization are shown to illustrate the approach and support our idea of applying it in the context of a Program Comprehension environment.
APA, Harvard, Vancouver, ISO, and other styles
9

Grivainis, Mark, Zuojian Tang, and David Fenyö. "TranspoScope: interactive visualization of retrotransposon insertions." Bioinformatics 36, no. 12 (April 16, 2020): 3877–78. http://dx.doi.org/10.1093/bioinformatics/btaa244.

Full text
Abstract:
Abstract Motivation Retrotransposition is an important force in shaping the human genome and is involved in prenatal development, disease and aging. Current genome browsers are not optimized for visualizing the experimental evidence for retrotransposon insertions. Results We have developed a specialized browser to visualize the evidence for retrotransposon insertions for both targeted and whole-genome sequencing data. Availability and implementation TranspoScope’s source code, as well as installation instructions, are available at https://github.com/FenyoLab/transposcope.
APA, Harvard, Vancouver, ISO, and other styles
10

Alamin M, Hind, and Hany H. Ammar. "Concerns-Based Reverse Engineering for Partial Software Architecture Visualization." JOIV : International Journal on Informatics Visualization 4, no. 2 (May 26, 2020): 58. http://dx.doi.org/10.30630/joiv.4.2.357.

Full text
Abstract:
Recently, reverse engineering (RE) is becoming one of the essential engineering trends for software evolution and maintenance. RE is used to support the process of analyzing and recapturing the design information in legacy systems or complex systems during the maintenance phase. The major problem stakeholders might face in understanding the architecture of existing software systems is that the knowledge of software architecture information is difficult to obtain because of the size of the system, and the existing architecture document often is missing or does not match the current implementation of the source code. Therefore, much more effort and time are needed from multiple stakeholders such as developers, maintainers and architects for obtaining and re-documenting and visualizing the architecture of a target system from its source code files. The current works is mainly focused on the developer viewpoint. In this paper, we present a RE methodology for visualizing architectural information for multiple stakeholders and viewpoints based on applying the RE process on specific parts of the source code. The process is driven by eliciting stakeholders’ concerns on specific architectural viewpoints to obtain and visualize architectural information related these concerns. Our contributions are three fold: 1- The RE methodology is based on the IEEE 1471 standard for architectural description and supports concerns of stakeholder including the end-user and maintainer; 2- It supports the visualization of a particular part of the target system by providing a visual model of the architectural representation which highlights the main components needed to execute specific functionality of the target system, 3- The methodology also uses architecture styles to organize the visual architecture information. We illustrate the methodology using a case study of a legacy web application system.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Source code visualization"

1

Hopfner, Marbod. "Source Code Analysis, Management, and Visualization for PROLOG." Doctoral thesis, kostenfrei, 2008. http://www.opus-bayern.de/uni-wuerzburg/volltexte/2009/3630/.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Kacan, Denis, and Darius Sidlauskas. "Information Visualization and Machine Learning Applied on Static Code Analysis." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3033.

Full text
Abstract:
Software engineers will possibly never see the perfect source code in their lifetime, but they are seeing much better analysis tools for finding defects in software. The approaches used in static code analysis emerged from simple code crawling to usage of statistical and probabilistic frameworks. This work presents a new technique that incorporates machine learning and information visualization into static code analysis. The technique learns patterns in a program’s source code using a normalized compression distance and applies them to classify code fragments into faulty or correct. Since the classification frequently is not perfect, the training process plays an essential role. A visualization element is used in the hope that it lets the user better understand the inner state of the classifier making the learning process transparent. An experimental evaluation is carried out in order to prove the efficacy of an implementation of the technique, the Code Distance Visualizer. The outcome of the evaluation indicates that the proposed technique is reasonably effective in learning to differentiate between faulty and correct code fragments, and the visualization element enables the user to discern when the tool is correct in its output and when it is not, and to take corrective action (further training or retraining) interactively, until the desired level of performance is reached.
APA, Harvard, Vancouver, ISO, and other styles
3

Wihlborg, Åsa. "Using an XML-driven approach to create tools for program understanding : An implementation for Configura and CET Designer." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-66414.

Full text
Abstract:
A major problem during development and maintenance of software is lack of quality documentation. Many programers have problems identifying which infor- mation is relevant for someone with no knowledge of the system and therefore write incomplete documentation. One way to get around these problems would be to use a tool that extracts information from both comments and the actual source code and presents the structure of the program visually. This thesis aims to design an XML-driven system for the extraction and pre- sentation of meta information about source code to that purpose. Relevant meta information in this case is, for example, which entities (classes, methods, variables, etc.) exist in the program and how they interact with each other. The result is a prototype implemented to manage two company developed lan- guages. The prototype demonstrates how the system can be implemented and show that the approach is scalable. The prototype is not suitable for commercial use due to its abstraction level, but with the help of qualified XML databases there are great possibilities to build a usable system using the same techniques in the future.
Ett stort problem under utvecklingen och underhållet av mjukvara är bristande dokumentation av källkoden. Många programmerare har svårt att identifiera vilken information som är viktig för någon som inte är insatt i systemet och skriver därför bristfällig dokumentation. Ett sätt att komma runt dessa problem skulle vara att använda verktyg som extraherar information från såväl kommentarer som faktisk källkod och presenterar programmets struktur påett tydligt och visuellt sätt. Det här examensarbetet ämnar att designa ett system för XML-driven extra- hering och presentation av metainformation om källkoden med just det syftet. Metainformationen som avses här är exempelvis vilka entiteter (klasser, metoder, variabler, mm.) som finns i källkoden samt hur dessa interagerar med varandra. Resultatet är en prototyp implementerad för att hantera tvåföretagsutvecklade språk. Prototypen demonstrerar hur systemet kan implementeras och visar att me- toden är skalbar. Prototypen är abstraktionsmässigt inte lämplig för kommersiellt bruk men med hjälp av kvalificerade XML-databaser finns det stora möjligheter att i framtiden bygga ett praktiskt användbart system baserat på samma tekniker.
APA, Harvard, Vancouver, ISO, and other styles
4

Ekwall, Axel. "Improving technical debt management and communication by visualizing source code : A concept driven design study to explore the concept of using a visualization tool to improve technical debt management and communication." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-280838.

Full text
Abstract:
With the increasing reliance on digital technology in our lives we, more than ever before, depend on software products and services. The development of such products and services is thereby becoming more complex and sophisticated. In these large software projects, developers often have to make compromises or settle for less than optimal solutions in order to reach deadlines or deliver a product to market in time. This can cause what is known in the industry as Technical debt, the accumulation of cost created by "shortcuts" taken during development. The goal of this paper is to design a concept of a visualization tool to aggregate and present an overview of technical debt in a software development project. Based on this goal, the study tries to answer the following question: Can a visualization tool help software development teams manage technical debt by improving awareness and communication about technical debt strategy and priorities?. A literature study on the topics of technical debt management and information visualization techniques is conducted in order to create a foundation for the work in this study. By leveraging concept driven design research, a survey is conducted and based on the results, an interactive prototype is developed and evaluated, in order to answer the research question. The prototype is evaluated through a critique session including semi-structured interviews with expert users working in software development projects. The main findings are that a visualization tool, like the one proposed in this study, could be used to help developers and other stakeholders in software projects to raise awareness about technical debt strategies and priorities. However, more research are required in order to refine the tool and visualizations included in the prototype.
Med det ökande beroendet av digital teknik i våra liv är vi mer än någonsin tidigare beroende av programvaruprodukter och tjänster. Utvecklingen av sådana produkter och tjänster blir därmed mer komplex och sofistikerad. I dessa stora mjukvaruprojekt måste utvecklare ofta göra kompromisser eller nöja sig med mindre än optimala lösningar för att nå deadlines eller leverera en produkt till marknaden i tid. Detta kan orsaka vad som är känt i branschen som teknisk skuld, ackumulering av kostnader som skapas av "genvägar" under utveckling. Målet med denna uppsats är att utforma ett koncept av ett visualiseringsverktyg för att sammanställa och presentera en översikt över teknisk skuld i ett mjukvaruutvecklingsprojekt. Baserat på detta mål försöker studien svara på följande fråga: Kan ett visualiseringsverktyg hjälpa programvaruutvecklingsteam att hantera teknisk skuld genom att förbättra medvetenheten och kommunikationen om teknisk skuld strategi och prioriteringar?. En litteraturstudie om ämnena teknisk skuldförvaltning och informationsvisualiseringstekniker genomförs för att skapa en grund för arbetet i denna studie. Genom att utnyttja konceptdriven designforskning genomförs en enkätundersökning och baserat på resultaten utvecklas och utvärderas en interaktiv prototyp för att besvara forskningsfrågan. Prototypen utvärderas genom en kritiksession med halvstrukturerade intervjuer med expertanvändare som arbetar med mjukvaruutvecklingsprojekt. De viktigaste resultaten är att ett visualiseringsverktyg, som det som föreslås i denna studie, skulle kunna användas för att hjälpa utvecklare och andra intressenter i mjukvaruprojekt att öka medvetenheten om teknisk skuldstrategier och prioriteringar. Dock krävs mer forskning för att förfina verktyget och visualiseringar som ingår i prototypen.
APA, Harvard, Vancouver, ISO, and other styles
5

Moura, Marcello Henrique Dias de. "Comparação entre desenvolvedores de software a partir de dados obtidos em repositório de controle de versão." Universidade Federal de Goiás, 2013. http://repositorio.bc.ufg.br/tede/handle/tede/7944.

Full text
Abstract:
Submitted by Erika Demachki (erikademachki@gmail.com) on 2017-11-06T19:48:59Z No. of bitstreams: 2 Dissertação - Marcello Henrique Dias de Moura - 2013.pdf: 3325482 bytes, checksum: 45be62e46fd5fda90d1d0561482a3d85 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5)
Approved for entry into archive by Erika Demachki (erikademachki@gmail.com) on 2017-11-06T19:49:14Z (GMT) No. of bitstreams: 2 Dissertação - Marcello Henrique Dias de Moura - 2013.pdf: 3325482 bytes, checksum: 45be62e46fd5fda90d1d0561482a3d85 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5)
Made available in DSpace on 2017-11-06T19:49:14Z (GMT). No. of bitstreams: 2 Dissertação - Marcello Henrique Dias de Moura - 2013.pdf: 3325482 bytes, checksum: 45be62e46fd5fda90d1d0561482a3d85 (MD5) license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) Previous issue date: 2013-03-22
Version Control Systems are repositories that store source code changes done by software developers. Research that extracts data from these repositories for analysis can be classified into two groups: those that focus on the development process and the ones that focus on the developers. The present dissertation investigates the second case and contributes to the field by providing: (a) the definition of a history file that summarizes changes made to software in line and file levels, (b) a set of metrics to evaluate the work of the developers; and (c) two approaches for comparing the developers based on their metrics. A computational system that implements these metrics and approaches was built and applied to two case studies of real software development projects. The results obtained in the studies were positive. They were consistent with the general perception of project managers about the work done by the developers. They also leaded to new ideas for improving the research.We believe that these contributions are a step towards a better understanding and characterization of the way about how software developers work.
Repositórios de Controle de Versão são sistemas que armazenam mudanças no código fonte realizadas por desenvolvedores de software. As pesquisas que extraem dados desses repositórios para análise podem ser classificadas em dois grupos: as que focam no processo de desenvolvimento e as que focam no desenvolvedor. O presente trabalho investiga o segundo aspecto contribuindo para o assunto com: (a) a definição de um histórico de arquivos que sumariza as mudanças realizadas no software em nível de linha e de arquivo; (b) um conjunto de métricas visando avaliar o trabalho dos desenvolvedores; e (c) duas propostas de abordagem para comparar os desenvolvedores. Um sistema computacional que implementa essas métricas e as abordagens foi construído, tendo sido aplicado em dois estudos de casos envolvendo projetos reais de desenvolvimento de software. Os resultados obtidos nos estudos foram positivos, coincidindo, em geral, com a percepção de gerentes de projetos sobre o trabalho dos desenvolvedores e apontando para novas ideias de evolução da pesquisa. Consideramos que este é um passo no sentido de entender e caracterizar melhor a forma de trabalho dos desenvolvedores.
APA, Harvard, Vancouver, ISO, and other styles
6

Hopfner, Marbod [Verfasser]. "Source code analysis, management, and visualization for PROLOG / vorgelegt von Marbod Hopfner." 2008. http://d-nb.info/994813236/34.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Jridi, Jamel Eddine. "Formulation interactive des requêtes pour l’analyse et la compréhension du code source." Thèse, 2010. http://hdl.handle.net/1866/4856.

Full text
Abstract:
Nous proposons une approche basée sur la formulation interactive des requêtes. Notre approche sert à faciliter des tâches d’analyse et de compréhension du code source. Dans cette approche, l’analyste utilise un ensemble de filtres de base (linguistique, structurel, quantitatif, et filtre d’interactivité) pour définir des requêtes complexes. Ces requêtes sont construites à l’aide d’un processus interactif et itératif, où des filtres de base sont choisis et exécutés, et leurs résultats sont visualisés, changés et combinés en utilisant des opérateurs prédéfinis. Nous avons évalués notre approche par l’implantation des récentes contributions en détection de défauts de conception ainsi que la localisation de fonctionnalités dans le code. Nos résultats montrent que, en plus d’être générique, notre approche aide à la mise en œuvre des solutions existantes implémentées par des outils automatiques.
We propose an interactive querying approach for program analysis and comprehension tasks. In our approach, an analyst uses a set of basic filters (linguistic, structural, quantitative, and user selection) to define complex queries. These queries are built following an interactive and iterative process where basic filters are selected and executed, and their results displayed, changed, and combined using predefined operators. We evaluated our querying approach by implementing recent state-of-the-art contributions on feature location and design defect detection. Our results show that, in addition to be generic; our approach helps improving existing solutions implemented by fully-automated tools.
APA, Harvard, Vancouver, ISO, and other styles
8

Sfayhi, Ahmed. "Génération automatique de configurations et de scénarios d'utilisation d'outils de visualisation à partir de spécifications de tâches d'analyse de logiciels." Thèse, 2015. http://hdl.handle.net/1866/12504.

Full text
Abstract:
Nous proposons une approche qui génère des scénarios de visualisation à partir des descriptions de tâches d'analyse de code. La dérivation de scénario est considérée comme un processus d'optimisation. Dans ce contexte, nous évaluons différentes possibilités d'utilisation d'un outil de visualisation donnée pour effectuer la tâche d'analyse, et sélectionnons le scénario qui nécessite le moins d'effort d'analyste. Notre approche a été appliquée avec succès à diverses tâches d'analyse telles que la détection des défauts de conception.
We propose an approach that derives interactive visualization scenarios from descriptions of code analysis tasks. The scenario derivation is treated as an optimization process. In this context, we evaluate different possibilities of using a given visualization tool to perform the analysis task, and select the scenario that requires the least effort from the analyst. Our approach was applied successfully to various analysis tasks such as design defect detection and feature location.
APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "Source code visualization"

1

Mukherjee, Sudipta. Source Code Analytics With Roslyn and JavaScript Data Visualization. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1925-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Mukherjee, Sudipta. Source Code Analytics With Roslyn and JavaScript Data Visualization. Apress, 2017.

Find full text
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Source code visualization"

1

Mukherjee, Sudipta. "Code Visualization." In Source Code Analytics With Roslyn and JavaScript Data Visualization, 155–65. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1925-6_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Mukherjee, Sudipta. "Code Mining." In Source Code Analytics With Roslyn and JavaScript Data Visualization, 91–130. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1925-6_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Mukherjee, Sudipta. "Code Forensics." In Source Code Analytics With Roslyn and JavaScript Data Visualization, 131–54. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1925-6_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Mukherjee, Sudipta. "Code Quality Metrics." In Source Code Analytics With Roslyn and JavaScript Data Visualization, 15–44. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1925-6_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Mukherjee, Sudipta. "Code Performance Metrics." In Source Code Analytics With Roslyn and JavaScript Data Visualization, 71–90. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1925-6_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Mukherjee, Sudipta. "Meet Roslyn Syntax API." In Source Code Analytics With Roslyn and JavaScript Data Visualization, 1–14. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1925-6_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Mukherjee, Sudipta. "Design Quality Metrics." In Source Code Analytics With Roslyn and JavaScript Data Visualization, 45–69. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1925-6_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Murad, S., I. Passero, and R. Francese. "Metric Pictures: Source Code Images for Visualization, Analysis and Elaboration." In Information Technology and Innovation Trends in Organizations, 279–87. Heidelberg: Physica-Verlag HD, 2011. http://dx.doi.org/10.1007/978-3-7908-2632-6_32.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Matsumoto, Shimpei, Ryo Hanafusa, Yusuke Hayashi, and Tsukasa Hirashima. "Analyzing Reading Pattern of Simple C Source Code Consisting of Only Assignment and Arithmetic Operations Based on Data Dependency Relationship by Using Eye Movement." In Human Interface and the Management of Information. Interaction, Visualization, and Analytics, 545–61. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-92043-6_44.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

van Albada, Sacha J., Jari Pronold, Alexander van Meegen, and Markus Diesmann. "Usage and Scaling of an Open-Source Spiking Multi-Area Model of Monkey Cortex." In Lecture Notes in Computer Science, 47–59. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-82427-3_4.

Full text
Abstract:
AbstractWe are entering an age of ‘big’ computational neuroscience, in which neural network models are increasing in size and in numbers of underlying data sets. Consolidating the zoo of models into large-scale models simultaneously consistent with a wide range of data is only possible through the effort of large teams, which can be spread across multiple research institutions. To ensure that computational neuroscientists can build on each other’s work, it is important to make models publicly available as well-documented code. This chapter describes such an open-source model, which relates the connectivity structure of all vision-related cortical areas of the macaque monkey with their resting-state dynamics. We give a brief overview of how to use the executable model specification, which employs NEST as simulation engine, and show its runtime scaling. The solutions found serve as an example for organizing the workflow of future models from the raw experimental data to the visualization of the results, expose the challenges, and give guidance for the construction of an ICT infrastructure for neuroscience.
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Source code visualization"

1

Bacher, Ivan, Brian Mac Namee, and John D. Kelleher. "The Code Mini-Map Visualisation: Encoding Conceptual Structures Within Source Code." In 2018 IEEE Working Conference on Software Visualization (VISSOFT). IEEE, 2018. http://dx.doi.org/10.1109/vissoft.2018.00023.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Borok-Nagy, Zoltan, Viktor Majer, Jozsef Mihalicza, Norbert Pataki, and Zoltan Porkolab. "Visualization of C++ Template Metaprograms." In 2010 10th IEEE Working Conference on Source Code Analysis and Manipulation (SCAM). IEEE, 2010. http://dx.doi.org/10.1109/scam.2010.16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Servant, Francisco, and James A. Jones. "Chronos: Visualizing slices of source-code history." In 2013 First IEEE Working Conference on Software Visualization (VISSOFT). IEEE, 2013. http://dx.doi.org/10.1109/vissoft.2013.6650547.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Assal, Hala, Sonia Chiasson, and Robert Biddle. "Cesar: Visual representation of source code vulnerabilities." In 2016 IEEE Symposium on Visualization for Cyber Security (VizSec). IEEE, 2016. http://dx.doi.org/10.1109/vizsec.2016.7739576.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Xie, Xinrong, Denys Poshyvanyk, and Andrian Marcus. "3D visualization for concept location in source code." In Proceeding of the 28th international conference. New York, New York, USA: ACM Press, 2006. http://dx.doi.org/10.1145/1134285.1134428.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Krinke, Jens. "Statement-Level Cohesion Metrics and their Visualization." In Seventh IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM 2007). IEEE, 2007. http://dx.doi.org/10.1109/scam.2007.28.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Krinke, Jens. "Statement-Level Cohesion Metrics and their Visualization." In Seventh IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM 2007). IEEE, 2007. http://dx.doi.org/10.1109/scam.2007.4362896.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Beck, Fabian, Fabrice Hollerich, Stephan Diehl, and Daniel Weiskopf. "Visual monitoring of numeric variables embedded in source code." In 2013 First IEEE Working Conference on Software Visualization (VISSOFT). IEEE, 2013. http://dx.doi.org/10.1109/vissoft.2013.6650545.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Bacher, Ivan, Brian Mac Namee, and John D. Kelleher. "On Using Tree Visualisation Techniques to Support Source Code Comprehension." In 2016 IEEE Working Conference on Software Visualization (VISSOFT). IEEE, 2016. http://dx.doi.org/10.1109/vissoft.2016.8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Lin, Chun-Cheng, and Hsu-Chun Yen. "Balloon Views of Source Code and Their Multiscalable Font Modes." In 2007 11th International Conference Information Visualization (IV '07). IEEE, 2007. http://dx.doi.org/10.1109/iv.2007.30.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Source code visualization"

1

Bauer, Andrew, James Forsythe, Jayanarayanan Sitaraman, Andrew Wissink, Buvana Jayaraman, and Robert Haehnel. In situ analysis and visualization to enable better workflows with CREATE-AV™ Helios. Engineer Research and Development Center (U.S.), June 2021. http://dx.doi.org/10.21079/11681/40846.

Full text
Abstract:
The CREATE-AV™ Helios CFD simulation code has been used to accurately predict rotorcraft performance under a variety of flight conditions. The Helios package contains a suite of tools that contain almost the entire set of functionality needed for a variety of workflows. These workflows include tools customized to properly specify many in situ analysis and visualization capabilities appropriate for rotorcraft analysis. In situ is the process of computing analysis and visualization information during a simulation run before data is saved to disk. In situ has been referred to with a variety of terms including co-processing, covisualization, coviz, etc. In this paper we describe the customization of the pre-processing GUI and corresponding development of the Helios solver code-base to effectively implement in situ analysis and visualization to reduce file IO and speed up workflows for CFD analysts. We showcase how the workflow enables the wide variety of Helios users to effectively work in post-processing tools they are already familiar with as opposed to forcing them to learn new tools in order post-process in situ data extracts being produced by Helios. These data extracts include various sources of information customized to Helios, such as knowledge about the near- and off-body grids, internal surface extracts with patch information, and volumetric extracts meant for fast post-processing of data. Additionally, we demonstrate how in situ can be used by workflow automation tools to help convey information to the user that would be much more difficult when using full data dumps.
APA, Harvard, Vancouver, ISO, and other styles
2

Appleyard, Bruce, Jonathan Stanton, and Chris Allen. Toward a Guide for Smart Mobility Corridors: Frameworks and Tools for Measuring, Understanding, and Realizing Transportation Land Use Coordination. Mineta Transportation Institue, December 2020. http://dx.doi.org/10.31979/mti.2020.1805.

Full text
Abstract:
The coordination of transportation and land use (also known as “smart growth”) has been a long-standing goal for planning and engineering professionals, but to this day it remains an elusive concept to realize. Leaving us with this central question -- how can we best achieve transportation and land use coordination at the corridor level? In response, this report provides a review of literature and practice related to sustainability, livability, and equity (SLE) with a focus on corridor-level planning. Using Caltrans’ Corridor Planning Process Guide and Smart Mobility Framework as guideposts, this report also reviews various principles, performance measures, and place typology frameworks, along with current mapping and planning support tools (PSTs). The aim being to serve as a guidebook that agency staff can use for reference, synergizing planning insights from various data sources that had not previously been brought together in a practical frame. With this knowledge and understanding, a key section provides a discussion of tools and metrics and how they can be used in corridor planning. For illustration purposes, this report uses the Smart Mobility Calculator (https://smartmobilitycalculator. netlify.app/), a novel online tool designed to make key data easily available for all stakeholders to make better decisions. For more information on this tool, see https://transweb.sjsu.edu/research/1899-Smart-Growth-Equity-Framework-Tool. The Smart Mobility Calculator is unique in that it incorporates statewide datasets on urban quality and livability which are then communicated through a straightforward visualization planners can readily use. Core sections of this report cover the framework and concepts upon which the Smart Mobility Calculator is built and provides examples of its functionality and implementation capabilities. The Calculator is designed to complement policies to help a variety of agencies (MPOs, DOTs, and local land use authorities) achieve coordination and balance between transportation and land use at the corridor level.
APA, Harvard, Vancouver, ISO, and other styles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography