系统分析与设计 HW5

1. 领域建模

• a. 阅读Asg_RH文档，按用例构建领域模型

          1）按 Task2 要求，请使用工具 UMLet，截图格式务必是 png 并控制尺寸

          2）说明：请不要受PCMEF层次结构影响。你需要识别实体（E）和中介实体（M）

 

    其中，除Reservation为中介实体外，其余均为实体。

• b. 数据库建模（E-R模型）

       - 按 Task3 要求，给出系统的 E-R 模型（数据逻辑模型）

       - 建模工具 PowerDesigner

       - 导出 Mysql 物理数据库的脚本

       - 简单叙说数据库逻辑模型与领域模型的异同

    E-R 模型图：

    物理数据库脚本：

/*==============================================================*/
/* DBMS name:      MySQL 5.0                                    */
/* Created on:     2018/4/29 15:14:33                           */
/*==============================================================*/


drop table if exists City;

drop table if exists "Credit card";

drop table if exists Customer;

drop table if exists Hotel;

drop table if exists Reservation;

drop table if exists Room;

/*==============================================================*/
/* Table: City                                                  */
/*==============================================================*/
create table City
(
   city_id              int not null,
   city_name            varchar(100) not null,
   primary key (city_id)
);

/*==============================================================*/
/* Table: "Credit card"                                         */
/*==============================================================*/
create table "Credit card"
(
   card_id              int not null,
   bank_name            longtext not null,
   owner                varchar(50) not null,
   phone_num            char(20),
   security_code        char(10),
   primary key (card_id)
);

/*==============================================================*/
/* Table: Customer                                              */
/*==============================================================*/
create table Customer
(
   customer_id          int not null,
   card_id              int,
   customer_name        varchar(50) not null,
   email_address        longtext not null,
   primary key (customer_id)
);

/*==============================================================*/
/* Table: Hotel                                                 */
/*==============================================================*/
create table Hotel
(
   hotel_id             int not null,
   city_id              int,
   room_id              int,
   hotel_name           varchar(100) not null,
   primary key (hotel_id)
);

/*==============================================================*/
/* Table: Reservation                                           */
/*==============================================================*/
create table Reservation
(
   book_id              int not null,
   hotel_id             int,
   room_id              int,
   customer_id          int,
   check_in_date        varchar(50) not null,
   check_out_date       varchar(50) not null,
   primary key (book_id)
);

/*==============================================================*/
/* Table: Room                                                  */
/*==============================================================*/
create table Room
(
   room_id              int not null,
   room_type            int not null,
   price                int not null,
   is_available_now     bool not null,
   primary key (room_id)
);

alter table Customer add constraint FK_Reference_6 foreign key (card_id)
      references "Credit card" (card_id) on delete restrict on update restrict;

alter table Hotel add constraint FK_Reference_1 foreign key (city_id)
      references City (city_id) on delete restrict on update restrict;

alter table Hotel add constraint FK_Reference_2 foreign key (room_id)
      references Room (room_id) on delete restrict on update restrict;

alter table Reservation add constraint FK_Reference_3 foreign key (hotel_id)
      references Hotel (hotel_id) on delete restrict on update restrict;

alter table Reservation add constraint FK_Reference_4 foreign key (room_id)
      references Room (room_id) on delete restrict on update restrict;

alter table Reservation add constraint FK_Reference_5 foreign key (customer_id)
      references Customer (customer_id) on delete restrict on update restrict;

      数据库逻辑模型与领域模型的异同：

      数据库逻辑模型从数据需求分析出系统的额实体属性图，对实体之间的依赖关机进行整合，由实体，属性和联系组成。

      领域模型是对领域内的概念类或现实世界中对象的可视化表示。

      相同之处：两种模型都可以反映类，类之间的关联以及类的属性。

      不同之处：数据库逻辑模型的定义用来表示存储于某处的持久性数据，且其建立与软件开发工作密切相关，是设计阶段的必需工作；而领域模型反映的是现实世界中对象的概念透视图，与业务逻辑相关，同领域中相似业务可能具有类似的领域模型，在领域模型里，并不会排除需求中没有明确要求记录其相关信息的类，而数据库逻辑模型则必须完成该排除工作，同时领域模型也不会排除没有属性的概念类。