Organization Modeling - Enterprise Data Governance - page 231

documentation of the use cases is sufficient: it is not
necessary to carry out a formal modeling such as that
practiced for transactional systems. At the same time, we
will distinguish the use cases that are carried out by default
through the MDM (elementary use case) and those that
require a bespoke development (extended use case).
11.3.1. Documentation of use cases
For the MDM system, modeling of a use case is
exceptional as they follow, most of the time, a simple
interaction model such as: screen display, data input, and
data validation. In other words, we are dealing with CRUD
type interactions to manage the Creation, the Reading, the
Update and the Deletion of business objects. With the
exception of read use cases, the others generally work on the
scope of a single business object, with a transaction
management which is limited to it.
For example, the MDM system has “modify product” and
“modify factory” use cases that are each executed following a
simple interaction, that of display, data input and data
validation. It is rare to dispose of a use case capable of
proceeding at the same time to the modification of products
and factories in a same transaction. In this case, the system
is further away from its reference and master data vocation
to achieve a transactional application. It would then be
necessary to specify the synchronization rules between the
product modifications and factory modifications, as well as
screens and interaction steps enabling the user to
successfully achieve the transaction.
Consequently, rather than modeling, it is more convenient
to document the use cases in the following manner:
− name, in a verbal form;
− type: create, read, update, delete;