One-to-One Dependencies in Database Design

Peretz Shoval

doi:10.1109/69.91053

One-to-One Dependencies in Database Design

Peretz Shoval

Department of Software and Information Systems Engineering

Research output: Contribution to journal › Article › peer-review

1 Scopus citations

Abstract

The types of dependencies between objects in some reality determine to a large extent the structure of its database schema. While 1:n (or n:l) and m:n dependencies received extensive treatment in various models and methods for database design, 1:1 dependencies received arbitrary treatment only. We focus on the 1:1 dependency type and show 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 l:n or n:l dependencies. These are implemented within the system ADDS for automated database design.

Original language	English
Pages (from-to)	371-379
Number of pages	9
Journal	IEEE Transactions on Knowledge and Data Engineering
Volume	3
Issue number	3
DOIs	https://doi.org/10.1109/69.91053
State	Published - 1 Jan 1991

ASJC Scopus subject areas

Information Systems
Computer Science Applications
Computational Theory and Mathematics

Access to Document

10.1109/69.91053

Cite this

@article{e106750355f84f4d9f23cd2670c31315,

title = "One-to-One Dependencies in Database Design",

abstract = "The types of dependencies between objects in some reality determine to a large extent the structure of its database schema. While 1:n (or n:l) and m:n dependencies received extensive treatment in various models and methods for database design, 1:1 dependencies received arbitrary treatment only. We focus on the 1:1 dependency type and show 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 l:n or n:l dependencies. These are implemented within the system ADDS for automated database design.",

author = "Peretz Shoval",

year = "1991",

month = jan,

day = "1",

doi = "10.1109/69.91053",

language = "English",

volume = "3",

pages = "371--379",

journal = "IEEE Transactions on Knowledge and Data Engineering",

issn = "1041-4347",

publisher = "Institute of Electrical and Electronics Engineers",

number = "3",

}

TY - JOUR

T1 - One-to-One Dependencies in Database Design

AU - Shoval, Peretz

PY - 1991/1/1

Y1 - 1991/1/1

N2 - The types of dependencies between objects in some reality determine to a large extent the structure of its database schema. While 1:n (or n:l) and m:n dependencies received extensive treatment in various models and methods for database design, 1:1 dependencies received arbitrary treatment only. We focus on the 1:1 dependency type and show 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 l:n or n:l dependencies. These are implemented within the system ADDS for automated database design.

AB - The types of dependencies between objects in some reality determine to a large extent the structure of its database schema. While 1:n (or n:l) and m:n dependencies received extensive treatment in various models and methods for database design, 1:1 dependencies received arbitrary treatment only. We focus on the 1:1 dependency type and show 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 l:n or n:l dependencies. These are implemented within the system ADDS for automated database design.

UR - http://www.scopus.com/inward/record.url?scp=0026220098&partnerID=8YFLogxK

U2 - 10.1109/69.91053

DO - 10.1109/69.91053

M3 - Article

AN - SCOPUS:0026220098

SN - 1041-4347

VL - 3

SP - 371

EP - 379

JO - IEEE Transactions on Knowledge and Data Engineering

JF - IEEE Transactions on Knowledge and Data Engineering

IS - 3

ER -

One-to-One Dependencies in Database Design

Abstract

ASJC Scopus subject areas

Access to Document

Other files and links

Fingerprint

Cite this