04.06.2015 Views

Database Modeling and Design

Database Modeling and Design

Database Modeling and Design

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Glossary 233<br />

database administrator (DBA)—The person in a software organization<br />

who is in charge of designing, creating, <strong>and</strong> maintaining the<br />

databases of an enterprise. The DBA makes use of a variety of software<br />

tools provided by a DBMS.<br />

database life cycle—An enumeration <strong>and</strong> definition of the basic steps<br />

in the requirements analysis, design, creation, <strong>and</strong> maintenance<br />

of a database as it evolves over time.<br />

database management system (DBMS)—A generalized software<br />

system for storing <strong>and</strong> manipulating databases. Examples include<br />

Oracle, IBM’s DB2, Microsoft SQL Server, or Access.<br />

data mining—A way of extracting knowledge from a database by<br />

searching for correlations in the data <strong>and</strong> presenting promising<br />

hypotheses to the user for analysis <strong>and</strong> consideration.<br />

DBA—See database administrator.<br />

degree of a relationship—The number of entities associated in the<br />

relationship: recursive binary (1 entity), binary (2 entities), ternary<br />

(3 entities), n-ary (n entities).<br />

denormalization—The consolidation of database tables to increase<br />

performance in data retrieval (query), despite the potential loss of<br />

data integrity. Decisions on when to denormalize tables are based<br />

on cost/benefit analysis by the DBA.<br />

deployment diagram (UML)—Shows the physical nodes on which a<br />

system executes. This is more closely associated with physical<br />

database design.<br />

dimension table—The smaller tables used in a data warehouse to<br />

denote the attributes of a particular dimension, such as time, location,<br />

customer characteristics, product characteristics, etc.<br />

disjointness constraint (d)—A symbol in an ER diagram to designate<br />

that the lower-level entities in a generalization relationship have<br />

nonoverlapping (disjoint) occurrences. If the occurrences overlap,<br />

then use the designation (o) in the ER diagram.<br />

entity—A data object that represents a person, place, thing, or event if<br />

informational interest; it corresponds to a record in a file when<br />

stored. For example, you could define employee, customer,<br />

project, team, <strong>and</strong> department as entities.<br />

entity cluster—The result of a grouping operation on a collection of<br />

entities <strong>and</strong> relationships in an ER model to form a higher-level<br />

abstraction, which can be used to more easily keep track of the<br />

major components of a large-scale global schema.

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

Saved successfully!

Ooh no, something went wrong!