ERIL can be seen as a set of guidelines aimed at improving the readability of structure diagrams. These guidelines were borrowed from DRAKON, a variant of flowcharts created within the Russian space program. ERIL itself was developed by Stepan Mitkin. The ERIL guidelines for drawing diagrams:
Lines must be straight, either strictly vertical or horizontal.
Vertical lines mean ownership.
Horizontal lines mean peer relationships.
Line intersections are not allowed.
It is not recommended to fit the whole data model on a single diagram. Draw many simple diagrams instead.
The same class can appear several times on the same diagram.
Use the following standard symbols to indicate the type of the relationship.
Do not lump together inheritance and data relationships.
Indexes
A class in ERIL can have several indexes. Each index in ERIL can include one or more fields, similar to indexes in relational databases. ERIL indexes are logical. They can optionally be implemented by real data structures.
Links
Links between classes in ERIL are implemented by the so-called "link" fields. Link fields can be of different types according to the link type:
reference;
collection of references.
Example: there is a one-to-many link between Documents and Lines. One Document can have many Lines. Then the Document.Lines field is a collection of references to the lines that belong to the document. Line.Document is a reference to the document that contains the line. Link fields are also logical. They may or may not be implemented physically in the system.
Usage
ERIL is supposed to model any kind of data regardless of the storage. The same ERIL diagram can represent data stored in a relational database, in a NoSQL database, XML file or in the memory. ERIL diagrams serve two purposes. The primary purpose is to explain the data structure of an existing or future system or component. The secondary purpose is to automatically generate source code from the model. Code that can be generated includes specialized collection classes, hash and comparison functions, data retrieval and modification procedures, SQL data-definitioncode, etc. Code generated from ERIL diagrams can ensure referential and uniqueness data integrity. Serialization code of different kinds can also be automatically generated. In some ways ERIL can be compared to object-relational mapping frameworks.
