Enterprise manageability diagrams
The enterprise manageability diagram shows how one or more applications interact with application and technology components that support operational management of a solution. This diagram is really a filter on the application communication diagram, specifically for enterprise management class software. Analysis can reveal duplication and gaps, and opportunities in the IT service management operation of an organization. It would identify temporary applications, staging areas, and the infrastructure required to support migrations (for example, parallel run environments, etc).
In this example, an enterprise manageability diagram shows how a part of the system will evolve to progressively pass from a hybrid situation (where "Trip" component (T1) uses the earlier "TripPortfolioManager" application which manages data access), to a situation without this earlier application, where the "Trip" component (T2) uses the new central repository. The use of "migrate" links summarizes which old parts are replaced by which new parts.
Entity application component: An entity component is frequently derived from business entities, and has the responsibility of managing the access to the entity, and its integrity.
Interaction application component: Represents the top level components that manage the interaction with the external of the IS. In most cases, it is a GUI component, such as here a web interface.
Provided services: Access points to application components through provided services.
Required services: Required services of application components need to be connected to provided services by other components.
Application: This Application component corresponds to legacy applications, off the shelf products, or can be an assembly of application components.
Database application component: Represents a repository. In a pure SOA architecture, these element should not appear. But for legacy analysis, or technology architecture modeling repository or repository deployment is useful.
Migration of elements between two versions of the IS: Generally used between business entities, or application components.
Information flow: Defines the flow of any kind of information (business entity, event, product, informal, etc.) between active entities of the enterprise.
Connector: Used between provided or required services, and or instances of application components.
Manageability diagram focused on the "Trip" application component migration issue.