Databases Reference
In-Depth Information
orientated model (top), i.e. capable of managing behavioral
facets, data validation rules, and the lifecycles of business
objects (decision table).
Rich data model
(Semantic)
Model-driven MDM
Semantic approach associated with a Model-driven
software development = data governance functions
automatically aligned with data models
=> OPEN FOR BUSINESS USERS
Object Oriented Database
Semantic approach based on a classic
software development
=> NOT OPEN FOR BUSINESS USERS
Software development lifecycle
CLASSIC
MODEL-DRIVEN
PIM- PLM
Weak data governance
across the whole
of the IS
CDI
Lack of real
data governance
Model-Driven Architecture (MDA)
Software development based on models
=> FOR IT SPECIALISTS
OLT P
(On-Line Transaction Processing)
Figure 12.8.
The classification of databases
and development techniques
From these two axes appear four classification zones:
− On-Line Transaction Processing (OLTP) and classic
development lifecycle (bottom left quadrant). We find here
databases and application software systems developed over
the last thirty years. MDM solutions, in this sector, behave
like transactional application software, evolving little and
not particularly open to data governance by business users.
The data model is not very expressive, which means bespoke
and hard-coded developments software for the management
of the lifecycles of business objects and data validation rules.
Repositories such as Customer Data Integration (CDI),
Product Information Management (PIM) and Product
Lifecycle Management (PLM) are situated in this quadrant;
