Entity-relationship diagrams

Model student enrolment

1. Create an Entity Relationship model.
2. Add Student, Enrolment and Module entities.
3. Create a relationship from Student to Enrolment and choose |-O< for one to zero-or-many.
4. Create the same cardinality from Module to Enrolment.
5. Record descriptions in custom properties and save the model.

Read both ends

The type is interpreted from From to To. |-| is one at both ends; |-|< is one to one-or-more; |-O| is one to zero-or-one; |-O< is one to zero-or-many; >-< is many-to-many. Reverse the endpoints when the one side belongs at the other end.

Do not infer optionality from the relationship label. Ask the domain owner whether a Student can have no Enrolments, and record the result explicitly.

Attributes and keys

Revelation's native entity boxes do not provide a full database-column compartment editor. Describe fields and keys in custom properties or accompanying documentation. Attribute text is not executable SQL and is not a schema migration.

Use the appropriate relationship

Additional conceptual relationship tokens are available below, but they are not substitutes for an unknown cardinality. Use Group/Parent to organise a model where useful. Supported Mermaid ER input can be imported; review how attribute content is represented after conversion.

Download the student enrolment example (JSON)

Try this with Rovo in Confluence

Choose the matching Revelation agent. Supply the destination page and review the result before sharing. Follow the Rovo guide to attach the created model to a macro.

Create an ER model with Student, Enrolment and Module. A Student has zero or many Enrolments; a Module has zero or many Enrolments. Each Enrolment belongs to one Student and one Module.

Supported element types

Supported relationship types