{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/911744aecee14626a18d89730c26ae50\" frameborder=\"0\" width=\"1510\" height=\"1132\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1132,"width":1510,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1132,"thumbnail_width":1510,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/911744aecee14626a18d89730c26ae50-6fa76a472e8c7440.gif","duration":250.459556,"title":"Creating Intended GC Toolkit Architecture","description":"In a recent blog post Chris Chedgey reviewed the GC Toolkit project using Sonar's current architecture view. He observed that the larger module had three distinct groupings of code with clear dependencies, and thought it could be beneficial to move two of those groupings into new modules. In this Loom he shows how to create that intended architecture model by adding the new modules, capturing the current dependency structure, adding placeholders for the 2 new modules, GCToolkitEvent and GCToolkitUtils, and wiring their dependencies. Finally he creates directives to move code from its current location into the new modules."}