Analyze the Evolution on a System Level
You’ve already learned to analyze temporal coupling between individual modules. Now we’re raising the abstraction level to focus on system boundaries. We start with just two boundaries: the production code and the test code.
Specify Your Architectural Boundaries
The first step is to define application code and test code. In Code Maat, which we’re returning to for this analysis, the definition is simple: everything under the src/code_maat directory is application code, and everything located in test/code_maat is test code.
Once we’ve located the architectural boundaries, we need to tell Code Maat about them. We do that by specifying a transformation. Open a text editor and type in the following text:
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.
