系统分析与设计第四次作业

系分第四次作业

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

1. 数据库建模(E-R 模型)

   使用Mysql Workbench构建

   

   生成的sql语句如下:

-- MySQL Script generated by MySQL Workbench
-- Sun Apr 29 12:43:14 2018
-- Model: New Model    Version: 1.0
-- MySQL Workbench Forward Engineering

SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL,ALLOW_INVALID_DATES';

-- -----------------------------------------------------
-- Schema mydb
-- -----------------------------------------------------
DROP SCHEMA IF EXISTS `mydb` ;

-- -----------------------------------------------------
-- Schema mydb
-- -----------------------------------------------------
CREATE SCHEMA IF NOT EXISTS `mydb` DEFAULT CHARACTER SET utf8 ;
USE `mydb` ;

-- -----------------------------------------------------
-- Table `mydb`.`Hotel`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`Hotel` ;

CREATE TABLE IF NOT EXISTS `mydb`.`Hotel` (
  `idhotel` INT NOT NULL,
  `name` VARCHAR(45) NULL,
  `price` VARCHAR(45) NULL,
  `location` VARCHAR(45) NULL,
  `Hotelcol` VARCHAR(45) NULL,
  PRIMARY KEY (`idhotel`))
ENGINE = InnoDB;


-- -----------------------------------------------------
-- Table `mydb`.`Customer`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`Customer` ;

CREATE TABLE IF NOT EXISTS `mydb`.`Customer` (
  `idCustomer` INT NOT NULL,
  `name` VARCHAR(45) NULL,
  `phone` VARCHAR(45) NULL,
  `Hotel_idhotel` INT NOT NULL,
  PRIMARY KEY (`idCustomer`),
  INDEX `fk_Customer_Hotel1_idx` (`Hotel_idhotel` ASC),
  CONSTRAINT `fk_Customer_Hotel1`
    FOREIGN KEY (`Hotel_idhotel`)
    REFERENCES `mydb`.`Hotel` (`idhotel`)
    ON DELETE NO ACTION
    ON UPDATE NO ACTION)
ENGINE = InnoDB;


-- -----------------------------------------------------
-- Table `mydb`.`Reservation`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`Reservation` ;

CREATE TABLE IF NOT EXISTS `mydb`.`Reservation` (
  `idReservation` INT NOT NULL,
  `Customer info` VARCHAR(45) NULL,
  `Room info` VARCHAR(45) NULL,
  `checkin_data` VARCHAR(45) NULL,
  `checkout_data` VARCHAR(45) NULL,
  `Customer_idCustomer` INT NOT NULL,
  `Hotel_idhotel` INT NOT NULL,
  PRIMARY KEY (`idReservation`, `Hotel_idhotel`),
  INDEX `fk_Reservation_Customer1_idx` (`Customer_idCustomer` ASC),
  INDEX `fk_Reservation_Hotel1_idx` (`Hotel_idhotel` ASC),
  CONSTRAINT `fk_Reservation_Customer1`
    FOREIGN KEY (`Customer_idCustomer`)
    REFERENCES `mydb`.`Customer` (`idCustomer`)
    ON DELETE NO ACTION
    ON UPDATE NO ACTION,
  CONSTRAINT `fk_Reservation_Hotel1`
    FOREIGN KEY (`Hotel_idhotel`)
    REFERENCES `mydb`.`Hotel` (`idhotel`)
    ON DELETE NO ACTION
    ON UPDATE NO ACTION)
ENGINE = InnoDB;


-- -----------------------------------------------------
-- Table `mydb`.`Room`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`Room` ;

CREATE TABLE IF NOT EXISTS `mydb`.`Room` (
  `idRoom` INT NOT NULL,
  `type` VARCHAR(45) NULL,
  `price` VARCHAR(45) NULL,
  `Reservation_idReservation` INT NOT NULL,
  `Hotel_idhotel` INT NOT NULL,
  PRIMARY KEY (`idRoom`),
  INDEX `fk_Room_Reservation1_idx` (`Reservation_idReservation` ASC),
  INDEX `fk_Room_Hotel1_idx` (`Hotel_idhotel` ASC),
  CONSTRAINT `fk_Room_Reservation1`
    FOREIGN KEY (`Reservation_idReservation`)
    REFERENCES `mydb`.`Reservation` (`idReservation`)
    ON DELETE NO ACTION
    ON UPDATE NO ACTION,
  CONSTRAINT `fk_Room_Hotel1`
    FOREIGN KEY (`Hotel_idhotel`)
    REFERENCES `mydb`.`Hotel` (`idhotel`)
    ON DELETE NO ACTION
    ON UPDATE NO ACTION)
ENGINE = InnoDB;


-- -----------------------------------------------------
-- Table `mydb`.`table1`
-- -----------------------------------------------------
DROP TABLE IF EXISTS `mydb`.`table1` ;

CREATE TABLE IF NOT EXISTS `mydb`.`table1` (
)
ENGINE = InnoDB;


SET SQL_MODE=@OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;

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

​ 逻辑模型是将概念模型转化为具体的数据模型的过程，即按照概念结构设计阶段建立的基本E-R图，按选定的管理系统软件支持的数据模型（层次、网状、关系、面向对象），转换成相应的逻辑模型。这种转换要符合关系数据模型的原则。

​ 领域模型是描述业务用例实现的对象模型。该模型为产生预期效果确定了业务人员以及他们处理和使用的对象之间应该具有的静态和动态关系。它注重业务中承担的角色及其当前职责。这些模型类的对象组合在一起可以执行所有的业务用例。

​ 数据库模型更具体，有由领域模型中关系得到的具体表间关系、也有每个属性的具体类型等，领域模型更关注整体