Databases Reference
In-Depth Information
12.1. Integration models
The integration of the MDM system with the rest of the
system is described at the time of logical modeling. Business
and organization models must not be impacted by this work.
However, it is necessary to avoid a situation in which models
could not be properly translated at the time of logical
modeling, because of technical constraints.
In particular, the following points need to be considered:
− impact of the functional and technical silo architecture
on the modeling of data approval processes. Certain steps in
these processes can appear under the constraints of silo
boundaries and data synchronization options. For example, a
financial classification is created in a silo and then sent, in a
batch mode, to the MDM system to be referenced and
validated. If the MDM system rejects this classification, it is
then necessary to foresee an organizational step, enabling an
actor to deal with the problem. This step is no longer useful
if the synchronization with the MDM system is carried out in
real time since the validation is done at the time of input;
− reinforcement of the business object states is used to
synchronize the MDM system with the other databases. For
example, a “product” business object, governed in the
repository, is synchronized with the manufacturing system
as soon as its business state changes from “to be configured”
to “configured”.
Consequently, as soon as the MDM approach is started, it
is necessary to decide upon the integration model which is to
be used for the future data repository (see Figure 12.1).
The objective is not to burden the business and
organization modeling with technical preoccupations but to
prepare the way in which their logical derivation will be
carried out. Figure 12.1 shows this decision stage and also
recalls that it is necessary to decide, before starting logical
