Functional Objectives
Distinguishing enterprise definitions and business function data
To ensure consistency of business function data, modelers can refer to enterprise definitions serving as the reference framework.
Data model mapping establishes a distinction between enterprise level definitions and business function data, while assuring traceability. The Dictionary tool supplements this approach, enabling compilation of business function vocabulary structured as a dictionary.
See "Managing Dictionaries in HOPEX", page 257.Integrating existing models
Existing models describing applications assets must be taken into account when creating new models or at the time of a revision project. Requirements vary according to use cases:
• "As-is to-be" type approach: development of a data model is progressive and is based on a stable reference state, which generally corresponds to data of the system in production.
• Software package installation: each software package (PGI, CRM, etc.) imposes its data model, encouraging a trend towards fragmentation and compartmentalization of the IS. Hence the need to have an independent model, linked to the different imposed models.
Mapping of data models is a means of bringing together the data models from different sources.
Use case
A typical case of data mapping occurs in the context of exchanges between applications, each with their own data models. When the number of applications becomes too high, you can install a reference pivot model that will serve as intermediary between the applications and thus avoid multiplication of mappings.