The Logical Record Access Approach to Database Design

Teorey, Toby J.; Fry, James P.

doi:10.1145/356810.356815

Cited by 33 publications

(13 citation statements)

References 47 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Haerder (1978) describes the structure of relationships between entities, but makes no mention of data model validation to insure that all relationships are accounted for. Teorey and Fry (1980) uses a processing matrix in which each transaction and report is represented in terms of the attributes required. It may be possible to adapt this approach for validation, but it is not presented as such.…”

Section: Literature Reviewmentioning

confidence: 99%

A Data Model Validation Approach for Relational Database Design Courses

Parker

2004

IISIT

View full text Add to dashboard Cite

This paper presents an instructional method for validating a relational database design. Data model validation is often overlooked in course projects involving relational database design, in part because while most database texts stress the importance of validation, few provide an instructional method for performing validation. Validation is a critical step, especially for students. A flawed data model may omit non-key attributes or even the foreign keys required to join tables. This can make the design of SQL queries, forms, and reports a frustrating experience. This approach requires the designer to determine which attributes account for the field values on forms and reports, which entities are associated with those attributes, and how those entities are linked to an integral or primary entity. Such an approach serves to validate the completeness of the data model.

show abstract

Section: Literature Reviewmentioning

confidence: 99%

A Data Model Validation Approach for Relational Database Design Courses

Parker

2004

IISIT

View full text Add to dashboard Cite

show abstract

“…An experiment was carried out on a simple case study (modified version of the example of reference [6] as given below.…”

Section: A Case Studymentioning

confidence: 99%

“…Logical design may be based upon some specific theory as dependency theoryll -3], relationships between entities [4][5], logical record access [6] ... etc. The model in which the design can be expressed is different in each case (e.g.…”

Section: Introductionmentioning

confidence: 99%

An Integrated Approach to Data Base Design

حامد¹

1993

eng

View full text Add to dashboard Cite

ABSTRACf. In this paper, a new method for data base design is proposed. The method mflkes use of some good features in different design approaches. Based on the results of a preliminary phase of determining user requirements, an initial design is first developed. Then the design is tuned according to some pre-d~fined changes in both the logical model and the physical representation. Response time is used as a measure of the effectiveness of the design.Algorithms to implement the method are developed. Selection of the best design model (logical and physical) is left to the data base administrator (DBA). Results obtained from running the proposed algorithms can be used to help the DBA in taking the appropriate decision.

show abstract

“…Access paths define the key data elements (index databases, database keys, indexes in IMS, CODASYL, and Relational DBMSs. respectively) through which efficient access paths have been widely studied in the database literature (Fedorowicz I987;Sacco 1986;Valduriez 1987;Teorey and Fry 1980). Much of this work has been DBMS independent.…”

Section: Physical Database Designmentioning

confidence: 99%

“…Although numerous mathematical approaches and automated support tools have been developed (Albano, de Antonellis and Di Leva 1985;Reiner 1984), physical database design remains a human intensive process (Lam, Su and Koganti 1988;Teorey and Fry 1980). Recently, knowledge-based or expert system approaches have been applied to the development of physical database design tools (Dabrowski, Jefferson, Carlis and March 1989;Dogac, Yuruten and Spaccapietra 1989;Kao 1986).…”

Section: Introductionmentioning

confidence: 99%

Form and Substance in Physical Database Design: An Empirical Study

Prietula

March

1991

Information Systems Research

View full text Add to dashboard Cite

As with many complex design problems, physical database design is difficult, ill-structured, and highly human intensive. In order to effectively construct support systems or improve the practice of database design, it is important to understand how human designers reason about the task. We report an empirical study of physical database design problem solving. Thirteen subjects each solved two physical database design problems: five subjects were experienced designers; eight were graduate students with little or no actual design experience, though they were exposed to the principles of design through coursework. For each problem, subjects were presented with a list of available problem information (hardware, content, and activity data) and were directed to generate a physical design (record structures and access paths) that would minimize retrieval time and storage space. All sessions were audiotaped. Three types ofdata were incorporated for the analysis: infonnation acquisition patterns, solution generation patterns, and verbal protocol. It was hypothesized that database design reasoning embodies forms of deliberation to reduce problem-solving complexity and that these forms resemble those found in other design problem-solving studies-commonality of task environmental demands will result in commonality in problem-solving methods in response to those demands. In particular, we expected to find specific control strategies, the use of hierarchical abstraction, the use of problem-specific heuristics, and the use of qualtitative reasoning with mental models of dynamic components of the task. Our results indicate that these forms are indeed present and of significant value in physical database design problem solving. Experience played a significant role in determining both the form and substance of reasoning used in physical database design. Both experienced and inexperienced database designers exhibited at least some of these forms of reasoning. Experienced designers, however, effectively applied these forms, demonstrating a substance of reasoning, although their methods of application varied considerably. The least experienced designers did not effectively apply these forms and, lost in the detail of the design problems, were unable to generate reasonable designs. It is concluded that recognition of appropriate reasoning forms and the effective application of these forms arc critical to developing efficient physical database designs. The implications of the findings are discussed.Database design-Problem solving-Expertise

show abstract

The Logical Record Access Approach to Database Design

Cited by 33 publications

References 47 publications

A Data Model Validation Approach for Relational Database Design Courses

A Data Model Validation Approach for Relational Database Design Courses

An Integrated Approach to Data Base Design

Form and Substance in Physical Database Design: An Empirical Study

Contact Info

Product

Resources

About