《chapter4_3.pptVIP

Chapter 4 High-Level Database Models  The database modeling and implementation process Outline: 1.entity-relationship diagram 2.Conversion of E/R diagram to relation schemas Entity-Relationship(ER) Model The ER model is a high-level conceptual data model. It has not been implemented in any commercial DBMS (?), but is a powerful short hand often used in database design for a first rendition of the miniworld. The ER model was introduced by Peter Chen in 1976, and is now the most widely used conceptual data model. Conceptual Data Models Conceptual data models provide languages to describe conceptual schemas. Conceptual schemas are used to describe the classes of objects that occur in an application area, their properties, their relationships, and the constraints that hold with respect to those classes of objects. Center on “what kind of objects a database contains” and not on “how these objects are stored” (? Internal Schema) and not on “how these objects are represented / displayed to a person that accesses the database” (? External Schema). As a database design tool formalizing the information requirements of the end users As a documentation tool for databases (to help programmers, especially those that have to update the database) As a data model of a database management system (only very few experimental systems exist) As a tool of system analysis The Real World Definitions An entity is an object in the miniworld. An attribute of an entity can have a value from a value set (domain) Each entity belongs to some one entity type Attribute Examples 表示方法 实体型：矩形＋实体名 属性：椭圆形，无向边与实体连接 联系：菱形＋联系名，无向边与实体连接，边上标注联系类型 E-R图构成规则 带有属性的E-R图例一 实体属性与实体及其联系图例二 实体属性与实体及其联系图例三 数据库设计步骤 目前数据库设计主要采用以逻辑数据库设计和物理数据库设计为核心的规范化设计方法。即将数据库设计分为六个阶段。 数据库设计步骤 Database Design Process 需求分析 1. 需求分析的任务 详细调查现实世界要处理的对象 充分了解原系统的工作概况 明确用户的各种需求 信息要求 处理要求 安全性要求 完整性要求 确定新系统的功能 考虑今后的扩充性 2. 需求分析的步骤 1) 调查组织机构情况 2) 调查各部门的业务活动流程 3) 协助用户明确对新系统的各种需求 4) 确定新系统的边界 5) 分析系统功能 ... 需求分析阶段 概念结