Almost ready for v1

Cleanup continues.

Author: RoelantVos

400_Integration_Layer/Data Integration Framework - Integration Layer.docx

@@ -44,13 +44,13 @@ The Data Integration provides a structured approach to data integration design f
 
 To adapt to business needs the intended data solution should decouple ‘warehouse logic’ from ‘business logic’. The basic assumption is that requirements will change over time, and that any solution that specifically is designed for a certain output or requirement will fail over time when adjustments are made. Rather, the framework views requirements from a data perspective and aims to properly integrate and consolidate data before applying a certain view.
 
-![1547519184139](..\9000_Images\1547519184139.png)
+![1547519184139](.\Images\1547519184139.png)
 
 # Data Integration Framework components
 
 The diagram below outlines the components that are required to support a data solution and enable automation. The intent is to enable a standard and structured way for documenting decisions made related to system design and intended operation.
 
- ![1547519339316](..\9000_Images\5C1547519339316.png)
+ ![1547519339316](.\Images\5C1547519339316.png)
 
 
 
@@ -77,7 +77,7 @@ The diagram below outlines the components that are required to support a data so
 
 The Data Integration consists of the following documents:
 
- ![1547519517248](..\9000_Images\5C1547519517248.png)
+ ![1547519517248](.\Images\5C1547519517248.png)
 
 A full overview is provided below:
 
@@ -117,7 +117,7 @@ In this example the Design Pattern would refer to the ‘AGA Data Integration -
 
 The Data Integration should be viewed as one part of the larger (enterprise) architecture. The purpose is to specify how the ETL and the data model can be configured for an optimal Enterprise Data Warehouse implementation. This is a detailed (albeit significant) component in the Data Warehouse architecture which in itself includes other components such as system landscape, subject areas and the Business Intelligence and Data domain. 
 
-![1547519790297](..\9000_Images\5C1547519790297.png)   
+![1547519790297](.\Images\5C1547519790297.png)   
 
 ## Using the Data Integration
 
@@ -139,4 +139,4 @@ In principle every project that contributes to the common integrated data model
 
 In this approach it is highly recommended to limit the scope to a short-term iteration; ideally bringing the cycle down to 2-3 weeks.
 
-![1547519869758](..\9000_Images\5C1547519869758.png)
+![1547519869758](.\Images\5C1547519869758.png)

400_Integration_Layer/Data Integration Framework - Integration Layer.md

@@ -83,7 +83,7 @@ This chapter describes the detail overview of the reference architecture.
 
 The high level reference architecture is as follows:
 
-![1547521419126](..\9000_Images\HighLevelSolutionOverview.png)
+![1547521419126](.\Images\HighLevelSolutionOverview.png)
 
 In this overview the basic flow of data as specified in the Reference Architecture is:
 
@@ -106,7 +106,7 @@ The following diagram is a bottom-up overview of the detailed steps taken and ch
 
 Each layer contains two (2) separate ‘areas’. These areas cover specific ETL functionality that support the overall purpose of the layer of which they are part of. Each area inherits the data modelling approach of the parent layer. 
 
-![1547521501883](..\9000_Images\LayersAndAreas.png)
+![1547521501883](.\Images\LayersAndAreas.png)
 
 In this diagram Error/Exception handling and Operational Metadata are positioned as applicable for every process in the architecture. The left column of areas in the diagram specifies the mandatory areas (Staging, Integration and Reporting Structure).  
 
@@ -280,7 +280,7 @@ Every Data Warehouse table contains a predefined set of metadata attributes, whi
 
 Error handling and exception is applicable to every layer and area in the architecture. Each individual layer definition document will describe how error handling is used for that particular section of the architecture since the exception handling is very different between layers. The error handling and recycling document itself lists and explains the concepts that can be used and will provide an overview of the complete error and exception handling solution.
 
- ![1547521779997](..\9000_Images\79997.png)
+ ![1547521779997](.\Images\79997.png)
 
 The details for error and exception handling are defined in the ETL Framework - 7 - Exception Handling v1.0’ document.
 
@@ -291,7 +291,7 @@ Similar to exception and error handling concepts the Metadata Model links in wit
 
 The Metadata Model document itself will list and explain the available concepts and will provide an overview of the complete framework. 
 
-![1547521843164](..\9000_Images\64.png)
+![1547521843164](.\Images\64.png)
 
 In general the metadata process model supports the ability to trace back what data has been loaded, when and in what way for every interface. A single attribute in any place in the architecture should be auditable back to the originating source system.