Restructure101

How to create a killer call graph for impact analysis

Posted by on | Featured | No Comments

Sometimes you really want to cut through a code-base to discover all the functions that can get called in response to a specific function being invoked, with all the other code removed from the picture. Or you might be coming … Read More

Tags: , , , , ,

The Structure101 Project Model

Posted by on | Featured | No Comments

So you just opened a Repository project, edited the Architecture diagrams, only to discover that there is no way to save your edits! What is going on here?! Our project model is somewhat convoluted – there is a sort of logic … Read More … Read More

Disentangling .NET Namespaces

Posted by on | Featured | No Comments

If architectural drift is addressed before monolithic code tangles have formed, the higher-level components can be disentangled by relatively low cost/risk relocation of classes between components. Otherwise more invasive class-level surgery is needed – this is possible with Restructure101, but … Read More

Making JUnit 4.8.2 tangle free – a possible solution

Posted by on | Featured | No Comments

The purpose of this exercise was to use Restructure101 to solve tangles in JUnit version 4.8.2. … Read More

Tags: , ,

Introducing Levelized Structure Maps (LSM)

Posted by on | Featured | 2 Comments

Levelized Structure Maps (LSM) are a new, intuitive way to visualize and manipulate software systems. Using LSM, large-scale refactoring to remove dependency tangles and other over-complexity, becomes second nature. LSM are the core of Restructure101. Items in the LSM are levelized … Read More … Read More

Structure101 New Feature: Class Name-map

Posted by on | Featured | No Comments

The name-map is a feature that most users will not require. But, there are certain use cases where its use can be invaluable. For example: If you have a large volume of class to class transformations, you may notice the … Read More