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.

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.

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 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.

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.

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.

scholarly journals PERANCANGAN SISTEM PENDUKUNG KEPUTUSAN KESESUAIAN LAHAN TANAMAN PADI KOMODITAS GOGO BERBASIS WEB

JURNAL IT ◽  
2020 ◽  
Vol 10 (2) ◽  
pp. 223-229
Author(s):  
Kamaruddin Kamaruddin ◽  
Hadi Sutrisno
Keyword(s):  
Source Code ◽  
Unified Modeling Language ◽  
Database Management System ◽  
Modeling Language ◽  
Use Case ◽  
Activity Diagram ◽  
Unified Modeling ◽  
Entity Relationship ◽  
Entity Relationship Diagram ◽  
Use Case Diagram

Kebutuhan lahan yang semakin meningkat, langkanya lahan pertanian yang subur dan potensial, memerlukan teknologi yang dapat membantu petani dan penyuluh pertanian untuk menoptimalkan penggunaan lahan maka dibuatlah sistem informasi Penentu Kesesuaian Lahan Tanaman Padi Komoditas Gogo berbasis website. Yang dapat membantu petani dan penyuluh pertanian mengoptimalkan penggunaan lahan yang sesuai dengan tanaman padi berdasarkan ciri-ciri karaktersitiknya. Sistem ini dikembangkan menggunakan metode pengembangan perangkat lunak Rapid Aplication Development (RAD) dengan pemodelan data Entity Relationship Diagram (ERD) dan pemodelan proses Unified Modeling Language (UML). Sistem ini berbasis web yang digunakan oleh penyuluh pertanian untuk mengetahui kondisi lahan pertanian jenis padi gogo untuk dapat mengoptimalkan penggunaan lahan secara berkelanjutan. Desain penelitian yang digunakan adalah UML (Unifel Modeling Language) yang didesain secara terstruktur yang terdiri dari rancangan model use case diagram, activity diagram, sequence diagram dan class diagram. Bahasa HTML, CSS dan Javascript digunakan untuk membangun antarmuka sistem sedangkan untuk pemprosesan web menggunakan bahasa pemprograman PHP dengan MySQL sebagai Database Management System dan framework CodeIgniter membantu dari segi kecepatan pengembangan dan efisiensi source code aplikasi. Penelitian ini menghasilkan sebuah sistem yang dapat membantu para penyuluh pertanian dan mempermudah dalam menganalisas kondisi lahan para petani jenis padi gogo.

scholarly journals Perancangan Sistem Informasi Berbasis Website pada Perkampungan Budaya Betawi Setu Babakan

2019 ◽  
Vol 8 (2) ◽  
pp. 67-72
Author(s):  
Ridwan Ahmad Ma'arif ◽  
Tri Ichsan Saputra ◽  
Mohamad Dimas Radityatama ◽  
Andez Apriansyah ◽  
Nur Hayati
Keyword(s):  
Unified Modeling Language ◽  
Modeling Language ◽  
Class Diagram ◽  
Unified Modeling ◽  
Entity Relationship ◽  
Entity Relationship Diagram

Indonesia merupakan negara kepulauan yang mana penggunaan media internet sebagai sarana penyebaran informasi sangat berguna, sebab berbagai jenis informasi dari bagian Indonesia manapun dapat diketahui dengan mudah. Pengguna internet di Indonesia telah mencapai 150 juta pada tahun 2019 yang mana angka tersebut mengalami kenaikan 13 persen atau sekitar 17 juta dari tahun sebelumnya, kemudian rata-rata setiap hari penggunaan waktu dengan internet yaitu selama 8 jam 36 menit. Perancangan website menggunakan metode pengumpulan data dan metode waterfall sebagai metode perancangan sistem. Digunakan diagram perancangan sistem berupa UML (Unified Modeling Language) yang terdiri dari usecase diagram dan class diagram serta ERD (Entity Relationship Diagram). Website dirancang dengan menggunakan framework CodeIgniter dengan tools Visual Studio Code dan MySQL sebagai sumber basis datanya. Pengujian dalam penelitian ini menghasilkan keberhasilan 100% dalam mengakses website diberbagai browser dan juga keberhasilan fungsi dari berbagai jenis interface yang dibangun.

scholarly journals THE APPLICATION OF UML IN THE PROTOTYPE OF DESIGN EXPERT SYSTEM FOR THE DIAGNOSIS OF CHILI DISEASES AND PESTS

2018 ◽  
Vol 5 (2) ◽  
pp. 214
Author(s):  
Muliadi Aziz ◽  
Irwan Budiman ◽  
Antar Sofyan
Keyword(s):  
Expert System ◽  
Unified Modeling Language ◽  
User Needs ◽  
Modeling Language ◽  
Use Case ◽  
Standard Size ◽  
Unified Modeling ◽  
Design Expert ◽  
Entity Relationship ◽  
Entity Relationship Diagram

<p><em>Prototype or archetype is the initial form or standard size of an entity. In the design field, a prototype is made before it is developed or precisely made specifically for development before it is made on an actual scale or before mass produced, it will feel very difficult if you do not have a compounding model to design a system. Therefore, to design a prototype expert system for diagnosing diseases and pests of chilli plants using the Unified Modeling Language (UML) method. The purpose of the implementation of this model is to meet all user needs for the software to be built. Manfaat dari model ini dapat membantu perancang perangkat lunak dalam membangun sistem pakar untuk mendiagnosis penyakit dan hama tanaman cabai. The result of this UML implementation is to obtain use case of system processing, diagram activity, entity relationship diagram, and form input output design.</em></p><p><em> </em></p>

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.

Sign in / Sign up

Export Citation Format

Share Document