Database Design Methodology Research Articles

Conceptual database evolution through learning in object databases

Changes to the conceptual structure (meta-data) of a database are common in many application environments and are in general inadequately supported by existing database systems. An approach to supporting such meta-data evolution in a simple, extensible, object database environment is presented. Machine learning techniques are the basis for a cooperative user/system database design and evolution methodology. An experimental end-user database evolution tool based on this approach has been designed and implemented. >

Materialization [database design

A new data abstraction, called Materialization, is introduced to model a situation that occurs frequently in the real world and has important implications for database design. Materialization is the relationship between two entity types, one that represents a conceptual object, for example, a TV Model, and one that represents its corresponding concrete objects, in this case, actual TV Sets. The Materialization construct is formally defined and contrasted with other well-known data abstractions. Its design implications are presented in terms of the entity-relationship model and its translation into a relational model. Guidelines are offered for the proper employment of this relationship in database design methodologies, and a discussion is provided of why this constitutes an important data modeling construct. >

Physical database design

Methods and techniques are available for helping the system development effort at the analysis and logical design stages. Yet, once the system has been defined, the designer is left with many decisions that will affect the construction, operation and maintenance stages. This article proposes a conceptual model to support the database designer at the physical design stage. The model incorporates database design methodology with decision support system (DSS) methods. A prototype version of the model is described, together with an analysis of a case study. Such a model may be integrated into a CASE methodology to encompass the entire information system development cycle.

A methodology and tool for top-down relational database design

This paper presents a methodology for logical design of relational schemas and integrity constraints using semantic binary schemas. This is a top-down methodology. In this methodology, a conceptual description of an enterprise is designed using a semantic binary model. Then, this description is converted into the relational database design. The paper also describes a tool which automates all the busy work of the methodology and provides graphic output. With respect to the intelligent design decisions, the tool accepts instructions from its user, who is a database designer, or, when the user defaults, makes decisions itself based on ‘rule-of-thumb’ principles.

Foundations of entity-relationship modeling

Database design methodologies should facilitate database modeling, effectively support database processing, and transform a conceptual schema of the database to a high-performance database schema in the model of the corresponding DBMS. The Entity-Relationship Model is extended to theHigher-orderEntity-RelationshipModel (HERM) which can be used as a high-level, simple and comprehensive database design model for the complete database information on the structure, operations, static and dynamic semantics. The model has the expressive power of semantic models and possesses the simplicity of the entity-relationship model. The paper shows that the model has a well-founded semantics. Several semantical constraints are considered for this model.

M ∗-object: An object-oriented database design methodology for CIM information systems : A. Di Leva, P. Giolito, F. Vernadat, pp 183–187

M ∗-object: An object-oriented database design methodology for CIM information systems : A. Di Leva, P. Giolito, F. Vernadat, pp 183–187

M∗-object: An object-oriented database design methodology for CIM information systems

M∗ is an information system design and analysis methodology developed for CIM environments. It is based on the PDN (Process and Data Net) model. In this paper, an object-oriented extension of M∗ for the design of information systems in CIM applications is presented. The architecture of the M∗ methodology and its organisation model are first presented. Then, the Process and Data Net model used for conceptual design of the CIM system database is discussed. This model is based on an object-oriented (OO) data model and a predicate/transition (PrT) Petri net model. It is used to describe the properties and behaviour of the objects of the CIM information system. A flexible manufacturing cell (FMC) example is given.

Usage refinement for ER-to-relation design transformations

Database schema refinement based on usage is proposed as a useful next step in a practical database design methodology founded upon entity-relationship (ER) conceptual modeling and transformation to normalized relations. A simple cost model is defined and applied to several examples and a case study, illustrating the important trade-offs among query and update costs, storage requirements, and degree of normalization with its data integrity implications.

Achieving and measuring flexibility in project information retrieval

Because of the diversity of people, organizations and activities involved in the management of construction, there is a need for great flexibility in the way in which project information can he presented. This paper describes how relational database technology can be used with integrated database design methodology to develop a flexible means of information retrieval. An implementation of a database of this type, for the purposes of research, has used project data from a real life project. The testing of the database has been of its ability to enable flexible information retrieval. The results show a significant improvement inflexibility measured on an ordinal scale. The paper thus shows how to gain greater flexibility in information retrieval for basic retrieval forms. It also presents a methodology by which flexibility can be measured and compared. It concludes by speculating on the consequences of extrapolating the results of the study to more complex forms of information retrieval.

On a human-centred approach to database systems

It is often illuminating to view a technology or a methodology from a novel perspective, thereby assessing it with criteria which are likely to differ markedly from those used by its designers. In this paper we review current database design methodology and, implicitly, database technology. We attempt to show that both are founded on an information-centred philosophy, and that the consequences of this view are significant and unsatisfactory. We investigate an alternative, human-centred philosophy and relate this to the more limited scope of a user-centred view which evolves from our analysis.

Descriptive specification of database object behaviour

Traditional database design methodologies are not appropriate for the specific requirements of object-oriented database systems and new database application areas. Apart from semantic complications arising from object-oriented database structures with complex objects, arbitrary data types as attribute domains, or generalization hierarchies, specification and semantics of dynamic database behaviour has to be of main interest for typical object-oriented applications, too. We propose the use of a temporal logic as a specification language for dynamic object behaviour and point out the formal semantics of such database dynamics specifications. A layered conceptual database design methodology is presented together with a discussion on design support techniques for behaviour specifications. Finally, implementation aspects are treated.

An integrated methodology for functional analysis, process design and database design

A methodology that combines and integrates the major stages of information systems development is presented. The methodology is based on hierarchical data-flow diagrams which are used to perform a functional analysis of the system. This enables the conducting of process design on the one hand, and information structure analysis and database schema design on the other. Specifically, we describe a method that connects the transactions of the system (the product of the process design stage) with the record-types (the product of database design stage). This connection closes the gap between the “procedural” and “structural” aspects of the system, and enables a smooth transition to the stage of system construction. It also facilitates the designing of sub-systems and their sub-schemas. Software tools that support all stages of the methodology are reviewed, emphasizing the tool DS2DS that connects the transactions with the record-types.

Need for “flexibility” in a conceptual model

The translation of one data model into another has become necessary. Database design methodologies stipulate that a conceptual model should be created prior to implementing a new database system. It is then, usually, the translation of this conceptual model into the physical model of a commercial database management system (DBMS) that is a necessity (e.g., The translation of the entity-relationship model into a relational DBMS). However, more and more we are seeing the translation of the data models in currently implemented conventional file and database systems into conceptual models (e.g., The translation of an ORACLE DBMS into an entity-relationship model). It is the conceptual model that is produced from the ‘reverse’ translation process that we address here; however, the ideas of flexibility can be applied to new database designs also. Since several different reverse translation algorithms have been developed, the questions that arise are: How do we know the resulting conceptual models are accurate? Does the resulting model contain enough information to be useful to database designers and which one is easier for the database designer to work with and to use as a communication tool with users or to develop new databases? The problem is that resulting conceptual data models from two different algorithms may differ even in the data objects obtained, and yet both be equivalent to the original model.

Database organization strategies for spatial decision support systems

Abstract The selection of a data model is an important step in designing a spatial decision support system (SDSS) because the database is the foundation of the system, and other system components must draw upon the database to perform analysis and display functions. The diversity of representations that must be maintained to support these functions often results in a complex database. One way to simplify the implementation of a complex database is to exploit features of a data model embedded in database management software. A methodology for SDSS conceptual database design was developed using the Entity-Category-Relationship approach. To accommodate this conceptual structure in database management software, we reviewed available data models and concluded that the hybrid extended network model is appropriate for use in an SDSS context. To illustrate this methodology, we designed a logical database structure for a locational analysis SDSS.

A generalized expert system for database design

Generalized Expert System for Database Design (GESDD) is a compound expert system made up of two parts: (1) an expert system for generating methodologies for database design, called ESGM; and (2) an expert system for database design, called ESDD. ESGM provides a tool for the database design expert to specify different design methodologies or to modify existing ones. The database designer uses ESDD in conjunction with one of these methodologies to design a database starting from the requirement specification phase and producing a logical schema in one of the well-known data models, namely, the hierarchical data model, the network data model, or the relational data model. The system is evolutive in the sense that an existing methodology can be modified or a novel methodology can be added to the existing ones. GESDD is a menu-driven system and it is coded in Prolog.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

Distributed database design methodologies

This paper surveys methodological approaches for distributed database design. The design of distribution can be performed top-down or bottom-up; the first approach is typical of a distributed database developed from scratch, while the second approach is typical of the development of a multi-database as the aggregation of existing databases. We review the design problems and methodologies along both directions, and we describe DATAID-D, a top-down methodology for distribution design. We indicate how the methodology is part of a global approach to database design; how to collect the requirements about the distribution of data and applications; and how to progressively build the distribution of a schema. Our approach is exemplified through one case study.

A comparative analysis of methodologies for database schema integration

One of the fundamental principles of the database approach is that a database allows a nonredundant, unified representation of all data managed in an organization. This is achieved only when methodologies are available to support integration across organizational and application boundaries. Methodologies for database design usually perform the design activity by separately producing several schemas, representing parts of the application, which are subsequently merged. Database schema integration is the activity of integrating the schemas of existing or proposed databases into a global, unified schema. The aim of the paper is to provide first a unifying framework for the problem of schema integration, then a comparative review of the work done thus far in this area. Such a framework, with the associated analysis of the existing approaches, provides a basis for identifying strengths and weaknesses of individual methodologies, as well as general guidelines for future improvements and extensions.

A logical design methodology for relational databases using the extended entity-relationship model

A database design methodology is defined for the design of large relational databases. First, the data requirements are conceptualized using an extended entity-relationship model, with the extensions being additional semantics such as ternary relationships, optional relationships, and the generalization abstraction. The extended entity-relationship model is then decomposed according to a set of basic entity-relationship constructs, and these are transformed into candidate relations. A set of basic transformations has been developed for the three types of relations: entity relations, extended entity relations, and relationship relations. Candidate relations are further analyzed and modified to attain the highest degree of normalization desired. The methodology produces database designs that are not only accurate representations of reality, but flexible enough to accommodate future processing requirements. It also reduces the number of data dependencies that must be analyzed, using the extended ER model conceptualization, and maintains data integrity through normalization. This approach can be implemented manually or in a simple software package as long as a "good" solution is acceptable and absolute optimality is not required.

Design and implementation of an integrated hospital database.

The need for the development of a modern hospital database which will support an integrated hospital information system has been recognized for several years. The exercise, however, has nearly always been more difficult than anticipated, and only a limited number of the relevant projects have been successful. A major common problem in most of the above efforts has been the lack of an appropriate hospital database design methodology: a subject on which the advice provided by the literature is limited. A database design methodology is proposed which should help overcome some of the difficulties and meet the database design requirements of a hospital in an optimal way.

A survey of database management in engineering

Database management in engineering fields is becoming extremely important. A number of reports and papers have been published on this subject and computer-aided design applications. It is important to know state-of-the-art to fully utilize the benefits of this new field. The paper contains a survey of literature on database management for engineering applications. The survey is broadly classified into database management concepts and systems. Research work of various authors in related areas such as database design methodology, data models, data definition and manipulation languages, database integrity and consistency are reviewed. Various database management systems (15 in all) currently in use are reviewed and their features tabulated. Capabilities and usefulness of these systems are provide important developments in data management field to the engineering community. Also, it should be useful to those currently engaged in research on the subject.