How Ontologies Turn One Model into Three Outputs and Living Documentation

Please register to be a participant

Most documentation describes a system after decisions have been made. By the time it is complete, something has changed. In this session we look at how a single domain model, expressed as an OWL/Turtle ontology, drives three distinct outputs simultaneously: visual UML diagrams, working code, and structured documentation. We trace the path from a natural language requirement to a deployed application and show how keeping the ontology as the canonical source means documentation is not written about the system. It is generated from the same model as the system itself.