Data dissemination diagrams
The purpose of the data dissemination diagram is to show the relationship between data entities, business services, and application components. The diagram shows how the logical entities are to be physically realized by application components. This allows effective sizing to be carried out and the IT footprint to be refined. Moreover, by assigning business value to data, an indication of the business criticality of application components can be gained. Additionally, the diagram may show data replication and system ownership of the master reference for data. In this instance, it can show two copies and the master-copy relationship between them. This diagram can include services; that is, services encapsulate data and they reside in an application, or services that reside in an application and access data encapsulated within the application.
In this model, data is localized either in a repository or in an entity application component
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.
Interaction application component: Represents the top level components that manage the interaction with elements outside the IS. In most cases, it is a GUI component, such as here a web interface.
Process application component: A process application component is responsible for a business process execution. It orchestrates the tasks of the process.
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.
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.
Application: This application component corresponds to legacy applications, off the shelf products, or can be an assembly of application components.
Business Entity: Describes the semantics of the entities in the business, independently of any IS consideration (e.g. storage, technology, etc).
Data flow: Expresses that data (for example business entity) is input or output from a dynamic entity.