Overview of Innovator for Database Architects

DB Reverse Engineering and DDL Generation

Existing databases are linked using reverse engineering. This is normally for both documenting database schema and integrating these databases into new projects. Innovator for Database Architects either directly reads the database using JDBC access for this or creates DB models from DDL scripts.

Based on the database schema, Innovator for Database Architects generates DDL scripts, either CreateTable scripts for new creations or AlterTable scripts for modifying existing databases. This means that all company features or project-specific features can be taken into consideration.

Mapping Between the Database Schema and Conceptual Model Content

Database schema and conceptual schema are integrated with each other in Innovator for Database Architects. Changes to the database schema are adopted in the conceptual schema. This is a basic requirement for real IT projects as manual maintenance of data models is time-consuming and it is easy to make mistakes. e.g. conceptual models are created for integrating existing undocumented databases.

Vice versa, the database schema can also be created from or compared with the conceptual schema.

Database Schema

Innovator for Database Architects supports all current relational database systems. Support for all relational databases can also be configured.

Tables, columns, views, primary keys, foreign keys, indexes, triggers, stored procedures and access rights are supported in database schemata. As well as semantic data types, direct data types are available from the target systems for typing.

The ISO standard, IDEF1X, is used when visualizing database schema; edges represent foreign keys.

You can change the size and compartments shown for database tables, e.g. for table columns and foreign keys. Compartment entries can be hidden and automatically maintained.

Functions, such as combining and splitting database tables (split columns, split rows), also support modeling in the database schema.

Conceptual Schema

The conceptual schema describes the technical requirements of the user independent of the implementation. Entity and relationship types are defined and graphically displayed in the model. Entity relationship modeling (ERM) has been established as the standard method for semantic data modeling.

Innovator for Database Architects provides different options for ER model notation: depending on which diagrams the user is already familiar with, they can use the classic Chen notation, James Martin (“crow’s foot�), SERM, DSA or IDEF1X notation or a notation based on UML class diagrams.

Mapping OO-ER for Integration with UML Models

Innovator for Database Architects enables connection of UML2 models from Innovator for Business Analysts or Innovator for Software Architects using OO-ER mapping. The mapping maps object-oriented modeling concepts to relational databases’ concepts. This works in both directions. Object-oriented analysis models are often taken in UML as the starting point for a conceptual database schema. e.g. a UML model with the requirements analysis’ result is taken from Innovator for Business Analysts using OO-ER mapping and converted into an initial conceptual schema. Traceability links are set. These allow modifications in the analysis model to be transferred into the conceptual schema at a later date. In the other direction, classes can be generated from entities; this facilitates development against the relevant database. Trace links can also be used here to ensure consistency between models.