数据库建模与设计：逻辑设计实战指南

需积分: 14 66 浏览量更新于2024-07-20 1 收藏 5.56MB PDF 举报

"Database.Modeling.and.Design.5th.Edition.Logical.Design" 本书《Database Modeling and Design: Logical Design》是数据库设计领域的经典著作，专注于在关系型数据库系统中的建模和设计技术。作者通过实体关系（ER）方法和统一建模语言（UML）方法，深入讲解了逻辑数据库设计，以规范数据需求和概念建模。书中首先介绍了数据库的生命周期，随后详细讨论了ER模型和UML，展示了数据建模概念如何应用于数据库设计过程。在数据库规范化部分，书中涵盖了ER模型和UML概念模型的功能等价性，以及Boyce-Codd范式下的关系模型。作者对比分析了面向对象数据库系统与关系数据库系统的差异，并探讨了解决两者之间不匹配问题的扩展方法，如对关系系统的增强。此外，书中还涉及了Web技术，包括XML的概述和特定数据库设计问题，以及如何利用IBM的Rational Data Architect、Computer Associates AllFusion ERwin Data Modeler和Sysbase的PowerDesigner等CASE工具来处理复杂的数据库建模问题。这本书对于初学者和经验丰富的专业数据库实践者来说都是很好的指南，提供了大量实际案例和设计规则，适用于任何基于SQL、UML或XML的系统，对于需要创建大型企业数据模型的人来说，具有立竿见影的效果。书中的章节涵盖了从介绍到具体设计工具的广泛主题，包括： 1. 引言 2. 实体关系模型 3. 统一建模语言 4. 需求分析和概念数据建模 5. 从概念数据模型转换到SQL 6. 规范化 7. 逻辑数据库设计示例 8. 对象关系设计 9. XML和Web数据库 10. 商业智能 11. 用于逻辑数据库设计的CASE工具通过阅读此书，读者可以深入了解数据库设计的各个方面，掌握从需求分析到实现的完整流程，并学习如何利用各种工具和技术来优化和管理数据库。

a. Conceptual data modeling. The data requirements are

analyzed and modeled by using an ER or UML dia-

gram that includes many features we will study in

Chapters 2 and 3, for example, semantics for optional

relationships, ternary relationships, supertypes, and

subtypes (categories). Processing requirements are

typically specified using natural language expressions

or SQL commands along with the frequency of occur-

rence. Figure 1.2 (S

tep II.a) shows

a possible ER

Information Requirements

Determine requirements

Logical Design

[multiple views]

Model Integrate views

[single view]

Transform to SQL tables

Normalize

Physical Design

Select indexes

[special requirements]

Denormalize

[else]

Implementation

Implement

[else]

Monitor and detect changing requirements

[defunct]

Figure 1.1 The database life

cycle.

4 Chapter 1 INTRODUCTION

c. Transformation of the conceptual data model to SQL

tables. Based on a categorization of data modeling con-

structs and a set of mapping rules, each relationship

and its associated entities are transformed into a set of

DBMS-specific candidate relational tables. We will

show these transformations in standard SQL in Chapter

5. Redundant tables are eliminated as part of this pro-

cess. In our example, the tables in Step II.c of Figure 1.2

are the

result of transformation of the integrated ER

model in Step II.b.

d. Norm

aliza tion of tables. Given

a table ( R), a set o f

attributes (B) is functionally dependent o n another

set of attributes (A) if, at each instant of time, each

A value is associated with exactly one B value. Func-

tional dependencies (FDs) are derived from the con-

ceptual d ata m ode l d iagra m a nd the semantics of

data relationships in the req uiremen ts analysis. They

represent the dependencies among data elements

that are unique i dent ifiers (keys ) of e ntiti es. Addi-

tional FDs, which repre sen t the dependencies

between key and nonkey attributes within entities,

canbederivedfromtherequirementsspecification.

Candidate relational tables associated with all

derived FDs are normalized (i.e., modified by

decomposing or splitting tabl es into smaller tables)

using standard normalization techniques. Finally,

redundancies in the data that occur in nor malized

candidate tables are analyzed further for possibl e

elimination, with the constraint that data integrity

must be preserved. An example of normalization of

the Salesperson table into the new Salesperson and

SalesVacations tables is shown in

Figure 1.2 from

tep II.c

to Step II.d.

We note here that database tool vendors tend to use

the term logical model to refer

to the conceptual data

model, and they use the term physical model to refer

to the DBMS-specific implementation model (e.g.,

SQL tables). We also note that many conceptual data

models are obtained not from scratch, but from the

process of reverse engineering from an existing

DBMS-specific schema (Silberschatz et al., 2010).

Chapter 1 INTRODUCTION 7

III. Physical design. The physical design step involves the

selection of indexes (access methods), partitioning,

and clustering of data. The logical design methodology

in Step II simplifies the approach to designing large rela-

tional databases by reducing the number of data

dependencies that need to be analyzed. This is accom-

plished by inserting the conceptual data modeling and

integration steps (Steps II.a and II.b of Figure 1.2)

into

the

traditional relational design approach. The objective

of these steps is an accurate representation of reality.

Data integrity is preserved through normalization of the

candidate tables created when the conceptual data

model is transformed into a relational model. The pur-

pose of physical design is to then optimize performance.

As part of the physical design, the global schema can

sometimes

be refined in

limited ways to reflect pro-

cessing (query and transaction) requirements if there

are obvious large gains to be made in efficiency. This

is called denormalization. It consists of selecting domi-

nant processes on the basis of high frequency, high vol-

ume, or explicit priority; defining simple extensions to

tables that will improve query performance; evaluating

total cost for query, update, and storage; and consider-

ing the side effects, such as possible loss of integrity.

This is particularly important for online analytical pro-

cessing (OLAP) applications.

IV.Database implementation, monitoring, and modifica-

tion. Once the design is completed, the database can be

created through implementation of the formal schema

using the data definition language (DDL) of a DBMS. Then

the data manipulation language (DML) can be used to

query and update the database, as well as to set up indexes

and establish constraints, such as referential integrity.

The language SQL contains both DDL and DML con-

structs; for example, the create table command represents

DDL, and the select command represents DML.

As the database begins operation, monitoring

indicates whether performance requirements are being

met. If they are not being satisfied, modifications should

be made to improve performance. Other modifications

may be necessary when requirements change or end

8 Chapter 1 INTRODUCTION

剩余334页未读，继续阅读

ramissue

粉丝: 354
资源: 1487

数据库建模与设计：逻辑设计实战指南

MK.Database.Modeling.and.Design.Fifth.Edition.Logical.Design

Morgan.Kaufmann.Database.Modeling.and.Design.4th.Edition.rar

Orchard.Signals.and.Systems.with.MATLAB.Computing.and.Simulink.Modeling.4th.Edition.Apr.2008

Fuzzy.Databases.Modeling.Design.And.Implementation

Database Modeling and Design.5th.2011

Database Modeling and Design 5th Edition

John.Wiley.&.Sons.Service-Oriented.Modeling.Service.Analysis.Design.And.Architecture.2008.pdf

Database Modeling and Design, Fifth Edition: Logical Design

Multilevel.Business.Processes.Modeling.and.Data.Analysis.365811083X

Springer.Computer.Graphics.and.Geometric.Modeling

最新资源