Databases Reference
In-Depth Information
system uses a decision table that enables the
synchronization to be automated
5
.
This decision table is master data; it is therefore governed
by the MDM system and benefits from use contexts
management and the version management (see Chapter 6).
11.2.3.
The other processes
Beyond data approval, other processes need to be taken
into consideration, in particular the following:
− initial data loading, often coupled with data cleaning
tools before injection into the MDM system;
− management of the lifecycle of the data repository
throughout the technical environments: development, unit
tests, user acceptance tests, training, pre-production,
production, etc.;
− integration of the MDM system with the rest of the
information system.
The modeling procedures for these processes are the same
as those used for data approval. The modeling is carried out
from the pragmatic aspect when they depend on the
organization. In the opposite case, they are dealt with at the
time of logical modeling.
11.3. Use cases
A use case describes the interaction of one actor with the
MDM system over the same timeframe. Unlike processes,
there is no task lists management; the workflow does not
intervene. We will see that an approach via the
5
. For example, for each step of a data approval process, the decision table
provides the list of the forbidden use cases for a direct setting off by user
interface actions or programming services of the MDM system.
