Reference Scheme Modeling

2019 ◽  
pp. 227-254
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Definite Descriptions ◽  
Modeling Languages ◽  
Database Modeling ◽  
Language Version ◽  
Unified Modeling ◽  
Version 2.0 ◽  
Reference Scheme ◽  
Entity Relationship ◽  
Object Role Modeling

In natural language, individual things are typically referenced by proper names or definite descriptions. Data modeling languages differ considerably in their support for such linguistic reference schemes. Understanding these differences is important both for modeling reference schemes within such languages and for transforming models from one language to another. This chapter provides a comparative review of reference scheme modeling within the Unified Modeling Language (version 2.5.1), the Barker dialect of entity relationship modeling, Object-Role Modeling (version 2), relational database modeling, the Web Ontology Language (version 2.0), and LogiQL (an extended form of datalog). The authors identify which kinds of reference schemes can be captured within these languages as well as those reference schemes that cannot be captured. The analysis covers simple reference schemes, compound reference schemes, disjunctive reference, and context-dependent reference schemes.

Modeling of Linguistic Reference Schemes

2015 ◽  
Vol 6 (4) ◽  
pp. 1-23 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Definite Descriptions ◽  
Modeling Languages ◽  
Database Modeling ◽  
Language Version ◽  
Unified Modeling ◽  
Ontology Language ◽  
Comparative Review ◽  
Entity Relationship ◽  
Object Role Modeling

When using natural language, people typically refer to individual things by using proper names or definite descriptions. Data modeling languages differ considerably in their support for such linguistic reference schemes. Understanding these differences is important for modeling reference schemes within such languages and for transforming models from one language to another. This article provides a comparative review of reference scheme modeling within the Unified Modeling Language (version 2.5), the Barker dialect of Entity Relationship modeling, Object-Role Modeling (version 2), relational database modeling, and the Web Ontology Language (version 2.0). The author identifies which kinds of reference schemes can be captured within these languages as well as those reference schemes that cannot be. The author's analysis covers simple reference schemes, compound reference schemes, disjunctive reference and context-dependent reference schemes.

Comparing Metamodels for ER, ORM and UML Data Models

2011 ◽  
pp. 23-44 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Modeling Language ◽  
Conceptual Schema ◽  
Database Modeling ◽  
Unified Modeling ◽  
Trade Offs ◽  
Information Engineering ◽  
Class Diagrams ◽  
Entity Relationship ◽  
Object Role Modeling

This chapter provides metamodels for some of the main database modeling notations used in industry. Two Entity Relationship (ER) notations (Information Engineering and Barker ER) are examined in detail, as well as Object Role Modeling (ORM) conceptual schema diagrams. The discussion of optionality, cardinality and multiplicity is widened to include Unified Modeling Language (UML) class diagrams. Issues addressed in the metamodel analysis include the normalization impact of non-derived constraints on derived associations, the influence of orthogonality on language transparency, and trade-offs between simplicity and expressibility. To facilitate comparison, the same modeling notation is used to display each metamodel. For this purpose, ORM is used because of its greater expressibility and clarity.

Object-Role Modeling

2010 ◽  
Vol 1 (1) ◽  
pp. 33-57 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Role Modeling ◽  
Modeling Language ◽  
Conceptual Level ◽  
Graphical Notation ◽  
Unified Modeling ◽  
Class Diagrams ◽  
Entity Relationship ◽  
Object Role Modeling ◽  
Business Requirements

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.

Objectification of Relationships

2011 ◽  
pp. 106-123 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Information Modeling ◽  
Graphic Notation ◽  
Unified Modeling ◽  
Modeling Approaches ◽  
Depth Analysis ◽  
Practical Guidelines ◽  
Entity Relationship ◽  
Main Ideas ◽  
Object Role Modeling

Some popular information-modeling approaches allow instances of relationships or associations to be treated as entities in their own right. Object-role modeling (ORM) calls this process “objectification” or “nesting.” In the unified modeling language (UML), this modeling technique is called “reification,” and is mediated by means of association classes. While this modeling option is rarely supported by industrial versions of entity-relationship modeling (ER), it is allowed in several academic versions of ER. Objectification is related to the linguistic activity of nominalization, of which two flavors may be distinguished: situational and propositional. In practice, objectification needs to be used judiciously, as its misuse can lead to implementation anomalies, and those modeling approaches that permit objectification often provide incomplete or flawed support for it. This chapter provides an in-depth analysis of objectification, shedding new light on its fundamental nature, and providing practical guidelines on using objectification to model information systems. Because of its richer semantics, the main graphic notation used is that of ORM 2 (the latest generation of ORM); however, the main ideas are relevant to UML and ER as well.

Constraints on Conceptual Join Paths

2011 ◽  
pp. 258-277 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Conceptual Modeling ◽  
Information Modeling ◽  
Modeling Language ◽  
Weak Support ◽  
Unified Modeling ◽  
Systems Model ◽  
Entity Relationship ◽  
Object Role Modeling ◽  
Object Oriented Systems

To ensure that a software system accurately reflects the business domain that it models, the system needs to enforce the business rules (constraints and derivation rules) that apply to that domain. From a conceptual modeling perspective, many application domains involve constraints over one or more conceptual schema paths that include one or more conceptual joins (where the same conceptual object plays roles in two relationships). Popular information modeling approaches typically provide only weak support for such conceptual join constraints. This chapter contrasts how these join constraints are catered for in object-role modeling (ORM), the Unified Modeling Language (UML), the Object-oriented Systems Model (OSM), and some popular versions of entity-relationship (ER) modeling. Three main problems for rich support for join constraints are identified: disambiguation of schema paths, disambiguation of join types, and mapping of join constraints to implementation code. To address these problems, some notational, metamodel, and mapping extensions are proposed.

scholarly journals Rancang Bangun Sistem Informasi Penjualan Fashion Berbasis Web

2018 ◽  
Vol 13 (3) ◽  
pp. 22-28
Author(s):  
Budi Sudradjat
Keyword(s):  
Product Information ◽  
Unified Modeling Language ◽  
Design Code ◽  
Application Development ◽  
Web Based ◽  
Unified Modeling ◽  
Online Sales ◽  
Wide Range ◽  
Entity Relationship ◽  
Entity Relationship Diagram

Sales System at H2H Couple Fashion today still use manual and very simple. Buyers must come directly so as not effective and efficient. Means of promotion there is inadequate so poorly known, it is harder to obtain for potential buyers. With the establishment of an online sales system web-based  is expected to provide ease of transaction as well as a means of effective and efficient promotion with a wide range of markets and provide satisfaction to customers thereby increasing profits for the company. Design, code creation, testing and support. by using a modeling tool such as a unified Modeling Language (UML), Entity Relationship Diagram (ERD) and data collection techniques by observation, and interviews. While the database application development tools using MySQL and PHPMyAdmin and PHP programming language, Adobe Dreamweaver CS6 text editor. This application provides product information and generate reports including product reports and sales reports.

scholarly journals Pembangunan Sistem Informasi Kartu menuju Sehat (KMS) Balita Berbasis WEB Studi Kasus: Posyandu KASIH BUNDA II

2021 ◽  
Vol 4 (2) ◽  
pp. 75-81
Author(s):  
Romzah Romzah ◽  
Yohanes Eka Wibawa ◽  
Pramitha Dwi Larasati
Keyword(s):  
Vitamin A ◽  
Unified Modeling Language ◽  
Sequence Diagram ◽  
Modeling Language ◽  
Class Diagram ◽  
Activity Diagram ◽  
Unified Modeling ◽  
Entity Relationship ◽  
Entity Relationship Diagram

Posyandu (Pos Layanan Terpadu) Kasih Bunda II merupakan pelayanan masyarakat yang bergerak pada bidang kesehatan balita. Posyandu ini memberikan pelayanan kesehatan seperti pengukuran berat badan, tinggi badan, pemberian vitamin A, pemberian obat cacing dan pemberian imunisasi dasar untuk balita. Pencatatan posyandu menggunakan media penulisan, sehingga membutuhkan 1 hari untuk menyelesaikan pencatatan posyandu dan merekap ulang data. Beberapa informasi tentang posyandu tidak tersalurkan seperti sulitnya mendeteksi perkembangan balita karena tidak ada laporan yang mendukung (harus memilah satu persatu data balita). Salah satunya dalam pengisian Kartu Menuju Sehat (KMS) balita, pengisian dapat dibuat lebih efektif dan efisien dengan dibuat secara digital, pengisian KMS tidak perlu melewati tahap yang panjang karena pencatatan, perhitungan, pelaporan terlalu rumit dengan buku-buku laporan yang banyak. Berdasarkan masalah tersebut maka dilakukan pembangunan sistem informasi menggunakan metode waterfall sistem dibangun menggunakan bahasa pemrograman PHP dan Database MySQL. Sistem informasi ini dirancang dengan sistem UML (Unified Modeling Language) yang terdiri dari Usecase Diagram, Activity Diagram, Sequence Diagram dan Class Diagram serta menggunakan Entity Relationship Diagram. Hasil yang diperoleh adalah sebuah sistem informasi berbasis web yang mampu mengelola data posyandu dan membantu pelaksanaan posyandu serta menyimpan arsip-arsip posyandu. Mendapatkan laporan semua balita, data kunjungan balita dan laporan grafik status gizi balita untuk orang tua.

scholarly journals Are we teaching UML according to what IT companies need? A survey on the São Carlos-SP region

2021 ◽  
Author(s):  
João Choma Neto ◽  
Luiz Henrique Ten Caten Bento ◽  
Edson OliveiraJr ◽  
Simone Do Rocio Senger Souza
Keyword(s):  
Unified Modeling Language ◽  
Use Case ◽  
Modeling Languages ◽  
Software Modeling ◽  
Unified Modeling ◽  
Agile Processes ◽  
Universal Language ◽  
Specific Subset ◽  
Development Processes ◽  
The Many

The Unified Modeling Language (UML) arisen intending to unify the many modeling languages and become the universal language for software modeling. Since its creation, more than 25 years have passed. With the growing success of agile methodologies for software development, supported by less modeling and documentation manifest, the use of UML-driven software processes has decreased, thus a specific subset of diagrams has been adopted, such as use case, class, and sequence. On the other hand, in academia, UML is still being taught in Computing courses, most of the time without knowing whether what is taught is what the industry needs for practical use. This paper presents an overview of the UML adoption in IT companies of the region. We analyzed quantitative and qualitative data to support academia at focusing on the most used UML diagrams by practitioners. We constructed a survey composed of 21 questions, distributed to 10 region companies, and we received 24 answers. The results of our study show high usage of UML, including companies adopting agile methods. Certain diagrams are more intensively used, for instance, use case diagrams. The results provide directions to improve UML teaching, focusing on diagrams that best adhere to the development processes employed, in particular, agile processes.

Two Meta-Model for Object-Role Modeling

2011 ◽  
pp. 17-42 ◽  
Author(s):  
Dave Cuyler ◽  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Role Modeling ◽  
Tool Support ◽  
Business Rules ◽  
Conceptual Information ◽  
Meta Model ◽  
Trade Offs ◽  
Interchange Format ◽  
Entity Relationship ◽  
Object Role Modeling

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.

Sign in / Sign up

Export Citation Format

Share Document