1991IEEE Transactions on Knowledge and Data EngineeringRequires access

One-to-one dependencies in database design

Peretz Shoval

Open publisher page 1 citations

Abstract

The author focuses on the 1:1 dependency type and shows its significance in database design. Various situations involving 1:1 dependencies are analyzed and classified, and proper treatment of the dependency in those situations is suggested. These dependencies are treated at both the conceptual and the logical design levels. Decision rules are provided for the conversion of 1:1 dependencies into 1:n or n:1 dependencies. These are implemented with the system ADDS for automated database design.>

About this research paper

What this paper is about

The author focuses on the 1:1 dependency type and shows its significance in database design. Various situations involving 1:1 dependencies are analyzed and classified, and proper treatment of the dependency in those situations is suggested. These dependencies are treated at both the conceptual and the logical design levels. Decision rules are provided for the conversion of 1:1 dependencies into 1:n or n:1 dependencies. These are implemented with the system ADDS for automated database design.>

Why it matters

OpenAlex reports 1 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

The author focuses on the 1:1 dependency type and shows its significance in database design. Various situations involving 1:1 dependencies are analyzed and classified, and proper treatment of the dependency in those situations is suggested. These dependencies are treated at both the conceptual and the logical design levels. Decision rules are provided for the conversion of 1:1 dependencies into 1:n or n:1 dependencies. These are implemented with the system ADDS for automated database design.>

Key concepts: Functional dependency, Dependency (UML), Computer science, Database design, Dependency theory (database theory), Database theory, Database, Data mining

Related papers

Back to paper searchBrowse research topicsOriginal source
One-to-one dependencies in database design — Research Paper | ScholarLens