In this diagram a description of the datapipe from an (webservice) or XML file source to the target datamodel is described. This is based on the transformation of a XML model to an intermediate tabular or relational model and this is then processed in an ETL process to transform the source data model in a number of steps to the required target model.

Description of the data sources in general. Is an aggregation of specific data source types. This generic datasource is added to the model to make associations possible with generic requirements and principles

Data entities saved in a relational (staging) database

Transformation function from the specific source data model to the standardized target data model. This can be a model or a protocol transformation. Often this transformation is divided in sub steps and these sub steps will be analyzed and modeled in the architecture of a specific data pipe implementation and components

Transformation of relational data entities (stored in a relational database) to the standardized data target.

Transformation of an XML stream or file to a relational model

Data target based on a standardized data model. Based on this model and the included data entities one or more interfaces can be implemented for the consumers.

File with a validated XML content that can be processed to a structured model and pessed to an ETL process

Physical model for the description of a technical implementatin model. This is platform specfic and is used for the creation of SQL DDL and ETL scripts and eventually for technical documentation.

Transformation functionality for transforming the data content from a (application) specific datamodel to a generic datamodel based on a standardized datamodel (see the service diagrams). This can be impllemented either in an ETL transform process or in a message handler for example in a service bus.

Workflow management for the scheduling and iteration of transformation tasks

For the transformation of source to target datamodels a description of the data elements has to be modeled.

The logfical or conceptual model is abstract in nature and is therefore independent from the implementation platform. In most cases this model must be readable for non IT stakeholderrs.

Extract functionality for receiving data from the source systems. This has a XML format and the source is either a webservice or a XML file. The data is extracted and prepared to be transformed

Load functionality for transferring the data to a data target and load it there. This can either be an ETL process or the implementation in a message handler