1 The vast majority of code suffers from poor structure - a huge driver of cost - making it difficult or impossible to know the impact of changes, what to test, where to add code.
2 Restructure101 is focused exclusively on refactoring your software architecture.
Not low level code refactoring but high-level structural refactoring - components, packages, jars, modules, assemblies, directories etc.
Remove component level tangles and see how much more effective the team becomes.
3 With the complexity inherent in today's codebases, the ability to let you see only what you need to see in the context of the whole code-base is key to successful refactoring. Our unique Levelized Structure Maps (LSMs) and their wide range of viewing options deliver the focus you need.
4 Manipulate our LSMs interactively with drag-and-drop simplicity to simulate structural refactorings. With the complexity chart, it's a risk-free heuristic step-by-step process that lets you see the impact of each change, so you always know you are heading in the right direction, allowing you to easily backtrack when necessary.
5 Restructure101's 'notables' highlight and rate the structural issues in your codebase - package tangles, class tangles, 'fat', and unused code so you know exactly where to target your efforts.
6 The goal is to drive the complexity chart toward the origin for a healthier, debt-free codebase, at which point you export your action list.
While the developers see and work through the action list in their IDE, progress can be tracked on a project wide basis in our centralized web based repository, integrated seamlessly with Sonar.
1 Define a reference architecture and layering rules for your whole team.
2 Communicate your architecture to the whole team.
3 Improve your understanding of your codebase from several perspectives with our comprehensive range of visualization tools.
4 Compare - see how your codebase has changed from any previous build - what are the new dependencies, new architecture violations, complexity metrics and trends? You don't need to review everything all the time - just keep an eye on how it's evolving.
5 Measure complexity limits and rule violations at any level: design, package or namespace, class, method.
1 Decide which complexity thresholds and architecture rules will not be violated.
2 Break the build and notify when structural constraints are crossed.
3 Automate the recording and tracking of architecture, violations, and complexity debt over time with the Structure101 web application and/or our Sonar plugin.
Integrates seamlessly with continuous integration and build environments such as Hudson, Maven, Ant, TeamCity and MS Build.