Categories
|
commercial software
Structure101 for v7Products: IntelliJ IDEA, Android Studio Vendor: Headway Software Email: Website: http://www.headwaysoftwa...cts/structure101/plugin/ Buy link: http://www.headwaysoftware.com/store License: http://www.headwaysoftwa...ownloads/eula-plugin.php Description:
The structure101 plug-in for IntelliJIDEA v7 (#6813-onwards) is a free companion
to the structure101 client product. The plug-in lets you influence your software
architecture as it happens – when the code is edited in the IDE. Structure101
architecture diagrams specify layering and composition in a concise format. The
plug-in displays the diagrams within the IDE, any violations to the target
architecture are shown on the diagrams, and the plug-in lets you navigate to the
relevant code. A key feature is that the plug-in can be set to warn only on new
code changes that are inconsistent with the architecture. This way developers
can grow the code-base towards the target architecture without being constantly
swamped with pre-existing violations.
Full documentation URL:
http://www.headwaysoftware.com/help/java/index.html?ideplugin_ideplugin.html
2 updates are hidden
show all updates
Recent change notes:Requires IDEA v7 - Build of at least #6813General usage instructions:The Structure101 for Java IDE Plug-in for IntelliJ is a free companion product for Structure101 for Java, a leading structural analysis and architectural control product from Headway Software. Install this free plugin only after you have used Structure101 to publish a snapshot and block architecture diagrams of your codebase to a Structure101 repository. |
|||||||||||||||||||||
Comments:
Thanks for asking the question Anonymous,
In a lot of cases, especially on smaller projects where the team has a good mental picture of the intended architecture, the IntelliJ dependency rules feature will fit the bill just fine.
However the number of "cannot use" rules will grow exponentially with the number of architectural components. The Structure101 architecture diagrams, with layering and nesting, can define a lot of rules in a highly condensed format (basically items should only depend on items lower in the diagram). And diagrams can make the big picture easier for the team to _understand_ compared to a long list of rules.
Also, any violations to the layering will be overlaid on the architecture diagrams making it easier to _understand_ the state of the architecture. And selecting a violation will show all the class-to-class dependencies that are causing it and you can navigate directly to the relevant code.
Another important aspect to Structure101 is that it can differentiate the architectural violations introduced since a particular point in time. This way you can get warnings (or errors if you choose) on just the new violations you are creating - i.e. you don't need to get swamped by warnings of pre-existing errors. This makes it practical to start architectural control on projects that have "drifted" already.
Finally, the plug-in is part of the overall Structure101 product that lets you define and monitor your architecture in the context of rich structural analysis, visualization, complexity measurement, reporting, trending and such.
There's an overview of how the plug-in fits with the other architectural control features in Structure101 here: http://www.headwaysoftware.com/products/structure101/ControllingArchitecturewithStructure101.pdf.
And an overview of the whole product (15 mins with audio) is here:
http://www.headwaysoftware.com/products/structure101/demos/structure101overview_viewlet_swf.html
To the author: does this plugin provides more that just dependency checking? Because if not, I don't see any reason to spend additional money on it.
To the author: does this plugin provides more that just dependency checking? Because if not, I don't see any reason to spend additional money on it.