Database Design Methodology Research Articles

Logical object structure and system implementation for BIM database in civil infrastructures

ABSTRACT Building Information Modeling (BIM) has attracted much attention as a vital information method in civil engineering. BIM data research has become increasingly important with the continuous understanding of BIM. The database designed especially for storing BIM data (IFC data) is called a BIM database. To realize centralized storage and sharing of complex building information, how to design and develop a BIM database will be a hot topic. However, the BIM database designed using an existing logical model (such as a relational model) is unsuitable for storing and managing a large amount of BIM data. To this end, we propose a database logical model for BIM database development called ‘logical object structure’. Based on the database design methodology, the logical schema of the BIM database is discussed, and five relation forms are established to describe the feature of engineering information. According to the relation forms, the logical object structure is presented, and the corresponding system implementation process is discussed. Finally, four workloads are set to test the logical object structure. The results show that the logical object structure can well support interactive behaviors of BIM data and provide good performance for the BIM database.

Designing and Implementing a Database for Thesis Data Management by Using the Python Flask Framework

This study aims to implement the database design used in thesis data processing using Flask. The results of the database design produce four tables, namely the lecturer table is used to store lecturer data, the student table is used to store student data, the title of thesis table is used to store data related to student thesis and the guidance table contains history during guidance with the supervisor, The design of the thesis data processing database was developed using Flask. Flask is a web framework written in Python. Flask serves as the application framework and the interface of the web-based flask application. In this research, the methodology used is to implement database development which consists of system analysis, logical design, physical design and implementation. The database design methodology is carried out by 1. Building a local conceptual data design based on user views, 2. Building and validating local logical data models, 3. Building and validating logical data models, 4. Translating logical data models for the database management system, 5. Designing and implementation of physical representation. The results show that the process of creating a thesis data management database can be done using the Flask framework. The development process using the flask framework includes the process of creating databases, tables and reading, adding, repairing and deleting data. In making the application, the application is divided into 2, namely the application used for database management and the application used to display website-based results that are used to display the results of data processing from the application. Implementation of data structures in the database design and applications used include programming language: Python 3.7.0, framework for displaying web-based data: Flask 1.1.2, and database management system using SQLite.

BrModelo: An Initiative for Aiding Database Design

The brModelo tool is a initiative of the UFSC Database Group. Its first version was developed in 2005, and its main purpose is to help teaching of relational database design. Compared to similar tools, its main differentials are the support to all steps of the classical database design methodology, user interaction during the logical design step, as well as the support to all extended Entity-Relationship concepts. With more than fifteen years of existence, the brModelo was very well-accepted by the brazilian Database community, which motivated the development and release of several versions of the tool. This article presents the history of brModelo, including its available versions and their functionalities. Additionally, we detail its functionalities and compare it with popular related tools.

A Unified Conceptual Model for Data Warehouses

These days, NoSQL (Not only SQL) databases are being used as a deployment tool for Data Warehouses (DW) due to its support for dynamic and scalable data modeling capabilities. Yet, decision-makers have faced several challenges to accept it as a major choice for implementation of their DW. The most significant one among those challenges is a lack of common conceptual model and a systematic design methodology for different NoSQL databases. The objective of this paper is to resolve these challenges by proposing an ontology based formal conceptual model for NoSQL based DWs. These proposed concepts are capable of realizing the cube concepts for visualization of multi-dimensional data in NoSQL based DW solutions. In this context, two strategies are specified, implemented and illustrated using a case study for devising of the proposed conceptual model.

Data modeling in the NoSQL world

NoSQL systems have gained their popularity for many reasons, including the flexibility they provide in organizing data, as they relax the rigidity provided by the relational model and by the other structured models. This flexibility and the heterogeneity that has emerged in the area have led to a little use of traditional modeling techniques, as opposed to what has happened with databases for decades.In this paper, we argue how traditional notions related to data modeling can be useful in this context as well. Specifically, we propose NoAM (NoSQL Abstract Model), a novel abstract data model for NoSQL databases, which exploits the commonalities of various NoSQL systems. We also propose a database design methodology for NoSQL systems based on NoAM, with initial activities that are independent of the specific target system. NoAM is used to specify a system-independent representation of the application data and, then, this intermediate representation can be implemented in target NoSQL databases, taking into account their specific features. Overall, the methodology aims at supporting scalability, performance, and consistency, as needed by next-generation web applications.

Design and Establishment of Database on the AtoN Properties for AtoN Simulator

This study investigated the design and establishment of AtoN(Aids to Navigation) in the AtoN Simulator. In recent years, IALA(International Association of Lighthouse Authorities) has raised the need of a system which could verify whether AtoN is appropriate for the design of AtoN and placement planning. An AtoN Simulator provides simulation circumstances, including the topographical and environmental characteristics of a primary harbor and the characteristics of a navigating ship and the maritime traffic. In the present study, we have developed an AtoN simulator system, including the integrated system design and the construction of an AtoN database. The AtoN Manager was developed as a virtual AtoN to manage the AtoN simulation. However, the data and materials are difficult to manage. Hence, an AtoN Manager and an AtoN simulation system have been needed for an effective managing of the AtoN properties database data. For the database structure design, we have analyzed the database design methodology. The AtoN properties have been analyzed for the effective data management. The AtoN properties designed in the present paper were classified into 19 categories. The status and properties database of AtoN were installed in 14 major ports, those were applied to the AtoN Manager. Designing the AtoN properties database was defined to reduce confusion of the use of English terms and abbreviations. The terms and acronyms have been defined in the AtoN properties and designed to the properties database structure for each AtoN. Before structuring the database for the AtoN Manager, the data of the AtoN properties for each harbor have been organized in accordance with the Excel system. The regulated data were converted into the AtoN properties database in use for the AtoN Manager. The database based on the AtoN properties table structure to each AtoN was designed. The AtoN simulator was implemented by the AtoN Manager applied to the AtoN properties database.

Database Design of Roadside Parking Toll Collection System

Database design methodology as the core of system design is brought forward combining the application environment and business processes of parking toll collection. Then the four stages of the parking toll collection system design are analyzed. They are the requirement analysis, conception framework design, logic framework design and physical framework design respectively. Through scheming out an optimum database mode applied to all kinds of parking toll collection system, the proposed system is able to collect parking fees based on PDA and manage the real-time information of parking lots.

γ-DB

In view of the paradigm shift that makes science ever more data-driven, we consider deterministic scientific hypotheses as uncertain data. This vision comprises a probabilistic database (p-DB) design methodology for the systematic construction and management of U-relational hypothesis DBs, viz., γ-DBs. It introduces hypothesis management as a promising new class of applications for p-DBs. We illustrate the potential of γ-DB as a tool for deep predictive analytics.

Design Methodology for Relational Databases : Issues Related to Ternary Relationships in Entitiy-Relationship Model and Higher Normal Forms

Entity-Relationship (ER) modeling plays a major role in relational database design. The data requirements are conceptualized using an ER model and then transformed to relations. If the requirements are well understood by the designer and then if the ER model is modeled and transformed to relations, the resultant relations will be normalized. However the choice of modeling relationships between entities with appropriate degree and cardinality ratio has a very severe impact on database design. In this paper, we focus on the issues related to modeling binary relationships, ternary relationships, decomposing ternary relationships to binary equivalents and transforming the same to relations. The impact of applying higher normal forms to relations with composite keys is analyzed. We have also proposed a methodology which database designers must follow during each phase of database design.

안전한 데이터베이스 설계를 위한 객체지향 분석·설계 방법론 -역할기반 접근제어를 중심으로-

In accordance with the advancement of IT, application systems with various and complex functions are being required. Such application systems are typically built based on database in order to manage data efficiently. But most object-oriented analysis design methodologies for developing web application systems have not been providing interconnections with the database. Since the requirements regarding the security issues increased, the importance of security has become emphasized. However, since the security is usually considered at the last step of development, it is difficult to apply the security during the whole process of system development, from the requirement analysis to implementation. Therefore, this paper suggests an object-oriented analysis and design methodology for secure database design from the requirement analysis to implementation. This object-oriented analysis and design methodology for secure database design offers correlations with database that most existing object-oriented analysis and design methodologies could not provide. It also uses UMLsec, the modeling language, to apply security into database design. In addition, in order to implement security, RBAC (Role Based Access Control) of relational database is used.

Formal approach for reengineering fuzzy XML in fuzzy object-oriented databases

Since semi-structured documents (e.g., XML) could benefit greatly from database support and more specifically from object-oriented (OO) database management systems, we study the methodology of reengineering XML to object-oriented databases when database migration occurs in this paper. In particular, considering the need of processing the imprecise and uncertain information existing in practical applications, we investigate the problem of migrating fuzzy XML to fuzzy object-oriented databases. To find the object-oriented schema that best describes the existing fuzzy XML schema (DTD), we devise a comprehensive approach centering on a set of mapping rules. Such reengineering practices could not only provide a significant consolidation of the interoperability between fuzzy OO and fuzzy XML modeling techniques, but also develop the practical design methodology for fuzzy OO databases.

관계형 데이터베이스 응용시스템을 위한 통합 설계방법론 개발 -객체지향 분석.설계 방법론을 중심으로-

본 논문에서는 UML(Unified Modeling Language)을 토대로 유스케이스(use case) 중심의 객체지향 분석 설계 방법론을 기반으로 한, 관계형 데이터베이스 통합 설계방법론에 대하여 다룬다. 본 통합 설계방법론에서 사용하는 개념모델은 비즈니스 프로화일(business profile)에 기반을 두고 있으며, 6단계로 구성되어 있다. 첫 번째 단계에서는 비즈니스 유스케이스(business use case)가 식별되어 마크로액티비티 다이어그램(macroactivity diagram)으로 표현되고, 두 번째 단계에서 마크로액티비티 다이어그램은 비즈니스 객체(business object)와 비즈니스 객체흐름(business object flow) 그리고 비즈니스 사용자책임(business worker's responsibilities)을 이용하여 상세 비즈니스 활동다이어그램(detailed business activity diagram)으로 변환된다. 세 번째 단계에서는 상세 비즈니스 활동다이어그램을 기반으로 시스템 전체의 정적 구조를 설명하는 비즈니스 클래스다이어그램(business class diagram)으로 변환된다. 네 번째 단계에서 비즈니스 클래스다이어그램은 대응하는 관계형 데이터베이스 초기 개념모델을 대표하는 클래스다이어그램으로 변환된다. 다섯 번째 단계에서 클래스다이어그램에 일반화와 특수화, 역할과 활동, 클래스 추가 그리고 중복 연관에 따른 추가적인 변환이 이루어지고, 마지막으로 관계형 데이터베이스 스키마로 변환이 이루어지게 된다. 본 논문에서 제시하는 방법론을 적용함으로써, 객체지향 분석 설계 방법론과 관계형 데이터베이스 설계방법론 사이에 유기적 연결이 이루어지게 되어, 객체지향 분석 설계 방법론 관계형 데이터베이스설계 방법론을 통합적으로 다룰 수 있게 된다. 이에따라 관계형 데이터베이스 기반의소프트웨어 시스템에 대한 객체지향 방식의 일관된 그리고 통합된 구축방안이 제공된다. 사례 연구로 제안한 통합 설계 방법론을 비자발급시스템에 대하여 적용한다. In this paper we present an integrated design methodology for relational database based on object-oriented analysis and design. The integrated design methodology is based on business profile and has six phases. In the first phase, business use cases are identified and described by macroactivity diagrams and then the macroactivity diagrams are transformed to detailed business activity diagrams by using objects, object flows and business worker's responsibilities. In the third phase, the detailed business activity diagrams are transformed to business class diagrams that describe the static structure of the entire business system based on detailed business activity diagrams. In the four phase, the business class diagrams are transformed to class diagrams that represent the initial conceptual model of the target relational database. In the five phase, we add additional transformations on the class diagrams with generalization and specialization of associations, roles, activities, additional classes and redundant associations. Eventually, the final class diagrams are transformed to relational database schema. The methodology presented in this paper by applying that proposal for organic connection between object-oriented analysis and design methodology and relational database design methodology. And it will be able to deal with integration management. By the integrated design methodology, we can make more easily software systems based on relational database. In the case study, proposal integrated design methodology applied for a visa issuing system.

Study on the Normalization for Internet Computing and Modeling of Conceptual Model XML-Based

This document explains and demonstrates on the Normalization for Internet computing and Modeling of Conceptual Model XML-based. The existing XML conceptual models have their limitation, largely because the semantic, such as “containment” and “multiple-scope”, could not be sufficiently described. XUML is a XML conceptual model based on UML. It is independent of specific XML schema definition language, and puts emphasis on describing relationships between domain concepts and defining related semantic constrains. XML normalization theory is recently a research focus, but the existing research outcomes are very complex so they are hard to be understood by XML designers. The development of database design methodology reveals that it is more effective to apply normalization theory in conceptual design than that in logical design. By following the successful approach, the characteristics of XML normal form are represented in XUML. Several XUML forms are defined, and the normalization based on XUML is investigated. The research on XML normalization theory further enhances XUML methodology. So we show the process of XML normalization in XML conceptual model in the paper. And several normalization methods are introduced. Finally, an example is presented to explain the general application of XML normalization methods.

SISRO, conception de bases de données à partir d'ontologies de domaine

Database design methodologies require both good modelling capabilities and knowledge of the field to be modelled. The first aspect is a one of the major difficulties for designers, since they have to move from one field to another one. Moreover, resulting databases are heterogeneous and difficult to integrate. In this paper, we propose a database design methodology, called SISRO. It is based on a prior definition of a local ontology for the database to be designed. This ontology is defined by specialization of shared domain ontologies, selective import of properties, and eventually extension with necessary concepts and/ or properties. The conceptual model is defined as a fragment of local ontology. Representing both ontologies and their articulations in the resulting database provides easy access, exchange and integration of data.

Ultra-Structure database design methodology for managing systems biology data and analyses

BackgroundModern, high-throughput biological experiments generate copious, heterogeneous, interconnected data sets. Research is dynamic, with frequently changing protocols, techniques, instruments, and file formats. Because of these factors, systems designed to manage and integrate modern biological data sets often end up as large, unwieldy databases that become difficult to maintain or evolve. The novel rule-based approach of the Ultra-Structure design methodology presents a potential solution to this problem. By representing both data and processes as formal rules within a database, an Ultra-Structure system constitutes a flexible framework that enables users to explicitly store domain knowledge in both a machine- and human-readable form. End users themselves can change the system's capabilities without programmer intervention, simply by altering database contents; no computer code or schemas need be modified. This provides flexibility in adapting to change, and allows integration of disparate, heterogenous data sets within a small core set of database tables, facilitating joint analysis and visualization without becoming unwieldy. Here, we examine the application of Ultra-Structure to our ongoing research program for the integration of large proteomic and genomic data sets (proteogenomic mapping).ResultsWe transitioned our proteogenomic mapping information system from a traditional entity-relationship design to one based on Ultra-Structure. Our system integrates tandem mass spectrum data, genomic annotation sets, and spectrum/peptide mappings, all within a small, general framework implemented within a standard relational database system. General software procedures driven by user-modifiable rules can perform tasks such as logical deduction and location-based computations. The system is not tied specifically to proteogenomic research, but is rather designed to accommodate virtually any kind of biological research.ConclusionWe find Ultra-Structure offers substantial benefits for biological information systems, the largest being the integration of diverse information sources into a common framework. This facilitates systems biology research by integrating data from disparate high-throughput techniques. It also enables us to readily incorporate new data types, sources, and domain knowledge with no change to the database structure or associated computer code. Ultra-Structure may be a significant step towards solving the hard problem of data management and integration in the systems biology era.

Ultra-Structure database design methodology for managing systems biology data and analyses

Ultra-Structure database design methodology for managing systems biology data and analyses

MAD skills

As massive data acquisition and storage becomes increasingly affordable, a wide variety of enterprises are employing statisticians to engage in sophisticated data analysis. In this paper we highlight the emerging practice of Magnetic, Agile, Deep (MAD) data analysis as a radical departure from traditional Enterprise Data Warehouses and Business Intelligence. We present our design philosophy, techniques and experience providing MAD analytics for one of the world's largest advertising networks at Fox Audience Network, using the Greenplum parallel database system. We describe database design methodologies that support the agile working style of analysts in these settings. We present dataparallel algorithms for sophisticated statistical techniques, with a focus on density methods. Finally, we reflect on database system features that enable agile design and flexible algorithm development using both SQL and MapReduce interfaces over a variety of storage mechanisms.

Six methodological steps to build medical data warehouses for research

Purpose We propose a simple methodology for heterogeneous data collection and central repository-style database design in healthcare. Our method can be used with or without other software development frameworks, and we argue that its application can save a relevant amount of implementation effort. Also, we believe that the method can be used in other fields of research, especially those that have a strong interdisciplinary nature. Background The idea emerged during a healthcare research project, which consisted among others in grouping information from heterogeneous and distributed information sources. We developed this methodology by the lessons learned when we had to build a data repository, containing information about elderly patients flows in the UK's long-term care system (LTC). Design We explain thoroughly those aspects that influenced the methodology building. The methodology is defined by six steps, which can be aligned with various iterative development frameworks. We describe here the alignment of our methodology with the RUP (rational unified process) framework. The methodology emphasizes current trends, as early identification of critical requirements, data modelling, close and timely interaction with users and stakeholders, ontology building, quality management, and exception handling. Results Of a special interest is the ontological engineering aspect, which had the effects with the highest impact after the project. That is, it helped stakeholders to perform better collaborative negotiations that brought better solutions for the overall system investigated. An insight into the problems faced by others helps to lead the negotiators to win-win situations. We consider that this should be the social result of any project that collects data for better decision making that leads finally to enhanced global outcomes.

Denormalization strategies for data retrieval from data warehouses

In this study, the effects of denormalization on relational database system performance are discussed in the context of using denormalization strategies as a database design methodology for data warehouses. Four prevalent denormalization strategies have been identified and examined under various scenarios to illustrate the conditions where they are most effective. The relational algebra, query trees, and join cost function are used to examine the effect on the performance of relational systems. The guidelines and analysis provided are sufficiently general and they can be applicable to a variety of databases, in particular to data warehouse implementations, for decision support systems.

On augmenting database design-support environments to capture the geo-spatio-temporal data semantics

A database design-support environment supports a data analyst in eliciting, articulating, specifying and validating data-related requirements. Extant design-support environments—based on conventional conceptual models—do not adequately support applications that need to organize data based on time (e.g., accounting, portfolio management, personnel management) and/or space (e.g., facility management, transportation, logistics). For geo-spatio-temporal applications, it is left to database designers to discover, design and implement—on an ad-hoc basis—the temporal and geospatial concepts that they need to represent the miniworld. To elicit the geo-spatio-temporal data semantics, we characterize guiding principles for augmenting the conventional conceptual database design approach, present our annotation-based approach, and illustrate how our proposed approach can be instantiated via a proof-of-concept prototype. Via a proof-of-concept database design-support environment, we exemplify our annotation-based approach, and show how segregating “what” from “when/where” via annotations satisfies ontologic- and cognition-based requirements, dovetails with existing database design methodologies, results in upward-compatible conceptual as well as XML schemas, and provides a straightforward mechanism to extend extant design-support environments.