Creating a Logical Model

In this section:

The Logical model is used to set up almost all objects in the MDM Hub, which are generated from metadata descriptions of all entities, relationships, and settings. It consists of several other models describing particular data layers. The Instance Layer is usually used as a canonical interface for all connected systems.

There are different approaches to creating the model and different modeling CASE tools. iWay MDS IDE has CASE capabilities and the Import feature for either Instance or Master Layer model, so it can be easily uploaded into an MDM project from different formats (for example, XMI, Sybase PowerDesigner, and so on).

There are two different modeling approaches:
Top of page
x
Creating a Logical Model Using the Bottom-up Approach

The bottom-up approach defines the MDM Hub canonical model according to the entities and attributes of connected systems. It is easier to map the data between the systems and the Hub. However, mapping from the Instance to Master Layer model can be more complicated.

To create a Logical model using the bottom-up approach:

  1. Understand the models of connected systems and their possible output interfaces.
  2. Define the Instance layer model as a superset of the models of the connected systems.
  3. Define the Master data layer model, based on the Instance layer model.
  4. Validate output interfaces defined by the Master data layer model with consuming systems and connected applications.

Changes might be necessary due to the requirements of consuming systems.

This approach is preferred if the MDM initiative is driven by the connected systems (from the architecture or sponsorship perspective).
Top of page
x
Creating a Logical Model Using the Top-down Approach

The top-down approach is considered a cleaner design from the MDM perspective, as the model is derived from the Master Layer (or the Golden Record) viewing requirements.

To create a Logical model using the Top-down approach:

  1. Create a list of users of the MDM solution. These can consist of systems, applications, business users, and departments.
  2. Understand the needs and goals of those users.
  3. Define the Master Data Layer model to satisfy those needs and meet the goals of the users.
  4. Define the Instance Layer model based on the Master Data Layer model and connected systems output interfaces.

Changes might be necessary, as some needs and goals might be impossible to realize because of the output interfaces of connected systems.

This approach is preferred if the MDM initiative is driven by the future users of the MDM solution (from the architecture or sponsorship perspective).
Top of page
x
Creating a Logical Model in iWay Master Data Server (MDS)

There are several options for setting up a logical model in iWay MDS:

iWay Software