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 "Travel" component (V1) uses the earlier "TravelPortfolioManager" application which manages data access), to a situation without this earlier application, where the "Travel" component (V2) uses the new central repository. The use of "migrate" links summarizes which old parts are replaced by which new parts.

enterprise-manageability-diagram
Manageability diagram focused on the "Travel" application component migration issue

entity-componentEntity 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-componentInteraction 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-servicesProvided services: Access points to application components through provided services.

required-servicesRequired services: Required services of application components need to be connected to provided services by other components.

ApplicationApplication: This Application component corresponds to legacy applications, off the shelf products, or can be an assembly of application components.

database-application-componentDatabase 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.

migrate-linkMigration of elements between two versions of the IS: Generally used between business entities, or application components.

information-flowInformation flow: Defines the flow of any kind of information (business entity, event, product, informal, etc.) between active entities of the enterprise.

connectorConnector: Used between provided or required services, and or instances of application components.

Comments   

Petr
+3 # Petr 2012-11-26 09:59
Hello, Iam not a TOGAF expert but I guess that the example diagram on this page is not a good illustration of an enterprise manageability diagram with respect to the definition that it shows "how one or more applications interact with application and technology components that support operational management of a solution".
Reply | Reply with quote | Quote
tkiblawi
+1 # tkiblawi 2013-02-26 12:47
Quoting Petr:
Hello, Iam not a TOGAF expert but I guess that the example diagram on this page is not a good illustration of an enterprise manageability diagram with respect to the definition that it shows "how one or more applications interact with application and technology components that support operational management of a solution".


I think that the above diagram intends to show one aspect of manageability as an example. The example they used for "Application Migration Diagrams" complements the idea they're trying to convey.
Reply | Reply with quote | Quote

Add comment

Leave this empty:


Security code
Refresh

Login

Sign in to use the forum and be informed of the latest news.

Latest comments