Use Sum of Coupling to Determine Architectural Significance
In Chapter 8, Use Code as a Cooperative Witness, we looked at change coupling as an interview tool for your codebase. The first step in any interview is to know who you should talk to.
As you’ve already seen, there are multiple reasons for change coupling, and some of the revealed dependencies are both expected and valid. This means that the highest degree of coupling may not be the most interesting. Instead, when striving to make sure our architecture is loosely coupled, we want to focus on the architecturally significant modules. Identifying those is the main purpose of the sum of coupling (SOC) analysis.
Sum of coupling is a behavioral code analysis technique that looks at how ...
Get Your Code as a Crime Scene, Second Edition, 2nd Edition 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.
