Databases Reference
In-Depth Information
these operations are not modeled as we have just indicated,
using state machines and decision tables, then the MDM
system will not be able to ensure, in an autonomous way, the
integrity of the data that it claims to administer. In that
case, provision for bespoke hard-coded software development
has to be made, in order to implement the rules which
manipulate the states. The risk of this situation is that it
might lead to the paralysis of the MDM system, giving rise to
a new and opaque application silo which is to be avoided at
all costs.
Finally, extended business operations are put into the
class of the business object in the following way:
-
an operation “update()” for the operation of the pre-
condition of the modification. This operation utilizes the
decision table which makes it possible to individually modify
the data and the state of the business object;
-
an operation “checkState()” for the control of the
changing of the state values. This operation utilizes the
decision table which makes it possible to change the state
values;
-
each operation which appears upon a transition of the
state machine is declared in the class of the business object.
9.3.2.
Elementary business operation
A business operation is “elementary” when its execution
does not depend on the business states of the objects. They
are described independently of the business states. They
don't appear in the state machines; they cannot interact with
the states and do not have decision tables.
Each elementary business operation is inscribed in the
class of its business object with an indication of its execution
mode (trigger): before update, after update, after deletion,
