Overview of Logical Data
The HOPEX Data Governance and HOPEX Data Architecture solutions each offer a profile dedicated to the definition of logical data: the Data Designer and the Data Architect.
Data Dictionary
A data dictionary collects and holds a set of logical data, and provides them with a namespace.
The data dictionary therefore participates in the organization of data in the HOPEX repository.
See Data Dictionary.
Data Domain Map
A data domain map represents the data domains of a data dictionary and their dependency links.
See Data Domain Map.
Logical Data Domain
A logical data domain represents a restricted data structure dedicated to the description of a software Data Store. It is made of classes and/or data views and can be described in a Data Area Diagram.
For more details, see Data Domains and Logical Data Domains.
To address these specific use cases, you can create Data Views in which you can see and modify the scope covered by the classes.
Logical Data View
From the perimeter of an object in a data dictionary or a data domain, a logical data view allows you to define a set of information for a specific use. See Logical Data View.
Data Model
When you choose to work with the “Data Model” formalism, business dictionaries are represented by data models (not data dictionaries).
For more details on creating and updating a data model, see Data Model.
Example
The data model of the "Purchase Request Automation" project is presented below.
The application manages purchase requests, orders and product stock levels in each of the representation offices.
A centralized catalog of products and suppliers is installed.
Contracts with referenced suppliers are also accessible from the application.