Page 49 -

10 Enterprise Data Governance

4
Driven Architecture . The feedback and lessons learned to
carry out such a change are missing, even though the
methods and tools are ready to be exploited.

It is indeed a transformation and not simply an addition
of further layers of software to that which are already in
place, which would only complicate the situation. The ability
of the existing systems to take on an extra layer of
complexity is coming to a stage which companies should not
exceed. The risk of overdosing on complexity could lead to
the loss of control of an Information System through its data.

The first step in order to improve the situation without
starting all over again is to regain control of data, without
imposing modifications on in-house software or software
packages already in place. It is all about reference and
master data, i.e. data shared and initialized before use by
transactional systems. This could be, for instance,
configuration of products, structures and organization
descriptions, or financial classifications etc. And this is
where the MDM approach comes in.

The improvement in management of this data, be it
reference or master data, is also necessary in order to meet
new business regulations such as Sarbanes Oxley, Basel II,
Solvency II, etc. These regulations require a very high level
of auditability and traceability in terms of information use.

This reactivation of data modeling comes with the
incorporation of new business requirements and
technological innovations:

– reference and master data governance should not only
be the responsibility of IT. Business users must be allowed to
govern data, in terms of management rights, data entry,
version management, queries, etc.;

4. In the sense of the standard Model Driven Architecture (MDA) of the
Object Management Group (OMG).