In short: This series takes ten ideas from software architecture research and tests them on real code. Most parts measure one idea on open-source projects and report the numbers. Some ideas held up. Picked from 18 months of history, 325 of 1,809 files caught 446 of 701 later likely bug-fix touches. Some did not. Once size and activity were in the model, knowing who owns a file did not help predict later fixes in any of five projects.

Each part explains where an idea comes from, then checks it against data. This page lists the ten parts and what each one found.

Four kinds of evidence

Each part reads one kind of evidence about a system. Parts 2 to 4 read the code's structure: which files import which. Parts 5 to 7 read version history: which files change, and how often. Parts 8 and 9 read the people behind the commits. Part 10 reads runtime traces, the record of real requests.

Part 1 covers the practice the rest feed into. A fitness function is a check with a threshold. It runs on every change and fails the build when one architectural quality slips.

Diagram of the ten parts grouped by the evidence each one reads. Part 1, fitness functions, is the check that runs a measurement on every change. Parts 2 to 4 read code structure, parts 5 to 7 read version history, parts 8 and 9 read people, and part 10 reads runtime traces.
Scroll chart for full detail. The ten parts, grouped by what each one reads.

The ten parts

Where to start

For one number to watch in CI, start with Decoupling Level. In its paper, the metric's coefficient of variation between ordinary releases was 2 percent, against 12 for propagation cost.

If all you have is a git history, start with code hotspots. A hotspot needs only two inputs: how large a file is and how often it changes.

To see what an import graph misses, read change coupling. And before building a trace pipeline for architecture work, read the runtime traces part. For structure, reading the code was cheaper.

I'm Maxat, a software engineer testing architecture research against real data. Corrections and questions are welcome.