UML Diagrams ontology

UML Diagrams ontologyMihai RomanObjectives The main objective of this project was to design an ontology based on the UML diagrams domain.

The focus was set on implementing an UML Class Diagram ontology

An UML Class Diagram ontology should be able to describe the relationships between classes and interfaces and the members of said classes and interfaces

specifications

The ontology was designed with this simple UML Class diagram in mind

Additionally, an interface and 2 child classes for the customer class where added in order to make the ontology more complexConcepts

RolesSome of the main implemented roles are: extends defines the relationship between a parent and a child class; inverse : hasChildClassimplements defines the relationship between a class and the interface it implementshasMember defines the relationship between a class or interface and their membersvisibility defines the visibility of a class (public, private, internal, protected)Instances In order to check our ontology in a real case scenario we need to implement instances Instances can be seen as the atomic elements of an ontology In this case, instances are the classes, interfaces and members described in the UML diagram above Examples of class instances : customer, order, specialOrder, normalOrder Examples of method instances : sendOrder, receiveOrderRules Rules help us apply constraints on the roles we declared For example a rule for the extends role would imply that: the entities using this role should both be classes the class which extends should have the same members as the classwhich is extended Thus when interrogating the ontology for the members of a child class or a class which implements an interface, it must result in the same members as those in the parent class or in the implemented interface Thank you