Data Model documentation options

Mikes Notes

Pipi has hundreds of autonomous databases, some with up to 60 tables. The existing Pipi entity engine stores every model, entity, relationship, and column Pipi uses. Developers need a web-based data model explorer to understand the databases they are using. The problem is how to design the user interface. This note examines how other modelling tools present information to develop something familiar and useful for Pipi.

Thanks, Alex, for sending me a list of more potential tools.

The experimental toy prototypes are here. (The web URLs will likely change in the future)

Resources

Requirements

A data model explorer needs to auto-generate documentation.

These objects are a minimum.
  • Database
  • Schema
  • E/R Diagram
  • Data Type
  • Table
  • Column
  • Data Domain
  • Relationship
  • Primary Keys (PK)
  • Foreign Keys (FK)
  • Indexes
And be able to provide these model views
  • Conceptual
  • Logical
  • Physical
Other
  • Data Dictionary including i18n
Linked data
The model objects need to automatically link to other documentation
  • DAO (Data Access Objects)
  • Ontologies
  • Use in workflows
  • Variables
  • "JavaDocs" style code packages
  • i18n object names

Examples

Database Workbench

DBeaver

dbDiagram

dbSchema



Drawio


DrawSQL



Enterprise Architect


ERDPlus


E/R Studio Data Architect

erwin Data Modeller


MS SQL Server Management Studio

MetaBase


Model Right

Navicat

QuickDBD

Software Ideas Modeller


SQLFlow

SQuirreL

SQLyog


Vertabelo Data Modeller




No comments:

Post a Comment