UML as a Data Modeling Notation, Part 1 UML as a Data Modeling Notation, Part 3 UML as a Data Modeling Notation, Part 4 The series of articles is in three parts. Part 1, set the stage, describing the ...

For effective data modeling, widely used notations include Entity-Relationship Diagrams (ERD) and Unified Modeling Language (UML) class diagrams.

The class and object diagrams are so detailed, describing elements such as interfaces and attributes, that translating UML notation into actual programming code is a virtual no-brainer.

A Unified Modeling Language (UML) use case diagram is a visual tool that provides a way for developers to come to a common understanding with system's end users and domain experts. The behavior of a ...

Is your feature request related to a problem? Please describe. Barker's Notation is a way of arranging an entity relationship diagram such that: there are no diagonal relationship lines no overlapp ...

At the ends of connectors in Entitiy Relationship diagrams, numeric cardinalities should be supported. While the crow feet notation is great, there are cases where more specific cardinalities are ...

We propose combining these two diagrams in a unified view of data pre-processing and data exploration. Heeding such motivation, we present a hybrid diagram called FLOWER (FLOW+ER) that combines modern ...

This article, Part 3 of a three-part series, discusses the aesthetics of preparing and presenting data models – no matter what notation is used.

On the other hand, Z is a formal language, which is non-executable, but, a strongly typed specification language. We here propose a structured-expandable format of a use case, which is expressed in Z ...