Mapping XML Schema to Entity Relationship and Extended Entity Relationship Models

The current trend toward increasing database applications and end-user computing brings about the need for effective training and support tools that enable end users to perform logical database designs. This paper presents a unique comparison of a network-based data model (the extended entity relationship (EER)) and a hierarchical-based data model (the structured object model (SOM)) and their associated logical database design methods, LRDM (EER-based) and the SOM method, in end-user logical database design. The SOM method, based on an object-oriented knowledge representation scheme, is a new structured method designed to be less susceptible to designer errors and yet capable of maintaining ease of understanding and use. The Logical Relational Design Methodology (LRDM), based on the EER model, shares some common characteristics with the SOM method. In the analytic comparison the basic components and constructs of EER and SOM, as well as their use in the logical design process, are compared to derive a qualitative assessment of the two methods. Two experiments using novice database designers were conducted to examine the effectiveness of each method in leading to accurate logical designs, the time needed for task completion and the improvement in performance over a short training period. To confirm the findings from other studies on logical database design using non-graphic methods versus using graphic methods, the normalization method was included in one of the experiments. The results showed that end users performed better with graphic methods and also preferred them to the non-graphic (normalization) method. Furthermore, users learned and improved in a short period using LRDM (EER-based). However, users of the SOM method generated more accurate designs, were able to identify more complex relationships, and had more significant improvements during the training period than did users of LRDM (EER-based).

Information integration is vital for keeping manufacturing operations competitive. A case study approach has been adopted to better understand the role of informatio in integrated manufacturing. Information is now considered a corporate asset. The creation, processing, movement and security of information is therefore as important as the products/services of an enterprise. The case studies have helped in identifying the requirements and issues involved in developing an information system and supporting software framework for a manufacturing enterprise. This paper deseribes a case study dealing with the integrated manufacture of optical fiber products. A phased development and implementation approach was adopted where a small, manageable slice of the system is considered for the case study followed by functional modeling (IDEFO) and data flow modeling (data flow diagrams). This identifies the pieces of information of interest. The information relationships are modeled using extended entity relationship (EER) diagrams which are then mapped to a relational model. The relational tables thus obtained were implemented on a commercial Database Management System (DBMS). The functional constraints and application interfaces were then built using Structured Query Languages (SQL) and commercial application interface tools. Subsequent sections describe the functional models, data flow diagrams (DFDs), EER diagrams, relational database design and user/application interfaces developed for the system. Implementation experiences and observations are discussed along with the applications of the implemented system. The case study has helped in developing a preliminary data model (i.e., a model about data by which a reasonable interpretation of the data can be obtained) for material handling (MH) functions.

XML data exchange has become ubiquitous in Business to Business (B2B) collaborations. Automating as much as possible the exchange of XML data between enterprise systems is a key requirement for ensuring agile interoperability and scalability in B2B collaborations. The lack of standardized XML canonical models or schemas in B2B data exchange, as well as semantic differences and inconsistencies between conceptual models of those that want to exchange XML data implies that XML data cannot be directly and fully automatically exchanged between B2B systems. We are left with the option of providing techniques and tools to support humans in reconciling the differences and inconsistencies between the data models of the parties involved in a data exchange. In this paper we introduce such a technique and tool for XML data exchange. Our approach is based on a lifting mechanism of XML schemas and instances to an object-oriented model, and the design and execution of data mediation at the object-oriented level. We use F-logic -- an object oriented rule language -- together with its Flora2 engine as the underlying mechanism for providing an abstract, object-oriented model of XML schemas and instances, as well as for specification and execution of the mappings at the model level. This provides us with a fully-fledged tool for design- and run-time data mediation, by focusing at the actual semantic models behind the XML schemas, rather than having to deal with the technicalities of XML in the data mediation process. Finally, we present the architecture of the current data exchange system and report on preliminary evaluation of our system.

A methodology which merges the data flow diagram (DFD) and the entity-relationship (ER) models as a front-end to an object-oriented software development process is described. In order to take advantage of the benefits of both approaches and to limit the disadvantages, a tool which builds an object-oriented specification model from a set of data flow diagrams is used. The object-oriented specification is in an Ada-like package format which specifies data objects and their operations. An extended ER model and user documents are produced from the DFD to provide information to the user. The ER produced model is used as an intermediate tool to illustrate the connections between each object. >

Database technologies are a core component of computing technology curricula. Their importance will only continue to expand as more and more data are retained in database systems. An effective database system is predicated on a good data model. Database design is the conceptualization of an underlying data model that progresses from identifying user requirements to graphically depicting those requirements and finally mapping the graphical models to a set of tables implemented in a physical database system. The abstract nature of much of database design makes it challenging to teach. This paper presents a set of software animations designed to support the teaching of database design concepts. Topic areas covered include mapping problem descriptions to Entity Relationship (ER) diagrams, mapping ER diagrams to tables, normalization and denormalization and comparison of various ER notation sets. The animations are fairly intuitive to use and are independent of any specific database text or product. They are intended to provide supplemental instructional support and also provide students with additional learning opportunities.

The design and implementation of a database modeling aid called Database Designer (DBD) using VP-Expert are discussed. The DBD expert system is intended to help novice users design a proper database by asking questions of the user and thus incrementally building a structure for an extended entity relationship (ER) diagram. The authors discuss their approach to system design for DBD and implementation issues specific to VP-Expert, such as combining backward chaining and forward chaining, procedural techniques, and transparency and visibility of VP-Expert statements. This study indicates that applying a systematic, structural approach, properly commenting the code, and logically grouping rules can make an expert system programming approach viable for designing a complex procedural design application like DBD. >

This paper researches the development method of domain ontology from the point of view of reverse engineering. Taking the relationship data model as the object, the paper analyzes how to identify the structural information of relationship mode from the legacy system. Then, the paper obtains the semantic information of the relationship mode making use of the extended entity relationship (EER) diagram and establishes the domain ontology model.

In the information age business activities of an organization can not be separated from the role of information systems and information technology, information system is a mainstay tool in order to win the competition in the industry. PT Khatulistiwa Suryanusa is a company engaged in the service and special Parts for Sale Jeep. In the company's sales and purchase process is still done manually. this causes various problems, including the management of data in the warehouse have difficulty to control the stock of goods in and out. To overcome such problems, the author intends to try to handle the processing of data on PT Khaulistiwa Suryanusa and design a system inventory information. The data was collected by the method of literature review, interviews, and observation method. Systems development method of information system using the waterfall method. whereas the method of data flow is used structured methods, DFD (Data Flow Diagram) describe the functional model and ERD (Entity Relationship Diagram) to describe the data model. The information system was built using Visual Basic software with database microsoft access. Keywords: system inventory information, Waterfall, ERD

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.

Since its inception by P. P. Chen in 1976 (Chen, 1976), the entity-relationship (ER) model has played an important role in the fields of database design, information systems analysis, and object orientation. During the past decades, a number of new concepts have also been introduced into the ER model by various researchers (e.g., Dos Santos, et al., 1979; Scheuermann, et al., 1979; Elmasri, et al., 1985; Teorey, et al., 1986; Gogolla, et al., 1991), giving rise to the notion of the enhanced (or extended) entity-relationship (EER) models. These efforts have largely enriched the usefulness and expressiveness of ER/EER as a conceptual model in many respects.

Data processing of industrial and field work practices in SMK Pasundan Rancaekek is still semi manual using a spreadsheet application. This can lead to various problems, namely checking students who have not made payment and registration of PRAKERIN, making evidence of transactions and reports effectively, placing students in accordance with the capacity of the place of PRAKERIN and scheduling supervisors in conducting visits. The method used is the System Development Life Cycle (SDLC), which includes system analysis, system design, system implementation, and system operation. Whereas to analyze user system requirements using Flowmap analysis, Context Diagrams, Data Flow Diagrams (DFD), Entity Relationship Diagrams (ERD), Data Dictionaries, and Structure Charts. The design of the PRAKERIN data processing information system uses Microsoft Visual FoxPro 9.0 as a system implementation, report generation, and for database processing. Thus the system designed by the author is expected to facilitate the PRAKERIN data processing process so that it is more effective and efficient.

Every person need an information and one of the media to spread it efficientlly is internet. User can share information to around of the world with website, blog, or social media. However there are a lot of institution that cant use this technology, one of them is ”Batu Penjuru” Orphanage ini Kulonprogo, Yogyakarta. This is the reason of writer make this research about the website design of ”Batu Penjuru” Orphanage in Kulonprogo as an information Media. This website is a good solution to introduce this orphanage to around of the world, especially in indonesia. This Website is made using Adobe Dreamweaver CS6, PHP coding and MySQL database. In this research, The Software Development use Waterfall Model. The first step to design this website is make user need analysis, both of user and administrator. The next step is makes the design of software by design the interface view. After that, design the database using Entity Relationship Diagram and Logical Relational Structure. The conclusion of this research is the website can become an efficient information media to introduces ”Batu Penjuru” Orphanage at Kulonprogo, Yogyakarta. Area of spreading information can become more wide and this website can become reference for all of people, especially for donatur that want to donate .

Entity-Relationship (ER) diagrams are widely used in software engineering to model relational databases and serve as semantic representations easily understood by humans. They convey the meaning of data, their relationships, and key modeling concepts. Despite their usefulness, designing ER diagrams requires technical expertise. This work proposes a prototype leveraging natural language processing tools, particularly large language models (LLMs), to simplify and democratize their creation. Using simple prompts, the system generates structured outputs in standard formats that can later be used for ER diagram construction. As a result, a web application was developed, offering a user-friendly interface that reduces time and effort, aiming to make diagram creation more accessible.

XML data update management in XML-enabled database

As XML data storage and interchange become ubiquitous, analysts and data engineers increasingly need tools to model their data and map it to XML schemas and to reverse engineer XML documents and schemas in support of evolution and integration activities. For effective data management, model transformations require guarantees of properties of interest including guarantees of information and constraintpreservation, redundancy-free and compactness guarantees, and assurances about readability and maintainability. In this paper, we make foundational observations about XML data management, including conceptual modeling for XML data, transformations to and from XML Schema and XML data models, and transformation guarantees concerning properties of interest, and we provide resolutions for conceptual mismatches between XML data management and more traditional data management. Our implemented prototype tools show that these observations and insights can provide a strong foundation for XML data engineering.