The Oahu code map showed that a single map could represent an entire software project in a way that was meaningful to all the developers on the team.
Could ubiquitous hand-drawn code map diagrams become a thing of the past?
Not mentioned: System of Preject level requirements/specifications and corresponding system/project level tests. Are there such documents in your development environment? Can you map requirements to the code? Can code maps help you see the impact from a change in the requirements?