Page 104 -

Taking Software Packages into Account 65

Software vendors do not always perceive this necessary
evolution of their offers in a positive manner. Indeed, when
the transformation strategy is carried out under the terms
we are explaining, then the software package imprint on the
IT system is reduced, in favor of a new independence
achieved with the help of repositories.

Consequently, market pressure is needed so that software
vendors take into account the new requirements that we
have described. This is already the case in the business
process management field: it is usual that software packages
are capable of situating business processes in BPM solutions,
outside of their scope.

This must also be the case with MDM, and the BRMS.

3.4. MDM is also a software package

The objective of independence for software packages has
been identified by companies, especially after the sometimes
painful experiences of a first wave of computerization, not
only for ERP, CRM but also PIM and CDI .
2

The reconquering of the independence approach vis-à-vis
software packages, thanks to the repository-based approach,
knows no alternative. It would not be reasonable, however,
for a company to launch into the development of a specific
MDM software solution. The technological and business
barriers are too strong, especially when delivering
administration functions such as version management,
enrichment of data by context, traceability functions, user
interfaces which are secure and sufficiently friendly for
business users, etc.

A company must acquire, on the market, an MDM
software solution which offers all the administration

2. See Chapter 1 for the positioning of PIM and CDI.