Practical systems modeling

A practice with a lineage.

We are simplifying and extending established modeling practices for a guided workshop.

People and traditions behind the work

Entity-relationship modeling, enterprise data modeling, enterprise architecture, and related conceptual-modeling traditions inform this World. The workshop’s notation is simplified; it is not a certification course or an implementation of a formal standard.

The entity-relationship model: toward a unified view of data

MIT Sloan School of Management, working paper 839-76 (1976), Peter P. S. Chen

Credits the entity-relationship modeling tradition. This institutional repository provides Chen’s 1976 working paper.

Source checked 2026-09-21. Linked for attribution and further study; no endorsement is implied.

Insights into enterprise conceptual modeling

Ateret Anaby-Tavor and colleagues; Data & Knowledge Engineering (2010), via IBM Research

Credits enterprise modeling practice and its varied forms in work before formal software requirements.

Source checked 2026-09-21. Linked for attribution and further study; no endorsement is implied.

The Zachman Framework Evolution

John P. Zachman, Zachman International / FEAC Institute

Credits the enterprise architecture tradition associated with John A. Zachman’s 1987 framework and its use of descriptive perspectives.

Source checked 2026-09-21. Linked for attribution and further study; no endorsement is implied.

Ontology Definition Metamodel

Object Management Group

Connects conceptual and enterprise models with knowledge representation and ontology modeling. This World does not implement or teach the standard.

Source checked 2026-09-21. Linked for attribution and further study; no endorsement is implied.

The workshop’s authorship

Renaissance Solutions developed the teaching direction with Mike Besso. Codex assisted with the workshop copy, implementation, and verification. Harbor Coffee, Maple Pantry, their people, quotations, records, and engineer–AI exchange are authored fictional illustrations. They are not customer accounts or live model output.

The lessons use one story to teach the process and reminders to show that it transfers. A new organization still supplies its own purposes, evidence, definitions, and exceptions.

Terms used in this World

Instance: One particular thing, such as Maria or Order #9821.
Type / class: A kind of thing whose instances share relevant meaning, such as Person or Order.
Role: How a person or thing participates in a context, such as Maria acting as a Customer.
Attribute / property: A descriptive fact attached to something, such as an order’s accepted time. It can become a separate thing when identity or history needs to be represented.
Relationship: A named connection between things, such as Person places Order.
Event / transaction: An event is an occurrence, such as Order Placed. A transaction records an agreed unit of activity; its boundary and completion need a definition.
Cardinality: How many instances can participate in a relationship: one, several, or none where the rules allow it.
Conceptual model: A purpose-driven representation of the important concepts and connections. A domain/logical view adds rules and detail; an instantiated view shows particular examples.
Bottleneck: A part of a process whose limited capacity constrains the flow of work. A delay or queue is a clue, not proof of which capacity constraint governs the process.