An Analytical and Empirical Comparison of End-User Logical Database Design Methods

The trend of producing databases which do not satisfy organizational requirements can be attributed to the fact that the database designer is required to simultaneously consider many design constraints and does not have a comprehensive methodology to follow. A new decomposition of the logical database design process in which each level satisfies a single design objective is developed. In this decomposition, the requirements process and logical database design process are integrated to ensure that organizational requirements are satisfied. A structured logical database design methodology called LDDM that is based on this decomposition has been developed. LDDM consists of six design steps: Requirements Step, Entity Step, Relationship Step, Entity Structure Step, Refinement Step and DBMS Accommodation Step. LDDM including its constituent steps and techniques is presented. The utilization of LDDM will result in increased designer productivity, better documentation and a high quality logical database.

The two stages of database design are logical and physical design. Logical database design, also referred to as , is done first. It is the process of studying the workings of a business organization, constructing a set of tables to store the business data, and understanding the constraints on the data, the dependencies between the tables, and the business rules concerning the data. The logical database design process is conducted without reference to any specific database technology such as Oracle or Microsoft SQL Server. Tools such as SQL Developer Data Modeler and Toad Data Modeler can be used for the purpose. Physical database design follows logical database design. First, the logical model is mapped to the proprietary features of the chosen database technology. Security requirements, integrity requirements, and business rules are also implemented. Finally, you consider performance: the ability of the database engine to handle work requests efficiently. This typically involves the creation of indexes on the data, and Oracle Database provides a wealth of indexing mechanisms to choose from.

The author conducts research on data management in the Graha Kasih Nursing Home in Kubu Raya District, which is to find problems with data processing that still uses paper so that it is susceptible to errors in the data recording process and the risk of data loss is very large, making it difficult to access data. Therefore the author designed a Relational Database for elderly data at the Graha Kasih Nursing Home of Kubu Raya District to overcome the problem. The form of research used in this study uses a case study with R & D (Research and Development) method which is a descriptive method which is the initial method of R & D method to collect data about existing conditions. While the data collection techniques used are interviews, observation and documentation studies. The method of analysis and design used in this research is the Database Method of Life Cycle (DBLC), with the focus of the discussion including Conceptual Database Design, Logical Database design, and Physical Database Design. Flowchat is used to describe existing running systems, while the proposed system modeling and design uses UML (Unified Modeling Language). The design of this Relational Database is made with Visual Basic .NET programming language as its design tool and MYSQL as its database. The designed database resulted in an application that could help the Graha Kasih Nursing Home of Kubu Raya District to facilitate the management of occupants 'data, contribution data, data on residents' transfers, contributor data, donation data, and employee data, as well as minimizing the risk of data damage and data loss. , and facilitate the process of accessing data easily and quickly.

In this paper, we conceptually model an Entity Relationship (ER) diagram and Extended Entity Relationship (EER) diagram from XML Schema. This conceptual view of XML Schema is a necessary step in understanding XML data, and can easily be used to translate XML data to the relational model. Once in the relational model, XML data can avail of mature relational database technology.

The examples shown in Figs. 2 and 3 of [1] illustrate the existence of simple cycles in the data model between the department and the manager of each case. Such relations, which are cyclic on a one-to-one basis, are frequent, both in the conceptual construction of data models by users and in the implementation of a data base for multi-file systems. To indicate this simple equivalency, the relation (D, M) can be replaced by an equivalent single domain, say X . Because of the frequency of occurrence of binary one-to-one relations, I have termed such relations a lexicon [2]. On applying this simplification, the result of the analysis for minimum cover given in [1] is a single set of relations as follows: R1(E, X, JC) R2 (X, CT) X(D, M).

As database applications have become more sophisticated, the development of support tools for database design has become more critical. Before support tools can be developed, however, the nature of database design problems and their solutions must be well defined. We apply data modelling principles to these tasks. The result is a multi level model of databases. The logical level describes database design problems and the physical level describes their solutions. This model is the basis for a computer aided database design methodology developed by the authors.

It is argued that ontologically clear entity relationship models can model the real world domains more accurately than ontologically unclear models. However, transformation of such models into the relational model at the logical level has not yet been studied sufficiently with a view to formulate new transformation rules. This paper presents a set of new transformation rules to convert ontologically clear conceptual models to relational models. Finally we did a comparison of two relational models that were developed from the ontologically clear and unclear models using a quality criterion synthesized from the extant literature. The preliminary results of this ongoing research study shows that the quality of relational model developed from ontologically clear conceptual model is superior to its ontologically unclear counterpart.

Lilys Gallery is an online shop that specializes in fashion goods, but currently doesn't have a dedicated website. This limitation affects its market reach and branding efforts. To boost sales and enhance branding for the customers in Jayapura Papua, creating a website is essential. This research focuses on analyzing the design of “developing a web-based clothing sales application for Lilys Gallery”. Using the SDLC waterfall methodology, which includes phases of requirement analysis, system design, implementation, testing, deployment, and maintenance. The website is built using HTML, JavaScript, and PHP, and its structure is designed using UML diagrams, including such as use case diagrams, class diagrams and entity relationship diagrams with the logical database design. The research dives into the process and design of the website, emphasizing usability, user experience, and functionality. The results indicate that a well-crafted website can significantly increase sales, broaden market reach, and strengthen the brand presence of Lilys Gallery in the competitive online fashion market. Furthermore, the study underscores the importance of an integrated online platform for managing inventory, processing sales, and engaging with customers effectively, ensuring a seamless shopping experience and higher customer satisfaction.

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

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.

With the rapid development of network technology, music websites gradually become a popular, and the emergence of pop music website is to meet the people's strong demand for popular music, because database plays an important role in the design of website, studying the database design of pop music website development is important. From the conception of database design, firstly, this paper studies conceptual design for the database design, conceptual design is mainly reflected in the form of an E-R diagram; then conducted logical in the database design, logical design is expressed by the pattern of table structure; finally, studies the security design of database design, describes the security policy of database. The studied content of this paper plays a supporting role for popular music website design, promotes the combination of music and websites, and enriches people's leisure life.

Most universities where students study informational technologies and computer science have an introductory course dealing with the development and design of databases. These courses often include usage of database design tools. In this paper, the #EER tool is presented, the task of which is to make the process of relational databases design easier for the students and partially automatize it. The tool evolved due to the experience in using similar tools for educational purposes. It enables fast and efficient development of the relational database conceptual model and its automatized compilation into a relational model and further to data definition language (DDL) commands. #EER tool is based on the extended entity-relationship (EER) model for conceptual modeling of relational databases. Modular architecture of the tool, the development of which is based on the usage of the design patterns, along with the benefits that its usage brings, is also presented.

In the last four years we have implemented tools for various tasks associated with database design: logical design, physical design, and re-design. An integrated example is presented to review and illustrate the capabilities of these tools. Plans for integrating the tools themselves to provide a more complete and unified service to the database designer are also presented.

With the national efforts to increase investment for quality education and an increase in the number of college enrollment music class students, so the college needs more music equipments. The college always faces challenge of the comprehensive information management for music equipments. This paper bases on requirement analysis for warehouse management of music equipment to conduct database design. Requirement analysis uses UML to conduct use case modeling and describes management process; database design conducted conceptual design and logical design; conceptual design represents by E-R; logic design bases on convert rule to design and represents by ten table structure. Content of this paper is the basic work of software development and provides support for the development of warehouse management system of music equipment, will play an active role in promoting the construction of college music equipment management information.

Extending classical functional dependencies for physical database design