1982
DOI: 10.1007/3-540-11214-6_1
|View full text |Cite
|
Sign up to set email alerts
|

An integrated approach to database design

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

1983
1983
1998
1998

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(3 citation statements)
references
References 38 publications
0
3
0
Order By: Relevance
“…It further selects a primary fragment F/' of this class Ci most appropriate to merge with this derived fragment F/a and eventually produces a non-overlapping set of horizontal fragments that has incorporated method dependency information. Finally, since it is possible to place an object in more than one primary fragment, Affinity Rule 5.2 is used to find the primary fragment with which it has the greatest affinity (line (15)(16)(17)(18)(19)(20)(21)(22)) and it is removed from all other (line (23-25)). 7.…”
Section: The Algorithmmentioning
confidence: 99%
“…It further selects a primary fragment F/' of this class Ci most appropriate to merge with this derived fragment F/a and eventually produces a non-overlapping set of horizontal fragments that has incorporated method dependency information. Finally, since it is possible to place an object in more than one primary fragment, Affinity Rule 5.2 is used to find the primary fragment with which it has the greatest affinity (line (15)(16)(17)(18)(19)(20)(21)(22)) and it is removed from all other (line (23-25)). 7.…”
Section: The Algorithmmentioning
confidence: 99%
“…Its design can be divided into two distinct parts: logical and physical [36]. The logical design describes the relation between data items and the way they are perceived by the users.…”
Section: The Implementation Of a Prototypementioning
confidence: 99%
“…U is a set of users who can be from the operations level, management control level, strategic planning level, or from a combination of these levels [4]. D, although it still represents needed data sets, can now be ad hoc sets obtained irregularly, or a knowledge base obtained by a logical data base design process [14,36], or by an artificial intelligence procedure [29], or both. D* is a data management component which can be a sophisticated Data Base Management System (DBMS), or can be a file system.…”
Section: Evolution Of Design Considerationsmentioning
confidence: 99%