Intuitive EA modelling experience

Visualizing complexity

The whole architecture graph or any segment can be shown on self-explanatory diagrams. Through our data-driven approach, every screen generated by SAMU is based actual data from its repository. Queries deliver data for the report, while the visualization rules will determine how the components will appear (i.e. The symbol used for a certain object type, layout, level of detail).

By setting up user-defined displaying rules, analyzing the architecture can be made simple. For instance, you can highlight areas based on certain attributes (i.e. Show all data flows on an application communications diagram, which transfer personal data).

Modelling

Visuals are not just read-only and static, as users can update and model the architecture graph on the diagrams. You can build up your models using the drag & drop of symbols to the canvas, just like in Visio. However, in SAMU, all of these actions are database transactions – new components are new records, lines are associations between records, and as needed, you are able reuse components that already exist in the repository.
As soon as you update anything, it becomes shared and visible to everyone with the proper access rights.

Modelling projects

Most importantly, SAMU is an ideal platform for the enterprise to model and plan the upcoming transformation initiatives in a collaborative and agile manner. It will not only show the current as-is state, but also each and every future to-be planned changes to the architecture. If this is done practically, it will become a knowledge base and the most up-to-date architecture information source of truth in your organization.

Understanding the risks and the impact of changes

SAMU contains the entire architecture graph, thus the potential impacts of upcoming changes can be evaluated much more quickly and easily. Just pick any component and see how applying modifications on it can affect other components across the organization.

Similarly, in case an incident happens (and unfortunately, they do), reports in SAMU can help you identify the potential causes of the issue within seconds.

ngEvaluating portfolios

Portfolios of architecture (i.e. Business Capabilities, Application Portfolios, Service Catalogs, Asset Inventories, etc.) can be analyzed and evaluated from many perspectives in SAMU. For instance, survey and classify the business application portfolio, according to its strategic importance, cost and other attributes. Based on these findings, transformation and strategic initiatives can be launched to save resources and gain efficiencies.

Automation

Yes, we use automation where possible to maintain data quality, but our focus is to get the users interested in collaborating and shaping the future together. Nevertheless, SAMU is able to integrate with basically any other tools via web service API (SOAP, REST) and/or automatic data synchronizations.