HOPEX Information Architecture > Data Architecture > The data model
The data model
 
Data Modeling Principles
Summary of Concepts
Building a data model
Creating a Data Model
Creating a Data Diagram
Entities
Creating an entity
Attributes
Associations
Creating an Association
Defining association roles (ends)
Multiplicities
Other association characteristics
Using reflexive associations
Displaying an N-ary Association
Constraints
Normalization Rules
First Normal Form
Second Normal Form
Third Normal Form
Generalizations
What is a generalization?
Multiple sub-entities
Multiple inheritance
Creating a generalization
Discriminator
Identifiers
Defining an Entity Identifier
Data Model Mapping
Functional Objectives
Running the mapping editor
Creating a Mapping
Deleting a mapping
Mapping details
Example of mapping between data models
To help you describe logical data, HOPEX Information Architecture offers a simple notation to represent all current cases based on the data model.
A data model is used to represent the static structure of a system, particularly the types of objects handled in the system, their internal structure, and the relationships between them.
At the physical layer of HOPEX Information Architecture, data models can be mapped with physical models.
Specific notations are also available:
*The UML notation: "The Class Diagram", page 9