Data Management Project Sjabloon | ViewPoints | Conceptual model viewpoints | Data object |

Data object

Data object is an ArchiMate concept that on the one hand can be linked to a number of ArchiMate concepts so that aspects such as quality, requirements. But also where is the dataset used and by whom, which application has a relation with this dataset etc. If necessary, you could link to the infrastructure from the data object. At this moment, this is not yet chosen in this example. As soon as there is a need in the community for this, this will be worked out further

Package Conceptual model viewpoints
Auteur Bert Dingemans
Alias
Stereotypes DataObject

Diagrammen

Primary data quality viewpoint

This viewpoint connects three archimate concepts. These are the information entities and a requirement that is subdivided into a number of data qualities. In the example, the DAMA data quality list is used. Within the associations, a score is given to the data within the entities (business object and data object). Keep in mind that this score can be an ist but also a soll or desired score. This can be further elaborated in the matrix by including a double score. In this viewpoint an example of the matrix is included including the example qualities of DaMa
Diagram in repository

Primary data ownership viewpoint

This viewpoint describes which concepts are used for modeling data ownership. Data ownership and stewardship are important aspects of after-management. In the viewpoint, use is made of four ArchiMate concepts, three on the business layer and one on the application layer. It is important that for the ownership a number of associations have been extended on the basis of a RACI classification. These can be displayed in a RACI matrix.
Diagram in repository

Primary data usage viewpoint

This viewpoint indicates which business and data objects are used by which users and perhaps even more importantly in which way. This is done by giving the associations between the user and the data objects a CRUD score. This can of course also be displayed in a matrix view
Diagram in repository

Secundary data usage viewpoint

This secondary viewpoint describes which data and business objects are used within which processes and functions. This can easily be extended with, for example, the application where the data is used. However, this will usually not be within the scope of a data architect and should be cooperated with other architecture disciplines.
Diagram in repository

Primary conceptual datamodel viewpoint

The primary conceptual model consists of two ArchiMate concepts from the passive structure part. Namely data objects and business objects. Often one of these two entities is used in the models. This depends on the further modeling, finds this place on application level then you can use the data objects, otherwise the business objects For both entities you can use specialization and aggregation as an association. In addition, a data object realizes a business object. If desired, you can show cardinalities at the associations, but that is not common. In addition, in a complex model or in many synonyms and homonyms, the modeling of two layers of abstraction can have added value
Diagram in repository

Secundary conceptual model viewpoint

In the secondary conceptual model it is modeled where, how and by which business or application entities these information entities are used or more precisely which entities have access to the information entities. For this, use is made of the behavioral tendencies in the application and the business layer of ArchiMate depending on the modeling level. Optionally, you can extend the model even further with active structure elements, however the question is whether this is the domain of the data modeller. For the link between the information entities and the behavioral entities, the access association (access) is used. Please note that this association can go two ways (or both).
Diagram in repository

Secundary trace viewpoint

This is an extension of the primary viewpoint which describes a link between the layers. This trace viewpoint is relevant in the situation where the model is used to generate program code based on classes and tables. In that situation you would like to have lookups and a trace between the logical and physical data modeling.
Diagram in repository

Primary Logical data model viewpoint Conceptueel - Logisch

In this viewpoint we see the relationship of the logical model with the conceptual model. An association is therefore made between two modeling languages and that is a specific extension for IDEA and is not part of both standards. Within EA there are three standard association types for modeling between modeling languages. Within IDEA we opt for the trace association for an association between the three modeling layers.
Diagram in repository

Gekoppelde elementen

Conceptual model viewpoints

Data Management viewpoints

Logical data model viewpoints

Links 2 Tags

Archimate Architect Architectuur Architectuur document Architectuur repository Ario Azure Big data Bouwblokken en patronen Bpmn Criteria Custodian Data Data architectuur Data governance Data kwaliteit Data management Data modelleren Database Datamodelleren Document Enterprise architect Enterprise architectuur Idea Image library Instruction Intervisie Logisch applicatie model Master data Matrix Mdg Metadata Metafoor Metamodel Modelleren Open source Principes Register Releasemanager Repository Simulator Software Sparx enterprise architect Sql Stakeholders Stappenplan Time aware modelleren Tips en tricks Training Videokanaal Viewpoint Webvideo Werkproces Whitepaper Wpp