Let\u2019s start at the business level. All components of the business layer are marked blue. At this level, we document all dimensions of a business capability. A process enables a business capability. Role participates in the performance of the process and works with IT assets. IT assets enable a process. IT assets generate reports. A business capability defines the set of business subject areas. A business subject area defines data entities. At this point, the conceptual level begins.<\/p>\n
Conceptual level<\/strong><\/p>\n All components at the conceptual level are colored purple. Constraints link a set of data entities. A data entity is also a component at the logical layer. That is why the shape of the data entity is double-colored.<\/p>\n Logical level<\/strong><\/p>\n Components at the logical layer have a green color. Relationships and business rules link data entities. Data attributes describe data entities. Relationships and business rules also link data attributes.<\/p>\n Physical level<\/strong><\/p>\n The components at the physical level are colored orange. The physical level includes IT assets such as databases and ETL tools. Databases include tables and columns. Software codes perform data transformations.<\/p>\n All components of the metadata model are linked in two directions: vertical and horizontal. In the vertical direction, we link IT assets, for example, systems, applications, and databases. Databases include tables and columns. The tables and columns of a particular database should be linked to the corresponding data entities and attributes. Data entities lead to business subject areas. Such a link is usually called \u201cvertical data lineage.\u201d<\/p>\n In the horizontal direction, at each layer, we link the components of this layer. For example, at the business layer, we connect all IT assets into the data chain to demonstrate how data entities move<\/p>\n from one asset to another. Such linking we call \u201chorizontal data lineage.\u201d We discuss these types of data lineage in detail in the next chapter.<\/p>\n Figure 2: A metamodel of data lineage<\/p><\/div>\n","protected":false},"excerpt":{"rendered":" In this section, we combine and link all data lineage layers and components in a graphical format. Data lineage can be documented at different abstraction levels. We speak about four layers: business and three levels of a data model as shown in Figure 2. Business level Let\u2019s start at the business level. All components of […]<\/p>\n","protected":false},"author":481,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[11],"tags":[],"acf":[],"yoast_head":"\n![\"Irina](\"https:\/\/solutionsreview.com\/expert\/files\/2023\/03\/Figure2-1024x578.png\")