category
应用程序通信图的目的是描述与元模型实体中应用程序之间通信相关的所有模型和映射。它显示应用程序组件和组件之间的接口。在适当的情况下，接口可以与数据实体相关联。在适当的情况下，应用程序可以与业务服务相关联。通信应该是逻辑的，并且应该只显示与架构相关的中介技术。
提示：使用应用程序组件尽可能多地呈现面向SOA的体系结构。存在不同类型的应用程序组件，允许将它们结构化为层。应用程序组件主要有GUI（交互）、流程和实体。由于遗留系统或外部应用程序，应用程序体系结构可能是混合的。”“应用程序”或“数据库”组件可用于此目的，并且可以与面向SOA的服务组件混合使用。应用程序组件通过所需或提供的服务进行连接，这些服务通过连接器连接。提供/需要的服务由通常在别处建模的IS服务类型化。
应用程序通信图呈现的要么是已经存在的应用程序地图，要么是未来情况的逻辑架构。鼓励使用SOA类型的架构。这种类型的架构基于面向服务的应用程序组件。如果体系结构是混合的，则可以显示（非SOA）应用程序、存储库和新的SOA架构部分的组合。
在面向SOA的体系结构中，建议根据服务应用程序组件的性质和级别对其进行结构化：专用于交互的组件（GUI、WEB）、专用于流程执行的组件以及最稳定的实体组件。
组件通过其所需和提供的服务进行互连，这些服务通过连接器连接。这些必需的和提供的服务由在别处建模的IS服务类型化。这些服务提供的服务操作传输数据（参数），其类型也以“消息”的形式建模。
UML/BPMN EAP Profile
Show/Hide legend
Interaction application component: Represents the top level components that manage the interaction with elements outside the IS. In most cases, this is a GUI component, such as here a web interface.
Entity application component: An entity component is frequently derived from business entities, and is responsible for managing the access to the entity, and its integrity.
Process application component: A process application component is responsible for a business process execution. It orchestrates the tasks of the process.
System federation: A system federation is the coarser-grained application component. It assembles systems to federate them, such as in the example of cooperation between different information systems between different companies.
Utility component: Represents an application component that is frequently reused, and most of the cases bought off the shelf.
Database application component: Represents a repository. In pure SOA architecture, these elements should not appear. However, for legacy analysis or technology architecture, modeling repositories or repository deployment can be useful.
Application: This Application component corresponds to legacy applications, off the shelf products, or can be an assembly of application components.
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.
Connector: Used between provided or required services, and or instances of application components.
Information flow: Defines the flow of any kind of information (business entity, event, product, informal, etc.) between active entities of the enterprise.
Flow link: Flow link between data (e.g. business entity, event, product) and active elements (e.g. business process, service).
External actor: An actor that is external to the enterprise
Consumes link: Expresses that a participant (e.g. actor) consumes an element of the IS (service, operation, application component).
Archimate
架构是分层的：交互组件（site）位于顶部，流程组件位于中间，实体组件位于底部。
本文：http://jiagoushi.pro/node/1241
讨论：请加入知识星球【首席架构师圈】或者小号【jiagoushi_pro】或者QQ群【11107777】