Define
Structure101 bridges the gap between the way your code-base is structured and how it should be structured, and helps your team evolve the code in line with the intended architecture.
The Structure101 graphical notation for software architecture diagrams uses an arrangement of cells to convey a number of architectural rules in a highly condensed format:
Composition is indicated by one or more cells being contained within a parent cell. Layering is indicated by the top-down arrangement of cells. Cells should only be used by cells in higher layers (unless specifically allowed or disallowed by a layering override, e.g. the green arrow in the example).
Mapping of each cell in the architecture diagram to physical items in the code-base is specified by 0, 1 or more wildcard expressions.
Violations of the layering, i.e. dependencies in the mapped physical code-base that break the specified layering, are shown on the diagram (conformant dependencies are not shown).
Visibility - whether cells are visible outside of their immediate scope.
You can define and edit architectural diagrams with Structure101. By publishing diagrams to a Structure101 repository, they can be immediately communicated to the team via the Structure101 web application and/or IDE plug-in components. Additionally, the programming team can recieve immediate warnings if they create any new architecture violations.
"I love the new architecture diagram functionality. With it we are able to define our architecture standards and enforce them during design and construction. As a Chief Architect who is responsible for overall design and system architecture, this capability is a great value-added to an already fantastic product."
Joong Lee, Chief Architect, EPL.