Databases Reference
In-Depth Information
even if simplification and adaptation of certain of these is
necessary.
This is the case with Praxeme applied to an MDM system.
In particular, the design of processes is simplified as it
involves treating reference and master data approval
processes in a less complex way than the processes that act
on transactional data.
However, data modeling fully benefits from the force of
the semantic modeling procedures offered by Praxeme. This
modeling guides the construction of the data model
necessary to the MDM system and favors its reuse at the
time of transactional data modeling. The same business
objects and lifecycles are reused to build the MDM system, to
synchronize it with the rest of the IT system but also to
progressively overhaul the transactions beyond the scope of
the initial MDM system itself.
Consequently, a company must avoid the implementation
of a method that would need to be invented just for the MDM
approach. On the contrary, it is necessary that the method
be based on an enterprise method and be useable across the
scope of MDM requirements.
If the Praxeme method is not used, it is necessary to
verify that the method envisaged to be used answers the
following demands:
-
there is a distinction between business modeling and
modeling of organizational processes. The business modeling
provides the lifecycle of the business objects, from a strictly
business point of view, outside the constraints of the
organization. The business objects and their lifecycles are
not modeled for the sole use of the MDM system. They must
be reused in order to manage the integration of the MDM
system with the rest of the IT system, but also at the time of
the progressive overhaul of the transactional systems. In
