Part 2Dissect Your Architecture

Part I showed you how to identify offending code in your system. Now we’ll look at the bigger picture.

In this part, you’ll learn to evaluate your software architecture against the modifications you make to your code. The techniques let you identify signs of structural decay, provide refactoring directions, and suggest new modular boundaries in your design. And it all starts with forensics. Let’s see what an innocent robber can teach us about software design.

Get Your Code as a Crime Scene now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.