Group items tagged

11. How is ontology different from object-oriented modeling? An ontology is different from object-oriented modeling (represented in UML) in several ways. First, the most profound difference is that the ontology technology is theoretically found on logic. While ontology allows automated reasoning or infer ence, object-oriented modeling does not. Another difference is the treatment of properties; while the ontology technology treats properties as the first-class citizen, the object-oriented modeling does not. That is, while the ontology technology allows inheritance of properties, the object-oriented modeling does not. While the ontology technology allows arbitrary user-defined relationships among classes (a type property), the object-oriented modeling limits the relationship types to the subclass-superclass hierarchical relationship. While the ontology technology allows adding properties to relationships such as symmetry, transitivity, and inversion so that they are used in reasoning, the object-oriented modeling does not. While the ontology technology allows multiple inheritances among classes and also among properties, the object-oriented modeling allows only single inheritances. Despite theses differences, object-oriented modeling and UML are accepted as a practical ontology specification, mostly because of their wide-spread use in industry and the multitude of existing models in UML. There is an on-going effort to add logic capability to object-oriented modeling, represented by OCL (Object Constraint Language).

daviding says: To improve our understanding of the science of service systems, I think that we need to get to the level of ontology vocabulary ... and probably no higher. SysML has features that UML doesn't ... which doesn't mean good or bad, just different.

We introduce the concept of structural analysis of a business enterprise. The practice of enterprise structural analysis amounts to the construction of an enterprise model using business entities defined in an enterprise ontology or enterprise architecture and creating specific views of the enterprise based on relationships among the entities. As we demonstrate through a simple yet illustrative example of a hypothetical coffee shop business, these views can provide many insights and points of analysis. Structural analysis provides an interactive, analytical environment for a user to view an enterprise from multiple perspectives, an approach not unlike On-Line Analytical Processing (OLAP) but for analyzing the qualitative or structural aspects of the enterprise.

daviding says: This article describes business entities, and works concretely through an example with activities, resources and organization in a coffee shop.