Databases Reference
In-Depth Information
11.2. Data approval processes
The data approval process is modeled in the same way as
any process with a more extended scope than just an MDM
system. We will now illustrate the mechanism of this type of
process with the help of an example that deals with the
modification of a product's tariff.
11.2.1.
Process example
Figure 11.1 is a simplified example of a data approval
process which involves two human actors (sales manager,
product manager) and a system actor (data quality for
product). It is an Activity Diagram in UML; reading it does
not require an in depth knowledge of the UML notation.
Each step of Figure 11.1 corresponds to an MDM use case,
except for “checking price quality” which is carried out by a
data quality tool, located outside the MDM system. This
process is entirely piloted by a workflow, either integrated in
the MDM tool, or outside it. The data flow between two steps
corresponds to the posting of a task into the task list of the
human actor who is the recipient of the flow, or in the queue
of the targeted system.
The sales manager is in charge updating the pricing of
products. He takes on the role of Data Steward
3
; he is
responsible for data updates by product. The tariff
modification is possible only if the state of the “product”
business object allows it. This constraint is visible in the
form of the state “Validated in the reference branch”, which
means that the product must be in the “validated” business
state in the reference branch of the version management.
This branch has the current version of the product
description
4
. The first action led by the sales manager is the
3
. See Chapter 7 for a detailed definition of roles.
4
. See Chapter 6 for a reminder of the principles of version management.
