04.06.2015 Views

Database Modeling and Design

Database Modeling and Design

Database Modeling and Design

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Glossary 235<br />

functional dependency (FD)—The property of one or more<br />

attributes (data items) that uniquely determines the value of one<br />

or more other attributes (data items). Given a table R, a set of<br />

attributes B is functionally dependent on another set of attributes<br />

A if, at each instant of time, each A value is associated with only<br />

one B value.<br />

generalization—A special type of abstraction relationship that specifies<br />

that several types of entities with certain common attributes<br />

can be generalized (or abstractly defined) with a higher-level<br />

entity type, a supertype entity; an “is-a” type relationship. For<br />

example, employee is a generalization of engineer, manager, <strong>and</strong><br />

administrative assistant, based on the common attribute job-title.<br />

A tool often used to make view integration possible.<br />

global schema—A conceptual data model that shows all the data <strong>and</strong><br />

their relationships in the context of an entire database.<br />

key—A generic term for a set of one or more attributes (data items) that,<br />

taken collectively, enables one to identify uniquely an entity or a<br />

record in a SQL table; a superkey.<br />

logical design—The steps in the database life cycle involved with the<br />

design of the conceptual data model (schema), schema integration,<br />

transformation to SQL tables, <strong>and</strong> table normalization; the<br />

design of a database in terms of how the data is related, but without<br />

regard to how it will be stored.<br />

lossless decomposition—A decomposition of a SQL table into two or<br />

more smaller tables is lossless if <strong>and</strong> only if the cycle of table<br />

decomposition (normalization) <strong>and</strong> the recomposition (joining<br />

the tables back through common attributes) can be done without<br />

loss of data integrity.<br />

m<strong>and</strong>atory existence—A connectivity between two entities that has<br />

a lower bound of one. One example is the “works-in” relationship<br />

between an employee <strong>and</strong> a department; every department has at<br />

least one employee at any given time. Note: if this is not true,<br />

then the existence is optional.<br />

multiplicity—In UML, the multiplicity of a class is an integer that<br />

indicates how many instances of that class are allowed to exist.<br />

multivalued dependency (MVD)—The property of a pair of rows in<br />

a SQL table such that if the two rows contain duplicate values of<br />

attribute(s) X, then there is also a pair of rows obtained by interchanging<br />

the values of Y in the original pair. This is a multivalued

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!