Data Modelling with Enterprise Architect

Conceptual information and data modelling

Data modelling is an important skill for using data in a targeted manner to achieve business success.

Goal

Prerequisite: You are familiar with the basic structure of Enterprise Architect and know how to use it to create, modify and reuse models, create views, track information and delete it again..

Part 1: You are familiar with the most important UML models, can read them and create them with Enterprise Architect. You have a basic understanding of how the UML language can be used for the conceptual modelling of software systems. In addition, you are aware of the advantages of a modelling approach and know the most important tips and tricks for creating UML models.

Distribution of training content: Both training courses focus on UML (50% of course time), with 30% dedicated to the use of Enterprise Architect. Each of our courses also teaches a methodology (15%), and around 5% is planned for best practices.

Data modelling languages

There are different languages for data modelling, the best known being the UML class diagram and the entity relationship diagram.

Logical data models

  • UML class model: classes as containers for data
  • UML attributes: as data
  • UML association: as relationships between data containers
  • UML generalisation: for abstraction and simplification of data structures
  • Enterprise Architect models: as an alternative to UML class diagrams
  • Differences and similarities between UML and Enterprise Architectt

Physical data models

  • The table
  • The table column
  • Special constraints on table columns
  • The foreign key relationship

Enterprise Architect

  • The MDA approach:
    • Model transformations from UML CD to physical data models
    • Model transformations from ER to physical data models
    • Model transformations from physical data models to ER
  • Generating DDL scripts
  • Importing existing databases via ODBC connection
  • Working with the Database Builder tool in Enterprise Architect
    • Forward generation of databases
    • Importing databases
    • Synchronising the model and live database