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 component: An entity component is frequently derived from business entities, and is responsible for managing the access to the entity, and its integrity.
Interaction 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 component: A process application component is responsible for a business process execution. It orchestrates the tasks of the process.
Database 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.
Persistent entity.
In this model, data is localized either in a repository or in an entity application component
Application component.
Data object.
Comments
TOGAF is fairly generic with data architecture.
See more:
http://wiki.glitchdata.com/index.php?title=TOGAF:_ADM_Data_Architecture
A data flow diagram is an application communication diagram?
Data dissemination is not a data flow diagram?
Data dissemination is about which entities are created and used by which applications?
See example artefacts at http://avancier.co.uk
You can go to the free-to-read web site if you want to know more.
"deployed" business entities to be more accurate, such as ":client", ":order".
The definition of Data Dissemination Diagram is taken from the standard document.
We take the different types of artifacts & diagrams from the TOGAF standard, in particular :
>>> 35.6 Architectural Artifacts by ADM Phase
"Data Flow Diagram" is not mentioned by the TOGAF standard, and I do not see why you introduce this here : it is not the subject, and since there are many definitions and usages of such diagrams, it is hard to see what you are mentioning. May be a proprietary approach?
Anyway, we make the exercise here to stick to the TOGAF standard (complex enough) as much as we can.
In TOGAF, it is called an Application Communication Diagram, the data flows are recorded in the Interface Catalog, and the components are recorded in the Application Catalog.
The purpose of a Data Dissemination Diagram is rather to show the replication and ownership of data entities.
The purpose of the presented diagram here is to show the ownership of data where we see here that "CC" and "Customer" own several types of data.
The "flow" mention in the diagram is very vague, and does not mention specific data flows. The different arrows in this picture recall the dependency context between application component. In a more complete data dissemination diagram, each component will swho its "owned" data.
This is one means to do so. Specialized dependencies is another way to do it.
>>> The purpose of a Data Dissemination Diagram is rather to show the replication and ownership of data entities.
Agreed, that is what it does.
RSS feed for comments to this post