I have been meaning to do some scalability tests on Structure101 for some time now but something always seems to get in the way. Step in the end of the last working day before Christmas. Just fire some code at it, and let’s see what happens! I have a new iMac, 2.7 GHz i5 with 12… Read more »
Structure101 Build (for Java, .Net and more) can be invoked in Hudson/Jenkins via an Ant, Maven or Execute Shell Script build step. In this post I will show example use cases of how to use each build step, and how to make a Hudson/Jenkins build unstable if any architecture violation is found. Thanks to Rochelle… Read more »
@chedgey met up with a couple of JUG leaders at the recent Java One, and between them they bashed out our sponsorship of Java User Groups worldwide. We would be delighted to also extend our offer to the .NET User Group (DNUG) community. If you are interested all you need to do is contact us. Details of our sponsorship are… Read more »
Checking architecture conformance or complexity thresholds at build time is easy to set up with the Structure101 Maven Plugin – this is a step-by-step guide, discussing some options along the way.
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 behind it, but it can be a nightmare if you dare to deviate from how… Read more »
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 this tutorial focuses on the simpler situation.
Today we are very pleased to announce the general availability of Restructure101 version 1.0 for Java and .NET. Restructure101 lets software developers refactor their software architecture to remove costly dependency tangles and structural complexity. We developed an interactive visual model called the Levelized Structure Map (LSM) which was specifically designed to allow software architects delve… Read more »
The purpose of this exercise was to use Restructure101 to solve tangles in JUnit version 4.8.2.
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 into rows, or levels, so that every item depends on at least one item on… Read more »
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 client reaction time becoming slow. To workaround this use the Java name-map, as it can… Read more »