Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Application Lists Diagrams and Matrices
Lists, sometimes referred to as catalogs, provide a simple way of viewing a group of applications. The list can be based on any number of criteria including a list of baseline applications, a list of target applications, or a list based on complex criteria such as the applications owned by a particular stakeholder that were installed before a certain data and that have a lifetime of retirement. The lists can be used simply to view the applications or to add new ones and change existing ones.
Enterprise Architect has a wide range of tools for working with lists of applications and provides ways of constructing lists dynamically, running searches across a selected part or the entire repository, applying filters and sorting mechanisms that can restrict and order a list based on particular criteria. Diagrams can be viewed as a list of elements or even viewed as a Gantt chart. There is also a very flexible Specification Manager that allows any Package to be viewed as a list of elements; this has built-in filtering, and notes and other properties can be edited inline.
The Model Views facility is another way of creating a list of elements in a tree structure similar to the Project Browser, but the elements can be added freely to a favorites Package or generated by a simple or sophisticated search. This is particularly powerful when working with applications and any number of tree based lists can be created.
The Model Search facility is another tool that can create a list of applications or interfaces based on predefined or user created criteria. This facility can function as an analytics tool to answer questions posed about the Application Architecture. For example - find the list of applications that were built in-house that are critical to the business and have a particular owner.
Diagrams are one of the most commonly used mechanism for expressing ideas in the Application Architecture. They can be large format diagrams intended to give a view of an entire landscape of applications and printed onto poster size paper, or smaller diagrams intended for documentation. An application Communication diagram is a typical candidate for a large A0 size diagram where all (or at least the most significant) applications are printed in a single diagram with lines showing how they are wired together, including payloads if required. Equally an application Communication diagram could be created with just a constellation of applications that realize a business service or capability.
Matrices provide an alternative view to diagrams and lists and allow stakeholders to view the relationship between two sets of elements in a familiar spreadsheet like view. The matrix could be between applications and capabilities or applications and business processes or any other elements including between the same set of applications to show connectivity. The matrix profiles can be setup and saved at the time the repository is created and as elements are added the relationships will become visible. If further analysis is required a matrix can also be conveniently exported to a CSV file so it can be opened in a spreadsheet application.