Analyzing how a CMake-based project has changed over time (Part 1 of 5). This article focuses on getting the project to build successfully, both for the current state of the code and the 4-year-old initial version of the code.
Category: Code Visualization
How Hard is it?
Understand is used to determine how much work it would take to create a database that reads files from a git repository.
Seeing the Unseeable
An advanced workaround for visualizing graphs when the layout fails – and I use it to fix a bug in the UML Class Diagram.
Visualizing Change
Understand lets you step back and visualize exactly what parts of your code have changed and see the impact.
Interesting Graphs about Your Code
A look at the most popular graphs in Understand, from Architecture Graphs to UML.
Making Graphs Interesting
Understand has a lot of different graphs that use the display area quite differently. Natasha goes into detail about how we determine what to display for that critical initial view of a graph.
Code Browsing using Graphical Views
Showing references in Understand graphical trees is a great way to hone in on the calls that built the tree as you debug or try to comprehend source code.
A visual tour of cyclomatic complexity
A visual tour of how maintenance risk increases with cyclomatic complexity
Analyzing the Imperial College COVID simulation model source code
I used Understand’s CodeCheck feature to examine an influential COVID infection simulation program from Imperial College in the UK as it existed in March 2020 when it was being used to advise world leaders.
Making big graphs manageable with “relationship” graphs
Use”Relationship” graphs, which draw sub-graphs between entities, to break big graphs into little graphs and work your way thru them – turning a big thorny graph into a few easy-to-follow graphs.