Extracting Entity Relationship Diagram (ERD) from English Sentences

Amani Abdel-Salam Al-Btoush 보안공학연구지원센터 2015 International Journal of Database Theory and Appli Vol.8 No.2

Entity Relationship Diagram (ERD) is the first step in database design; it is an important step for the database designers, users, analyst, managers and software engineering. Since English is a universal language, this paper describes a methodology that extracts ERD from English sentences. This methodology is based on a predefined set of a heuristic rules that aims to extract the elements of the ERD, then these rules are mapped into a diagram. A diagram generator automatically converts the rules into the ERD according to the rules of generating. The proposed methodology is explained by examples to show how it can provide a mechanism for quickly and easily way in extracting the ERD.

A New Approach for Semantic Integrity Constraints Representation in Enhanced Entity-Relationship and Relational Database Schemas

Islam Hassan AlTarawneh 보안공학연구지원센터 2016 International Journal of Database Theory and Appli Vol.9 No.2

In this paper Semantic-Enhanced Entity Relationship (SEER) and Semantic –Relational Database (SRD) diagrams are proposed. SEER and SRD are extensions of Enhanced Entity Relationship (EER) and Relational Database (RD) diagrams respectively that are based on dealing with Semantic Integrity Constraints. EER and RD do not take semantic constraints in matter. A lots of information are lost because of the shortage of documentations. The proposed SEER and SRD models embed the semantic constraints using a new notations and pseudo code to give a full diagram fo

Generating ER Diagrams from Requirement Specifications Based On Natural Language Processing

Eman S. Btoush,Mustafa M. Hammad 보안공학연구지원센터 2015 International Journal of Database Theory and Appli Vol.8 No.2

An Entity Relationship (ER) data model is a high level conceptual model that describes information as entities, attributes, and relationships. Entity relationship modeling designed to facilitate database design. The abstract nature of Entity Relationship diagrams can be discouraging task to both designers and student alike. This paper deals with the problem of extracting ER elements from natural language specifications using Natural Language Processing (NLP). The approach provides the opportunity of using natural language documents as a source of knowledge for generating ER data model. The structural approach is used to parse specification syntactically based a predefined set of on heuristics rules. Extracted words with its Part Of Speech (POS) mapped into entities, attributes and relationships, which are the basic elements of ER diagrams.

Conceptual Data Modeling: Entity-Relationship Models as Thinging Machines

Al-Fedaghi, Sabah International Journal of Computer ScienceNetwork S 2021 International journal of computer science and netw Vol.21 No.9

Data modeling is a process of developing a model to design and develop a data system that supports an organization's various business processes. A conceptual data model represents a technology-independent specification of structure of data to be stored within a database. The model aims to provide richer expressiveness and incorporate a set of semantics to (a) support the design, control, and integrity parts of the data stored in data management structures and (b) coordinate the viewing of connections and ideas on a database. The described structure of the data is often represented in an entity–relationship (ER) model, which was one of the first data-modeling techniques and is likely to continue to be a popular way of characterizing entity classes, attributes, and relationships. This paper attempts to examine the basic ER modeling notions in order to analyze the concepts to which they refer as well as ways to represent them. In such a mission, we apply a new modeling methodology (thinging machine; TM) to ER in terms of its fundamental building constructs, representation entities, relationships, and attributes. The goal of this venture is to further the understanding of data models and enrich their semantics. Three specific contributions to modeling in this context are incorporated: (a) using the TM model's five generic actions to inject processing in the ER structure; (b) relating the single ontological element of TM modeling (i.e., a thing/machine or thimac) to ER entities and relationships; and (c) proposing a high-level integrated, extended ER model that includes structural and time-oriented notions (e.g., events or behavior).

비즈니스 프로세스 서술 도구의 성능 비교 연구

안현섭(Ahn, Hyunsup),김용재(Kim, Yong Jae),함유근(Hahm, Yu Keun) 한국상품학회 2008 商品學硏究 Vol.26 No.4

정보시스템의 발전과 함께 현실업무가 더욱 복잡해지면서, 정보시스템 개발 초기단계에서 사용자의 요구사항이 누락되거나 중복되는 경우가 자주 발생하고, 차후에 이를 수정하기 위한 노력이 증대되면서, 전체개발비용과 기간이 증가하게 된다. 이 문제를 해결하기 위해서 업무 프로세스를 표현하기 위한 다양한 방법론이 제안되어왔지만, 각 방법론의 우열을 어떻게 가릴지에 대한 체계적인 항목별 연구는 이제까지 없었다. 이 연구에서는 사용자가 직관적으로 이해할 수 있고, 분석가가 업무 프로세스를 충분히 표현할 수 있으며 동시에 시스템구축 비용을 최소화할 수 있는 방법론이 가장 이상적이라는 점을 고려해서, 누락도, 중복도, 명확도, 표현력 등의 방법론 평가기준을 제안하며, 이 지표를 은행의 자산건전성 평가업무라는 표준 업무에 적용해서 각 방법론의 우위내지는 문제점들을 살펴본다. 프로세스 중심 기법인 자료흐름도와 유즈케이스 다이어그램과 비교할 때, 데이터 중심 기법인 개체관계도가 상대적으로 낮은 함축성과 높은 복잡성에도 불구하고 낮은 누락도와 명확한 표현력을 가지고 있으며, 업무기술서와 병행될 때 프로세스 함축과 누락에 대한 부담을 크게 감소시킬 수 있을 것으로 나타난다. In developing information systems, frequent omissions and redundancies of user requirements lead to increasing total cost should such fallacies be corrected later. Thus business requirements may better be formalized consistently in order to shorten development cycles as well as to control overall costs. To cope with this problem, various methods for describing business processes have been proposed in the past. Yet there has been no general agreement as to which model works better over which. This research approaches the problem by defining quality dimensions measuring effectiveness of individual methods and provides a general framework for analyzing and appraising competitive methodologies by specifically focusing on Entity-Relationship Diagram, Data Flow Diagram, and Use Case Diagram. Empirically speaking, Entity-Relationship Diagram outclasses the other two in simplicity, correctness, and expression power, possibly reflecting its dominance over other tools. We find that, despite that its lower readability, its high expression power and convenience quite surpasses its drawbacks. Additionally, it also makes sense to adequately use well-formed job descriptions to enjoy considerable synergy with Entity-Relationship Diagram for successful information systems developments.

XML 스키마의 개념적 모델링을 위한 확장된 개체관계 모델

정인환,김영웅 한국인터넷방송통신학회 2015 한국인터넷방송통신학회 논문지 Vol.15 No.1

XML은 인터넷 상의 데이터의 표현 및 교환의 사실상 표준으로 자리 잡고 있으며, XML 자체가 데이터를 저 장하기 위한 논리적 구조를 표현하고 있지만, 다양하고 복잡한 표현으로 인해 문서 구조를 한 눈에 파악하기에는 어려 운 점이 있어 개념적 모델의 도구로 사용하기 적절하지 못한 점이 있다. 본 논문은 XML 스키마 문서 구조를 확장된 개체관계 모델을 이용하여 그래픽 형태로 개념적 모델링할 수 있는 기법을 제안한다. 이를 위해 XML 스키마 구조를 표현하기 위해 확장된 개체관계 모델을 제시하고, XML 스키마 요소들을 확장된 개체관계 모델로 표현하기 위한 표현 규칙들을 제시하고, 제안한 기법으로 모델링한 개념적 모델을 논리적 모델인 XML 스키마 문서로 매핑하는 사례를 통 해 본 기법의 완전성을 보여준다. XML has become one of the most influential standard language for representing and exchanging data on internet. However, XML itself has a ability to represent a logical structure for storing and managing data, it is inadequate to use as a conceptual modeling tool because of its complexity for representing the document structures. In this paper, we propose the graphical form of conceptual modeling techniques for representing the structure of the XML schema documents using an extended entity relationship diagram. For this, extended entity relationship model is presented for representing the XML schema structure, transformation rules are presented for transforming extended entity relationship model into XML schema document to show the completeness of the proposed model.

비서직 종사자를 위한 업무 데이터베이스 설계 방안에 대한 연구

신동희(Shin Dong-Hee),김명옥(Kim Myong-Ok) 한국비서학회 2006 비서·사무경영연구 Vol.15 No.1

본 연구는 비서들의 효율적 사무정보처리를 위해 실무에서 곧바로 적용하여 업무를 처리할 비서 업무지원 데이터베이스를 설계하는데 그 목적이 있다. 설계에 알서 비서직 종사자의 데이터베이스의 인지도 및 업무에서의 필요성 및 활용도를 파악하기 위해 총 203명의 비서직 종사자를 대상으로 설문조사를 실시하였다. 조사 결과 데이터베이스에 대한 지식을 보유하고 있는 비서직 종사자들이 업무수행 등을 위해, 데이터베이스에 대한 지식 보유 필요성을 높게 평가해 데이터베이스의 지식 보유와 교육이 매우 필요한 상황임을 스스로도 인지하고 있음이 확인되었다. 특히, 업무를 위한 비서데이터베이스 활용도 조사 결과가 정보관리직의 결과와 비교해 크게 낮은 것으로 나타나 비서직 종사자들도 정보 관리 업무가 점점 강조되고 있는 사회적 요구에 발맞추어 정보 관리의 핵심 도구인 데이터베이스 활용도를 높이기 위한 방안 마련이 필요할 것으로 판단되었다. 또한 현재 업무 환경에 비서 업무를 지원하기 위해 구축된 데이터베이스가 없다고 응답한 응답자의 경우 그 필요성에 대해 매우 높이 평가한 결과로 보아 이들에게 비서 업무 지원 데이터베이스 구축 및 활용이 매우 시급한 시점임이 재확인되었다. 이를 위해 비서 업무를 위한 데이터베이스를 E-R 모델링 기법을 이용해 설계하였다. 우선 이의 기초자료 수집을 위해 18명의 현직 비서들에게 반구조화 된 설문지를 배포하고 수집하였다. 이 조사로 비서 업무 내용 및 현재 사용하고 있는 데이터베이스의 문제점, 현재 업무를 데이터베이스화하지 못한 사유를 파악해내고 비서 데이터베이스의 근간이 되는 총 27개의 개체(entity)를 추출해 내었다. 모든 개체들을 ERD로 도식화하였으며 개체와 속성간의 관계 스키마를 생성하였고 요구 사항을 반영한 질의문(query) 일체를 최종 제안하였다. 이 결과물이 비서직 종사자들에게 데이터베이스 기술 및 지식을 효과적으로 전달하는 기초자료로 활용되며, 향후 비서 데이터베이스의 구축과 운용의 체계를 세우는데 필요한 핵심 근거로, 또한 국내 각 사무관련학과에서 데이터베이스의 이론과 실습의 균형 있는 교육을 위한 기초자료로 활용될 것을 기대한다. The purpose of this research is to gauge awareness among office professionals ("OP" henceforth) of database, to quantify the practical usage of database and to propose a database model designed based on the research results specifically for OPs. Current understanding/usage of Of'-support database(henceforth "OPDB") and need for additional information/skills. are based on a survey of 203 OPs in the field. The survey shows that OPs themselves with current DB knowledge put heavy emphasis on the need of knowledge on DB for career advancement and operations. Preparation and promotion of DB usage increase by OPs appear to be a significant issue. as increased need for information management trend is expected to continue: however the usage rate of DB by OP staffs recorded significantly below compared to average information system professions' usage rate: In addition. respondents who pointed the lack of effective OPDB available considered need for such system higher than the other group, which reaffirms our view on necessity of urgent structuring and usage of OPDB. For this purpose, a relational database model was designed based on the research result. First. a need analysis were performed on a data collected from an open-ended survey conducted with 18 active OPs to determine task list. the limitations of the current available database tools. and to design the database. Finally 27 separate entities and their attributes were identified. Based on relational database model, an entity relationship diagram was used to define relationship between entities. Also. sample queries for extracting data from the relational database are provided. The study results showed the level of OPs' awareness and utilization and followed is a database model designed based on the analysis on their tasks and requirements. The implication of this research is to generate awareness and interest of database among OPs. to be used as bases for designing OPDB and to be used to develop a well-balanced curriculum of database theory and hands on training for all business schools in the country.

쇼핑몰 데이터베이스 설계를 위한 의미객체 모델링

전태보,김기동,오준형 江原大學校 産業技術硏究所 2005 産業技術硏究 Vol.25 No.A

Semantic object model has widely been recognized as an alternative data modeling approach to entity-relationship model for database system design. In this study, we have presented a semantic object model for intermediary type shopping mall consisting of multiple buyers and sellers. Essential processes and information with regard to the customer management, product management, price estimation, product order etc. have been considered for this study. Upon careful examination and analysis of them, a detailed semantic objects and attributes have been drawn and structured into semantic object diagrams. The final objects were converted into an entity-relationship diagram so that intuitive comparison could be made for relational database design. The results in this study may form a conceptual framework for both academic concerns and more complicated system applications.

Unified Modeling Language and Enhanced Entity Relationship : An Empirical Study

Manal Mahmoud Alkoshman 보안공학연구지원센터 2015 International Journal of Database Theory and Appli Vol.8 No.3

A perfect design of the diagrammatic notations is necessary to communicate between the designer and the user at the requirements analysis stage. The Unified Modeling Language (UML) and Enhanced Entity Relationship (EER) are typically used for designing large systems and applications. On paper, diagrammatic notations can be used to develop or perform maintenance on the application. Any notations used, must represent business rules accurately. At the same time, the notations must be understandable to manager, user and programmer. ER and EER diagrams have been taught in colleges and universities for many years. In recent years, the Unified Modeling Language has appeared for the representation of relational databases. There are many articles in the literature discussing the efficacy of using the UML in modeling relational database systems. The choice between diagrammatic notations does not show any thoughtfulness for an understanding of the human reader. This study focuses on a comparison between the EER and the UML Class Diagram, the cause of the common notations and acceptance among system analysts and programmers. It was proven through an experiment on the sample of students participating in the experiment. The experiment takes the opinion of information technology students to determine which the best diagrammatic notation for them to use. These students will be programmers and system analysts in the future. The results identified through experiment are the favorite for graphic students, and the result can show any relational model closer to the user and manger.

Requirement-Oriented Entity Relationship Modeling

Lee, Sang-Won,Shin, Kyung-Shik Korea Data Strategy Society 2010 Journal of information technology applications & m Vol.17 No.3

Most of enterprises depend on a data modeler during developing their management information systems. In formulating business requirements for information systems, they widely and naturally use the interview method between a data modeler and a field worker. But, the discrepancy between both parties would certainly cause information loss and distortion that lead to let the systems not faithful to real business works. To improve or avoid modeler-dependant data modeling process, many automated data design CASE tools have been introduced. However, since most of traditional CASE tools just support drawing works for conceptual data design, a data modeler could not generate an ERD faithful to real business works and a user could not use them without any knowledge on database. Although some CASE tools supported conceptual data design, they still required too much preliminary database knowledge for a user. Against these traditional CASE tools, we proposed a Requirement-Oriented Entity Relationship Model for automated data design tool, called ROERM. Based on Non-Stop Methodology, ROERM adopts inner systematic modules for complete and sound ERD that is faithful to real field works, where modules are composed of interaction modules with a user, rules of schema operations and sentence translations. In addition to structure design of ROERM, we also devise detailed algorithms and perform an experiment for a case study.