Explore an interactive structural model of your codebase. Specify API’s, dependencies, and layering. Find regions of complex structure or API violations. Figure out how to break monoliths into modular structures. Simulate structural refactoring work before time is spent on major code editing. Share action lists and specs with Workspace and Build to make it happen.
Check and record your projects’ structure as it changes. Report on new or worsening structural complexity, API and dependency violations. Applies specs created by Studio to the new code, and records data for tracking in Dashboard. Plugs into your build or CI system and integrates with code quality platforms such as Hudson/Jenkins, Maven, SonarQube, etc.
Track structural over-complexity, the degree of specification and modularity, and the number of API violations over time. See lists of specific problem code items and containers, including which problems are new/fixed or got worse/better in the last build.
Who uses what?
The Structure101 components can be used independently but are most effective when used together to realize the team’s structural priorities. Those wearing the architect’s hat will generally use Studio to set up the Structure101 project and specify action lists and API specs. These are then visible to programmers via Workspace who benefit from consistent architectural understanding and guidance as it relates to their immediate activities. Dashboards let team leads and managers track progress toward structural and architectural goals.