scholarly journals Mapping Common Errors in Entity Relationship Diagram Design of Novice Designers

2021 ◽  
Vol 13 (1) ◽  
pp. 1-19
Author(s):  
Rami Rashkovits ◽  
Ilana Lavy
Keyword(s):  
Data Model ◽  
System Development ◽  
Data Modeling ◽  
Database Schema ◽  
Solo Taxonomy ◽  
Key Factor ◽  
Novice Designers ◽  
Entity Relationship ◽  
Entity Relationship Diagram ◽  
Conceptual Data

Data modeling in the context of database design is a challenging task for any database designer, even more so for novice designers. A proper database schema is a key factor for the success of any information systems, hence conceptual data modeling that yields the database schema is an essential process of the system development. However, novice designers encounter difficulties in understanding and implementing such models. This study aims to identify the difficulties in understanding and implementing data models and explore the origins of these difficulties. This research examines the data model produced by students and maps the errors done by the students. The errors were classified using the SOLO taxonomy. The study also sheds light on the underlying reasons for the errors done during the design of the data model based on interviews conducted with a representative group of the study participants. We also suggest ways to improve novice designer's performances more effectively, so they can draw more accurate models and make use of advanced design constituents such as entity hierarchies, ternary relationships, aggregated entities, and alike. The research findings might enrich the data body research on data model design from the students' perspectives.

Using Ontology and Rule-Based Reasoning for Conceptual Data Models Synonyms Detection

2019 ◽  
Vol 30 (1) ◽  
pp. 1-21
Author(s):  
Ljubica Kazi ◽  
Zoltan Kazi
Keyword(s):  
Data Model ◽  
System Development ◽  
Data Models ◽  
University Student ◽  
Specific Data ◽  
Entity Relationship Model ◽  
Relationship Model ◽  
Er Model ◽  
Entity Relationship ◽  
Conceptual Data

Conceptual data models can change during the information system development and teamwork phases, which require constantly monitoring with synonyms detection. This study elaborates on an approach for detecting synonyms in an entity-relationship model based on mapping with ontological elements. The use of a specific data model validator (DMV) tool enables formalization of the ontology and ER models, as well as their integration with the set of reasoning rules. The reasoning rules enable mapping between formalized elements of the ontology and ER model, and the extraction of synonyms. Formalized elements and reasoning rules are processed within Prolog for the extraction of synonyms. An empirical study conducted by using university student exams demonstrates usability of the proposed approach. The results show effectiveness in extraction of synonyms in all types of conceptual data model elements.

scholarly journals Aplikasi Rencana Pernikahan Berbasis Web Mobile

2021 ◽  
Vol 2 (2) ◽  
Author(s):  
Rizal Wardani ◽  
Yunita Prastyaningsih ◽  
Arif Supriyanto
Keyword(s):  
Data Model ◽  
Machine Language ◽  
Physical Data ◽  
Entity Relationship ◽  
Entity Relationship Diagram ◽  
Conceptual Data

Pernikahan adalah upacara pengikatan janji nikah yang dirayakan atau dilaksanakan oleh dua orang denganmaksud meresmikan ikatan perkawinan secara norma agama, norma hukum, dan norma sosial. Pasangan calonpengantin yang akan menikah harus memiliki persiapan yang matang. Untuk mendapatkan persiapan yangmatang maka pasangan calon pengantin perlu mendapatkan informasi mengenai layanan pernikahan secara lebihlengkap. Untuk menanggulangi permasalahan tersebut, maka perlu adanya sebuah sistem informasi yangmewadahi informasi-informasi mengenai layanan pernikahan yaitu Sistem Informasi Rencana PernikahanBerbasis Web Mobile. Aplikasi Rencana Pernikahan Berbasis Web Mobile ini menggunakan HypertextPreprocessor (PHP) sebagai bahasa pemrograman, MySQL sebagai penyimpanan database, perancanganmenggunakan Entity Relationship Diagram (ERD), Conceptual Data Model (CDM), Physical Data Model(PDM) serta Unified Machine Language (UML) dan metode waterfall. Data yang digunakan pada aplikasi inididapatkan melalui wawancara kepada penyedia layanan pernikahan di Kecamatan Pelaihari Kabupaten TanahLaut. Aplikasi ini dapat membantu pasangan calon pengantin mendapatkan informasi mengenai layananpernikahan, lokasi penyedia layanan pernikahan dan menentukan paket pernikahan sesuai dengan biaya yangdimilikinya serta memudahkan penyedia layanan pernikahan mempromosikan usaha mereka.

scholarly journals A Method For Reverse Engineering Legacy Accounting Systems

1998 ◽  
Vol 2 (3) ◽  
pp. 93-104
Author(s):  
Joseph H. Callaghan ◽  
Thomas W. Lauer ◽  
Eileen Peacock
Keyword(s):  
Reverse Engineering ◽  
Data Model ◽  
Data Modeling ◽  
Future Research ◽  
Accounting Systems ◽  
Reverse Engineer ◽  
Modeling Approach ◽  
Entity Relationship ◽  
Entity Relationship Diagram ◽  
General Journal

The growing emphasis on information for the development of products, services, and managing activities has increased the need for the integration of data which has been collected and used for various IS applications. Problems arise from the integration of information from such a variety of sources. One approach to this problem is reverse engineer these systems. Reverse engineering derives a data model from existing sys-tems with the aim of redesigning it. The paper describes a data modeling approach that takes data from general journal and an archetypal specialized journal and translates it into an entity-relationship diagram. The article also discusses areas for future research.

scholarly journals Graph Database Schema for Multimodal Transportation in Semarang

2019 ◽  
Vol 5 (2) ◽  
pp. 163
Author(s):  
Panji Wisnu Wirawan ◽  
Djalal Er Riyanto ◽  
Dinar Mutiara Kusumo Nugraheni ◽  
Yasmin Yasmin
Keyword(s):  
Public Transportation ◽  
Data Model ◽  
Database Schema ◽  
Bus Rapid Transit ◽  
Graph Database ◽  
Transportation Mode ◽  
Traveler Information ◽  
Multimodal Transportation ◽  
Entity Relationship ◽  
Entity Relationship Diagram

Background: Semarang has broad area that cannot be covered entirely by single transportation mode. To reach a specific location, people often use more than one public transportation mode. Apart from Bus Rapid Transit, another exist namely angkot or city transportation. Multimodal traveler information is then  required to help passenger searching for a route. Several studies of multimodal traveler information system has been conducted, however the data model for multimodal transportation did not conceived in detail.Objective: Proposes a database of multimodal transportation design using graph data model by taking Semarang as a case study.Method: We create our model in oriented entity-relationship diagram (O-ERD) and map this O-ERD to the graph database schema.Result: We develop our data model in graph database schema and we implement the model using Neo4J graph database for validation purpose. Our model consist of  three graph node label namely Shelter, Angkot Stopper, and Closer Place. To validate our model, we execute a search query using the Cypher query to look for location with closer place to it.Conclusion: Our data model was successfully developed and implemented. Searching transportation route in the implementation of our model has been conducted using cypher query. It can successfully display all possible paths and routes. Our query can distinguish between one mode of transportation with another.Keywords: Graph database, Multimodal transportation, Neo4j, Cypher

scholarly journals Sistem Informasi Rekam Medis Pada Klinik PT. Nippon Paint Jakarta

2020 ◽  
Vol 1 (1) ◽  
pp. 61-74
Author(s):  
Mohamad Siraji ◽  
Heri Kuswara
Keyword(s):  
Information System ◽  
System Development ◽  
Medical Data ◽  
Health Care Facilities ◽  
Use Case ◽  
Activity Diagram ◽  
Efficient Management ◽  
Entity Relationship ◽  
Entity Relationship Diagram ◽  
Clinic Medical

Medical record is a file that contains records and documents about patient identity, examination, treatment, actions and other services that have been provided to patients in health care facilities. Problems that occur in the Clinic PT. Nippon Paint Jakarta is an ineffective and efficient management of medical data. This information system aims to manage medical data quickly and accurately. This system development method uses SDLC by making UML diagrams such as use case diagrams, class diagrams, activity diagrams, entity relationship diagrams as stages of system design. This information system is based on WEB using the PHP programming language supported by SQL database. The results of the design of this system are expected to be one of the solutions to the problems that have occurred so far.   Keywords: Clinic, Medical Records, Informations Systems     Abstrak   Rekam medis adalah berkas yang berisi catatan dan dokumen tentang identitas pasien, pemeriksaan, pengobatan, tindakan dan pelayanan lain yang telah diberikan kepada pasien pada sarana pelayanan kesehatan. Permasalahan yang terjadi di Klinik PT. Nippon Paint Jakarta yaitu pengelolaan data medis yang kurang efektif dan efisien. Sistem informasi ini bertujuan supaya pengelolaan data medis dapat berjalan dengan cepat dan tepat. Metode pengembangan sistem ini menggunakan SDLC dengan membuat diagram-diagram UML seperti use case diagram, class diagram, activity diagram, entity relationship diagram sebagai tahapan perancangan sistem. Sistem informasi ini dibuat dengan berbasis WEB menggunakan bahasa pemrograman PHP yang didukung basis data SQL. Hasil rancang bangun sistem ini diharapkan dapat menjadi salah satu solusi dari permasalahan yang terjadi selama ini.   Kata kunci: Klinik, Rekam Medis, Sistem Informasi

scholarly journals Membangun Perpustakaan Digital Pada Madrasah Aliyah Negeri (MAN) 1 Sumbawa Besar

EXPLORE ◽  
2018 ◽  
Vol 8 (2) ◽  
pp. 13
Author(s):  
Suhardiman ◽  
Dwinita Arwidiyarti ◽  
Maspaeni ◽  
Belsana Butar Butar
Keyword(s):  
Life Cycle ◽  
System Development ◽  
Data File ◽  
Development Life Cycle ◽  
Entity Relationship ◽  
Entity Relationship Diagram

Perpustakaan mempunyai peranan penting dalam hal menyediakan informasi yang berkaitan dengan pengetahuan dan merupakan unsur penting dalam lembaga pendidikan. Keberhasilan dalam peningkatan efisiensi dan efektifitas pendidikan dapat didukung dengan kehadiran perpustakaan. Perpustakaan yang ada di MAN 1 Sumbawa Besar adalah perpustakaan non digital, di mana anggotanya adalah guru dan siswa yang ada di lingkungan MAN 1 Sumbawa Besar. Masalah yang muncul pada perpustakaan tersebut adalah adanya keterbatasan jumlah buku yang dimiliki sehingga seringkali buku yang akan dipinjam stoknya kosong di perpustakaan karena sedang dipinjam oleh peminjam lainnya, selain itu juga adanya batasan hari dan waktu layanan perpustakaan sehingga peminjaman buku hanya dapat dilakukan pada hari dan jam kerja. Untuk dapat mengakomodir kebutuhan akan buku dan tingginya minat baca pada guru dan siswa MAN 1 Sumbawa Besar maka aplikasi perpustakaan digital adalah solusi yang tepat. Aplikasi ini dibangun dengan menggunakan metode System Development Life Cycle (SDLC) yang merupakan metodologi klasik yang digunakan untuk mengembangkan, memelihara dan menggunakan sistem informasi yang terdiri atas beberapa tahapan yaitu tahap perencanaan, analisis, perancangan, seleksi, penerapan dan pemeliharaan. di mana perancangan sistemnya dibuat dengan menggunakan Flowchart Sistem untuk menggambarkan alur dari sistem yang dirancang dan Usecase Diagram untuk menggambarkan menu-menu yang dapat diakses oleh user. Perancangan database dibuat dengan menggunakan Entity Relationship Diagram yang menghasilkan 5 (lima) tabel yaitu Tabel User, Tabel Jenis, Tabel File, Tabel Kategori dan Tabel Ebook. Output tercetak yang dihasilkan berupa Laporan Data Anggota, Laporan Data File dan Laporan Data Ebook untuk diserahkan kepada Kepala Sekolah setiap bulan sekali. Dengan aplikasi perpustakaan digital ini perpustakaan pada MAN 1 Sumbawa Besar akan dapat meningkatkan pelayanannya kepada anggota dan juga pada pihak lain yang bukan anggota perpustakaan dengan menyediakan ebook dan file yang dapat diunduh kapanpun tanpa dibatasi jam layanan dan tanpa batasan stok buku fisik. Kata Kunci : perpustakaan, perpustakaan digital

The Objects Model and the Class Diagram

2011 ◽  
pp. 13-56
Author(s):  
Peretz Shoval
Keyword(s):  
Information Needs ◽  
Relational Model ◽  
Verbal Description ◽  
Database Schema ◽  
Class Diagram ◽  
Data Types ◽  
Data Definition ◽  
Er Model ◽  
Entity Relationship ◽  
Entity Relationship Diagram

The objects model (or object oriented [OO] model) is a conceptual-application model that is used to define a database schema representing a certain reality. The model views the world as consisting of objects belonging to classes. The objects of these classes have attributes, behavior (i.e., functions), and various relationships with other objects. The objects model can be presented as a class diagram (also termed OO diagram or objects diagram). Like an entity relationship diagram (ERD), the class diagram has two main goals: 1. To serve as a communication medium between the developers (analysts/ designers) and the users or their representatives. The diagram is created as a result of the interactions between the two parties, during which they discover and define the users’ information needs; the diagram serves like a contract between these two sides which summarizes the users’ needs. 2. To be the basis for further development of the information system (IS). Based on the diagram, it should be possible to design the database schema of the application, and (partially) the functions that it will have to perform. For that, it is necessary to transform the class diagram into an equivalent verbal description—an objects schema. This is done using an object definition language (ODL), similar to data definition language (DDL) in the relational model. In principle, all components of the class diagram are mapped to the objects schema. However, the objects schema includes more details which are not included in the diagram. For example, in the diagram each attribute has a name, and some attributes may have specific constraint definitions (e.g., key, unique); in the objects schema there are more detailed definitions, including the attributes’ domains or data types (e.g., numeric, char., real, etc.) and lengths. Another example, in the class diagram, we only write the names of the classes’ functions, while in the objects schema we specify the parameters of the functions. As aforementioned, there is a great deal of similarity between the OO and ER models and diagrams, since the ER model is one of the sources from which the objects model originated. But there are differences between the two models, which we will review later on. One of these differences is that the ER model is “static,” that is, it only deals with the data structure, while the objects model also includes “behavior,” that is, the functions that operate on the data. The rest of this chapter is dedicated to describing the components of the objects model and the class diagram. The description is organized in four main categories: objects and classes, attributes, relationships, and functions.

scholarly journals PERANCANGAN SISTEM INFORMASI MANAJEMEN ASET DAN INVENTARIS SMK N 7 PADANG

2014 ◽  
Vol 2 (1) ◽  
Author(s):  
Fitra Sani ◽  
Dharma Liza Said ◽  
Denny Kurniadi
Keyword(s):  
Asset Management ◽  
Management System ◽  
System Development ◽  
Information Management System ◽  
Language Program ◽  
System Method ◽  
Development Life Cycle ◽  
Search Data ◽  
Entity Relationship ◽  
Entity Relationship Diagram

Processing of asset management and inventarize at SMKN 7 Padang running manually such as inventarize of new stuff to be record through ledger by hand. Cause of that, the managing asset operator have troubles to manage and making asset management reports, managing and checking supply data of stuff, list of entry and ordering stuff, difficult to search data and making data stuff that already exist. To solve this problem, we made an information management system of asset management and inventaries. Scheme of the system method used system development life cycle (SDLC). It start from system design to phase scheme of detailed system, like flowmap, and DBMS (Database Of Management System) for databases, normalization, ERD (Entity Relationship diagram) and also use Java for language program and Neatbeans 7.4 for IDE. It will be implemented through the desktop. The advantages of this application is : facilitating in data processing and help the operator to manage the asset of inventaries at SMKN 7 Padang. Beside that, this program provide simplicity for students, teachers, and visitors to borrowing and repayment asset of inventarize at SMKN 7 Padang.

scholarly journals Developing Database System for Managing Medical Insurance Claims in the Human Resource Department

2020 ◽  
Vol 19 (2) ◽  
Author(s):  
Salma Eka Ramadhany ◽  
Hery Hamdi Azwir
Keyword(s):  
System Development ◽  
Systems Design ◽  
Medical Insurance ◽  
Database Systems ◽  
Flow Diagram ◽  
Private Company ◽  
Systems Planning ◽  
Entity Relationship ◽  
Entity Relationship Diagram ◽  
Five Phases

<p>PT. X Indonesia provides medical insurance for their employee from BPJS Kesehatan and other private company insurance. Currently, the data management of medical insurance members is not efficient and effective because the data regarding medical insurance are managed manually using MS Excel. The manual process leads to incorrect data input and causes a delay in the process of getting treatment and reimbursement claim process. The company will reimburse the payment but the process is long and complicated because the company should check the limitation for reimbursement claim per year. To solve the problem, database systems are constructed using System Development Life Cycle (SDLC) methodology which consists of five phases; systems planning, systems analysis, systems design, systems implementation, and system test, and deployment. The business process flow diagram of the current and proposed system is analyzed. After that, user requirements are determined. The data flow diagram and entity-relationship diagram (ERD) is constructed. And the system is developed using MS Access. Finally, the system is deployed. The result is an application running in MS Access that can manage medical insurance claim with more efficient and effective, compare to previous MS Excel.</p><p> </p>

scholarly journals KOMBINASI SISTEM BERBASIS WEB DAN ANDROID SEBAGAI APLIKASI PRESENSI KEGIATAN MENGGUNAKAN QR CODE

2021 ◽  
Vol 23 (1) ◽  
pp. 12-21
Author(s):  
Riovan Styx Roring ◽  
FX Nanang Sujatmiko
Keyword(s):  
System Development ◽  
Personal Data ◽  
Qr Code ◽  
Smart System ◽  
Quick Response Code ◽  
Development Life Cycle ◽  
Effective System ◽  
Waterfall Model ◽  
Entity Relationship ◽  
Entity Relationship Diagram

Registration and list of attendees are an important factor to be done in formal and informal activities. The purpose is to know the attendees’ personal data and presence. Registration and presence using the manual method such as form filling in a piece of paper produce problem, among them is over excess of paper and time consuming presence activity. Therefore, a new efficient and effective system that take advantage of Android Smartphone and Quick Response Code (QR Code) as Smart Attendance System is needed. The use of Android and QR Code technology simplify registration and presence process so that the proses would be much faster and efficient. The design of QR Code presence application based on Android is using System Development Life Cycle (SDLC) Waterfall model and designed using Use Case Diagram and Entity Relationship Diagram. The presence application is made using combination of two platform, that is Android and web. On the Android Smartphone there are scanner and administrator profile. Whilst at the web platform contain participant, event, and admin database. The existence of the design and Smart Attendance system implementation, registration and list of attendees process will be faster, efficient, and used as on of the smart system to support the smart city is expected.

Sign in / Sign up

Export Citation Format

Share Document