Legacy Data Models in UML etc. can be Recycled into Graph Data Models
I tried to get an overview of the data modeling tools market (see addendum below) and I found a list of 77 ERD-supporting tools and a list of 49 UML tools, many of which are also used for data modeling. The history of these tools go back to the mid 80es with the CASE tools (see also below) based on the emerging IBM PC/AT computers. There must be hundreds of thousands of good, reusable data models! Why waste such a large resource of business metadata?
New edition: Now also supports UML 2.0 Eclipse UML tools!
Much similar to data science we need to be able to (in "Metadata Science") to read, transform, scope / reduce / enhance and adapt to modern database technologies. Not least graph databases, if you ask me.
This book contains all you need to do this for the legacy data models - scripts, models and flows.
Why waste time on remodeling the same data again, because you change platform? Explore how to auto-generate graph data models (for Neo4j) from legacy data models in UML, XML, ERD, concept maps and other formats. And it includes a design of a metadata repository giving you full scale control.
Below you see thumbnails for the 6 different contexts supported so far:
- A Concept Map (CmapTools, CXL/XML format)
- An OASIS OData CSDL Definition XML-file
- A XML Schema
- A StarUML Class Model in XPD-format
- An Eclipse PapyrusUML Class Model in a XMI-file
- A UML Class Model in SparxSystems’ EA Tool in a XMI-file
Contents of the Book
- Resided in Oracle®
- Were modeled as UML® class diagrams, and
- Were also available in JSON-format.
To make the story short: We built (mostly we generated) a graph model by way of extracting metadata, mostly from an XMI®-representation of the UML® model, but also from some JSON meta files. We only used Cypher®-scripts and it was a whole lot easier than we thought it would be. This saved us a lot of time and gave us good opportunities for caring about the scope of the forthcoming graph data model.
This book explains how to do that. Cypher®-scripts are included for Concept Maps (CmapTools®), CSDL, XML Schemas, StarUML v1 and UML® via XMI®. More to follow.
It also explains how to build a simple graph-based metadata repository for:
- Business level concept models
- Solution level logical data models, and
- Physical models.
Cypher-scripts for repository handling are indeed also part of the book (under a MIT license)..
We suggest a choice of two approaches:
- Fast Track Data Models (agile)
- Super Data Models (crafted, using the repository)
Short recap of the evolution of data modeling tools:
CASE tools on wikipedia: https://en.wikipedia.org/wiki/Computer-aided_software_engineering. With the advent of the IBM PC/AT, a first wave of tools came about: Excelerator from Index Technology, Knowledgeware, Texas Instrument's CA Gen and Andersen Consulting's FOUNDATION toolset (DESIGN/1, INSTALL/1, FCP). Many of the leaders of the CASE market of the early 1990s ended up being purchased by Computer Associates, including IEW, IEF, ADW, Cayenne, and Learmonth & Burchett Management Systems (LBMS).
Database Star (https://www.databasestar.com/data-modeling-tools/) lists 77 data modeling tools supporting ERD diagrams! Some of them also support UML. First pure data modeling tool was PowerDesigner (1989) from Sybase (according to wikipedia).
What about UML tools, then? They are also used for data modeling. Wikipedia lists (https://en.wikipedia.org/wiki/List_of_Unified_Modeling_Language_tools) 49 UML tools. According to that list, the first one was, once again, PowerDesigner (1989) from Sybase.
Actually PowerDesigner started out as AMC*Designor in 1989 from a French company called SDP (cf. https://www.powerdesigner.biz/EN/powerdesigner/powerdesigner-history.html). The following year the English version S-Designor came out, and in 1995 they got bought by PowerSoft and the name changed to PowerDesigner. 2 years later Sybase bought the company.