Object-Role Modeling

2018 ◽  
pp. 2540-2546
Author(s):  
Terry Halpin
Author(s):  
Rusul Yousif Alsalhee ◽  
Abdulhussein Mohsin Abdullah

<p>The Holy Quran, due to it is full of many inspiring stories and multiple lessons that need to understand it requires additional attention when it comes to searching issues and information retrieval. Many works were carried out in the Holy Quran field, but some of these dealt with a part of the Quran or covered it in general, and some of them did not support semantic research techniques and the possibility of understanding the Quranic knowledge by the people and computers. As for others, techniques of data analysis, processing, and ontology were adopted, which led to directed these to linguistic aspects more than semantic. Another weakness in the previous works, they have adopted the method manually entering ontology, which is costly and time-consuming. In this paper, we constructed the ontology of Quranic stories. This ontology depended in its construction on the MappingMaster domain-specific language (MappingMaster DSL)technology, through which concepts and individuals can be created and linked automatically to the ontology from Excel sheets. The conceptual structure was built using the object role modeling (ORM) modeling language. SPARQL query language used to test and evaluate the propsed ontology by asking many competency questions and as a result, the ontology answered all these questions well.</p>


Author(s):  
Dave Cuyler ◽  
Terry Halpin

For conceptual information analysis, the object-role modeling (ORM) approach is arguably more suitable than entity-relationship modeling and the class modeling technique within the Unified Modeling Language. Although ORM has been used for three decades and now has industrial modeling tool support, it has no official, standard meta-model. Because of its extensive capability for expressing business rules, ORM is currently being considered as a possible standard for business rules expression within the Object Management Group (OMG), and for use in ontology standards. To support these initiatives and the interchange of ORM model data between different software tools, this chapter discusses recent research by the authors to pave the way for a standard ORM meta-model that employs a standard interchange format. Two different ways of meta-modeling ORM features are presented, design trade-offs are examined, and extensions to ORM are proposed. As proof of concept, a working prototype that is compliant with the OMG’s Meta-Object Facility is also discussed.


Author(s):  
Herman Balsters ◽  
Terry Halpin

This paper provides formal semantics for an extension of the Object-Role Modeling approach to support declaration of dynamic rules. Dynamic rules differ from static rules by involving state transitions, rather than simply individual states. This paper restricts application of dynamic rules to single-step transactions, with a previous state (input to the transaction) and a new state (the result of that transaction). These dynamic rules specify an elementary transaction type by indicating which kinds of objects or facts (being added, deleted or updated) are involved. Dynamic rules may declare pre-conditions relevant to the transaction, and a post-condition stating the properties of the new state. In this paper the authors provide such dynamic rules with a formal semantics based on sorted, first-order predicate logic. The key idea underlying their solution is the formalization of dynamic constraints in terms of static constraints on the database transaction history.


Author(s):  
Terry Halpin

When modeling information systems, one often encounters subtyping aspects of the business domain that can prove challenging to implement in either relational databases or object-oriented code. In practice, some of these aspects are often handled incorrectly. This chapter examines a number of subtyping issues that require special attention (e.g. derivation options, subtype rigidity, subtype migration), and discusses how to model them conceptually. Because of its richer semantics, the main graphic notation used is that of second generation Object-Role Modeling (ORM 2). However, the main ideas could be adapted for UML and ER, so these are also included in the discussion. A basic implementation of the proposed approach has been prototyped in Neumont ORM Architect (NORMA), an open-source tool supporting ORM 2.


Author(s):  
Terry Halpin

Object-Role Modeling (ORM) is an approach for modeling and querying information at the conceptual level, and for transforming ORM models and queries to or from other representations. Unlike attribute-based approaches such as Entity-Relationship (ER) modeling and class modeling within the Unified Modeling Language (UML), ORM is fact-oriented, where all facts and rules are modeled in terms of natural sentences easily understood and validated by nontechnical business users. ORM’s modeling procedure facilitates validation by verbalization and population with concrete examples. ORM’s graphical notation is far more expressive than that of ER diagrams or UML class diagrams, and its attribute-free nature makes it more stable and adaptable to changing business requirements. This article explains the fundamentals of ORM, illustrates some of its advantages as a data modeling approach, and outlines some recent research to extend ORM, with special attention to mappings to deductive databases.


Sign in / Sign up

Export Citation Format

Share Document