Analyzing how a CMake-based project has changed over time (Part 4 of 5). This article focuses on creating a trendline of changes to avoid the artifacts caused by non-linear history.
Category: Code Visualization
CMake Compare Part 5: Author Awards
Analyzing how a CMake-based project has changed over time (Part 5 of 5). This article focuses on calculating statistics by author given Understand databases for many time points.
CMake Compare Part 3: Violation Trends
Analyzing how a CMake-based project has changed over time (Part 3 of 5). This article focuses on creating a CodeCheck Violation trend line from multiple databases representing different time points in GitAhead.
CMake Compare Part 2: Automation
Analyzing how a CMake-based project has changed over time (Part 2 of 5). Using command-line tools to create hundreds of comparison databases and constructing a trend line of analysis errors over time
CMake Compare Part 1: Creation
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.
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.