On Pattern-Based Database Design and Implementation

The introduction in the educational process of database design CASEtechnologies requires the institution of significant costs for the purchase of software. A possible solution could be the use of free software peers. At the same time this kind of substitution should be based on even-com representation of the functional characteristics and features of operation of these programs. The purpose of the article – a review of the free and non-profi t CASE-tools database design, as well as their classifi cation on the basis of the analysis functionality. When writing this article were used materials from the offi cial websites of the tool developers. Evaluation of the functional characteristics of CASEtools for database design made exclusively empirically with the direct work with software products. Analysis functionality of tools allow you to distinguish the two categories CASE-tools database design. The first category includes systems with a basic set of features and tools. The most important basic functions of these systems are: management connections to database servers, visual tools to create and modify database objects (tables, views, triggers, procedures), the ability to enter and edit data in table mode, user and privilege management tools, editor SQL-code, means export/import data. CASE-system related to the first category can be used to design and develop simple databases, data management, as well as a means of administration server database. A distinctive feature of the second category of CASE-tools for database design (full-featured systems) is the presence of visual designer, allowing to carry out the construction of the database model and automatic creation of the database on the server based on this model. CASE-system related to this categories can be used for the design and development of databases of any structural complexity, as well as a database server administration tool. The article concluded that the qualitative training of specialists in the field of information technology is impossible without an understanding of the students of the principles of construction of the database, practical development of modern methods of design and development database. Instrumental basis of database design information technology are modern CASE-tools. Today, on the software market presented a large number of commercial CASE-systems database design, which differ in their characteristics. The limiting factor is widely used in the Russian universities CASE-technologies database design is the high cost of the software. We have in its review of the free and non-profi t CASE-tools database design, their systematization to help teachers and students in the choice of available tools design and development database.

In this paper, we discuss some design principles that will aid in the design and querying of multimedia databases. We use an object-relational data model and argue that multimedia objects should normally have a special attribute called ‘core’ which stores the real object itself in contrast to the abstraction which is reflected in the rest of the attributes. We present an extension to the ER Diagram that takes advantage of the ‘core’ notion to facilitate design of multimedia databases. We discuss some desirable features in a query language for multimedia databases: simplifications like the use of path expressions and implicit use of functions (methods) as attributes, and explicit specification of the display layout and format either at the data definition level or query specification level. To materialize this last feature, we propose a display specification extension to SQL (SQL+D) that we have implemented.

The purpose of the study is to adapt the antipattern method to improve the effectiveness of teaching students in the fields of “Applied Informatics”, “Information Systems and Technologies”, “Software Engineering” to the principles and techniques of relational database design within the framework of relevant disciplines and practices. Training in database design is an important component of the formation of a specialist software developer. The totality of decisions taken in the design process should be based on generally accepted rules, principles and recommendations, as well as on the existing experience in creating and operating information systems, which is difficult to reproduce in the conditions of the university audience.Materials and methods. An approach focused on the concept of antipatterns – unsuccessful common design solutions will allow increasing the effectiveness of students’ training in database design. The antipattern concept has become widespread following the wide spread use of the concept of a pattern, that is, a common standard solution inscribed in the context of the problem being solved. Both the concept of a pattern and the concept of an antipattern were initially focused on object-oriented software, but later gained recognition in all areas of information technology. The paper proposes a scheme for describing the antipattern, includ ing the name, a brief description, possible causes of occurrence, a list of disadvantages of application in the construction of relational databases, a conceptual model in the form of an ER-diagram (entity-relationship diagram), an example of the appropriate database structure, ways to avoid antipatterns, as well as possible exceptions when using just such a design decision when creating a database may be justified.Research results. Based on educational, scientific and technical literature and periodicals, as well as on the basis of an analysis of the existing practice of designing information systems, a catalog of common antipatterns for designing relational databases has been compiled and described. Examples of antipatterns: “Jumble of names”, “Duplicate tables”, “False abstraction”, “Non-atomic attributes”, “Duplicate columns”, “Changing data in due course (temporaryfields)”, “Parallel connections”, ““Divine” table”, “Speculative metadata modification”, etc. At the same time, some of the patterns made it possible to illustrate the general principles of relational database design, for example, such as “No sophisticated programming is capable of correcting fatal architectural flaws”. It is shown that the existing unsuccessful solutions are often due to certain prerequisites, for example, the need to perform a hotfix that is, a “temporary” solution, or a premature attempt to improve system performance, or the desire to get some report with one request, avoiding unnecessary connections, etc. In addition to the technical aspects, the relevance of a correct and uniform naming system is shown, the absence of which makes it difficult to maintain and develop the system and leads to unnecessary costs. The proposed approach was tested when teaching students the disciplines “Databases”, “Database design”, “Architecture of information systems”. The students who completed the training improved their understanding of the principles and practices of database structure design. Conclusion. The use of the proposed catalog of antipatterns in the educational process of the university makes it possible to accelerate the training of young specialists in the techniques of designing the structure of relational databases, avoid common mistakes when creating information systems, and improve the overall design culture.

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.

This study aims to produce a user interface for scientific work repository information systems that are useful for facilitating the Baiturahmah Nursing Academy in searching for scientific work references online. Scientific works are scientific essays that present general facts and are written according to the correct writing methodology and the truth can be proven, the opinions in scientific works are always accompanied by supporting evidence, for that the process of storing scientific works can be arranged in a structured manner. The management of scientific works from the Baiturrahmah Nursing Academy community is currently still manual, the process to access scientific works is done by borrowing directly from the library. The method used in this research is the Waterfall Model System Development Life Cycle (SDLC) and system design tools using the UML model. While the programming language and database design used the PHP programming language and MySQL database. The results of this study are a scientific work repository application that can be accessed online which provides convenience in the process of storing scientific papers, making it easier for the Baiturrahmah Nursing Academy to find references for writing scientific papers.

The need for high-quality crumb rubber in West Sumatra tends to increase. However, the amount and quality of rubber from suppliers belong to weak caused by the bad monitoring systems, the supply cannot be met properly, and there is a lot of shrinkage in rubbers purchased by the company. Therefore this research was carried by implementing the Decision Support System (DSS) which was expected to help facilitate supplier data searches and evaluate the supplier's performance. The first stage in this research was designing DSS included the use of Unified Modeling Language (UML) diagram and database design. Next, built an applicable software using Personal Home Page (PHP), My Structured Query Language (MySQL), and Apache. An advantage of DSS designed was to accommodate differences and changes in rubber supplier assessment criteria according to the consideration of each crumb rubber industry in West Sumatra. There were 3 of 11 main crumb rubber criteria assessed. The results of these 3 criteria were obtained highest weight, namely Dryness (0.18), cleanliness (0.15), and consistency of quality (0.10). While the previous performance obtained the lowest weight (0.05). This meant that the criteria of dryness, cleanliness, and consistency of quality, will be the main considerations for companies in ranking and evaluating suppliers who work with companies.

Current database systems are often large and complex and the case that a user or an application has full access to the entire database is rare. It is more likely to occur that access is granted via windows of the entire systems, called views. A view, usually virtual, is defined by giving a query on the whole database and at any point the content of the view is just the outcome of this query. Applications query a base relation or a view in the same way. Therefore, querying a view does not represent a serious conceptual problem. In contrast, the issue of view updating is problematic and of paramount importance: it refers to the problem of translating an update request against a view into an update request involving the base of data. Over the years, a substantial amount of research has been devoted to the various issues surrounding view updating and not surprisingly a wide selection of approaches to the view update problem has evolved. See [2,3] for surveys of methods for view updating.

The control equipment management system is a kind of multimedia information management system that includes images, texts and database information. The most important thing for such a management system is the design of database. This paper first gives some aspects that should be paid attention to in the process of designing database. Then it makes a detailed design for the control equipment management system database forms the following aspects: the conceptual structure design of the database, the logical structure design of the database, and the physical structure design of the database. The actual operation results of the system show that the design of the database has obtained good results.

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.

To utilize database management systems, a database designer must construct a schema, which is used to validate the data stored and help set up efficient access structures. Because database design is an art, and because the real world is irregular, unpredictable, and evolves, truly useful database systems must be tolerant of occasional deviations from the constraints imposed by the schema, including so-called “semantic integrity constraints,” which are first-order assertions about consistent database states. For example, the integrity constraint

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

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

Detailed kinetic models are widely used in the field of combustion chemistry for the design and development of combustors, engines, fuels, and additives. Due to the proliferation of models and the increasingamount of data encapsulated within each model, ambiguities, discrepancies, and mistakes are ever present, leading to incorrect scientific conclusions and inaccurate predictions. Significant efforts have been made to improve the quality of published kinetic models via semi-automated cross-referencing tools, but there remains a need for the consolidation of models in a medium that supports their continued analysis, use, revision, and overall contribution. The relationships between resonance structures, isomers, species, species names, thermochemical parameters, chemical reactions, reaction rate expressions, and metadata, are complex, especially when many of these are re-used across different kinetic models. A Structured Query Language (SQL) database schema paired with a web application and RESTful API, implemented in a Python-based web framework, is proposed to store detailed kinetic models and expose a rich interface for data analysis, model comparison, and data contribution, all within a readable, extensible, and maintainable code base appropriate for an academic research setting.--Author's abstract