数据库设计英文文档.docx

南京信息工程大学实验（实习）报告学院 计算机与软件学院 实验名称 数据库设计 指导教师 王海滨 日期 12.13专业 软件工程 年级 2013班级 软件工程3班 学号 20131344097姓名 郭明清1. The books management system management system data requirementsThrough the establishment of a library management system based on C/S system, makes the books management work systematic, standardization and automation, so as to improve the management efficiency, also convenient for readers borrowing.Using c # programming, the realization of the management of the database information.System application conforms to the provisions of the library information management and processing, satisfy the librarian to books and the demand of the library information management, and achieve the intuitive and convenient in the process of operation, use and security requirements.System with the method of the modular program design, convenient for the combination of the system function and modify, supplement and maintain and facilitate participation in technical personnel.Data dictionary:Data stream number: D01 data flow name: readers information description: the reader informationAfter data flow source: readers lending, administrators will reader input information into the computer.The data flow goes: books management module.Readers information will be stored in the database information table (readers).Data item: the readers name, student id and professionalData stream number: D02 data flow name: book information description: book informationData flow sources: after the book to the library, the administrator will book input information into the computer.The data flow goes: books management module.Readers information will be stored in the database (book information table).Data item: the book number + + books category title + + author press + Price unit Price + date + purchase quantityData stream number: D03 data flow name: readers situation description: readersAfter data flow source: books are borrowed, computer the reader information back to the administrator.The data stream to: administrator.Data entry: has borrowed books + number + renew frequency of has borrowedData stream number: D04 data flow name: books situation description: booksAfter data flow source: books are borrowed, computer will book information back to the administrator.The data stream to: administrator.Data item: whether the title + number + have borrowData stream number: D05Data flow name: borrow return book information description: borrow return book informationSource of data flow: the administrator to put borrow return book information into the computer.聽The data flow goes: books management module.Books borrowed information will be stored in the database (borrowing information table).Data item: have borrow name + is also the titleData stream number: D06Data flow name: book information description: book informationData flow source: readers get book information from the computer.Data flows to: the reader.聽Data item: the book number + + books category title + + author press + Price unit Price + date + purchase quantityData stream number: D07Data flow name: readers lending situation description: readers lendingSource of data flow: readers lending conditions from the computer.Data flows to: the reader.聽Data item: whether the title + number + have borrow1.1 books management system management system function data requirements(1) readers basic information input, including login number, readers, readers name, gender, etc.(2) readers basic information query, modify, including number, name of the reader, readers gender, etc.(3) books categories of standards, categories of information input, including category number, category name.(4) the books category information query, modify, including category number, category name.(5) the book inventory information input, including number, name of books, books, books category, authors last name, name of publisher, publication date, date of registration.(6) book inventory information query, modify, including number, name of books, books, books category, author name, press, name, date of publication, registration, etc.(7) library information input, including the reader code, serial number, date of library books.(8) borrow books information query, modification, including number, book number, date of return the book readers.(9) return the book information input, including number, book number, date of return the book readers.(10) also book information query and modify, including also book readers readers number, name, book number, name of the book, end date, return the book date, etc.Fine input (11) are also book, book beyond the deadline also include beyond deadline also readers of the book number, book number, fines.(12) are also fine books query, delete, including readers readers number, name, book number, name of the book, fines, etc.(1) the administrator management, including the creation of user information, delete, readers of user information, add, delete, book information book information.1.1 organizational structureThe organizational structure of the listed document.The first chapter: the books management system management system data requirements.The second chapter: the books management system management system concept design.The third chapter: the books management system management system logic design.Appendix A: is this document index of the chart.1. The concept designThe analysis on the basic needs of books management system management system, using the conceptual structure design of abstract mechanism, the results of the analysis of information needed for classification, organization, system entity, the entity attribute, the keys of the entities, the connection between the entity and the types of contact, can design the concept model of the system.聽Through the analysis, we can extract the books management system management system basic entities are: administrators, readers, three entities by readers borrow books, the administrator management, administrators and readers, readers and books are one-to-many link.1.1 the overall E - R diagram聽User: user id, name, sex, its role, phone, email, password, whether can borrow books, current can borrow books number;User role: authority number, name of permissions, access description;Are records: extended number, extended user number, beyond the book number, are days overdue, fines, whether already pay a fine;User role: part number, role, character description, the maximum number of days can borrow books maximum number, can borrow books, can renew frequency, the maximum number of days per renew, role authorization;Administrator: administrator id, name, password, phone, email;Lost records: number, lost books number lost, lost books have user number, report time, pay a fine, whether or not to buy lost books;Books: book number, bname, author, ISBN number, press, publishing time, total number of words, the total number of pages, pricing, content abstract, books category, warehousing date, is in charge of, whether can borrow, books category;Library: branch number, branch pavilion, contact phone number, address, introduction of branch libraries;Books categories: type type number, name, type, extended should pay fines and lost should pay fines;Borrowing record: borrowing number, user id, book number, time saving, have returned, should also date, whether be renew, renew frequency, if they are;Books categories: category number, category name and category;System: the log number, journal content, time, system is normal;Between each entity contact overall e-r diagram below:1.1 books management system management system module e-r diagramVarious modules and functions to see relationships the e-r diagram below:1. The logic designE-r diagram to relational model transformationLogic structure of the relational model is a set of collection of relation mode.E-r map is by the entity, the entity attributes and the relationship between entities three components.So the e-r diagram into relation model is actually to entity, the entity attributes and the relationship between entities into relational model.The following conversion principle.1. Entity type transformation: an entity type is transformed into a relational schema.Entity is the relationship of attribute, the entitys code is the relationship between code.2. Contact type conversion, do different treatment according to different situations.(1) a 1:1 ties can be converted into a separate relational schema, can also be a merger with arbitrary end corresponding relational schema.If the relationship is converted to an independent mode, is linked to the contact of each entity code and contact properties of itself are converted into relationship, each entity code is the relationship between the candidate code.If a merger with one end entities corresponding relational schema, you need to add another attribute in the relational schema of a relational schema attribute code and the link itself.2 a 1: N link can be converted into a separate relational schema, can also be a merger with n-terminal corresponding relational schema.If the relationship is converted to an independent mode, is linked to the contact of each entity code and contact properties of itself are converted into relationship, and the relationship between the code for n-terminal entity code.(3) a M: N relationship into a pattern.Linked to the contact of each entity code for each entity code combination.(4) three or more than a multiple connections between the entity can be converted into a relational schema.Linked to the multiple link code of each entity and contact itself are converted into relations of attribute, and the relationship between the code for each entity code combination.5 with the same code of relational schema can be merged.The design of table 1.1(1) the User, record the basic information of the User;(2) UserRole, record the user role, different roles have different permissions;(3) UserRights, record the user can have permissions;(4) the Administration, the basic information of the record administrator, the administrator has all permissions, and can change the user rights;(5) OverTimeRecord, records have been extended to borrow books information;(6) LostRecord, book information records have been lost;(7) BorrowRecord, record book lending;(8) Book, record the basic information of the Book;(9) Library, the basic information of the record books branch;(10) BookCategory, record books category;(11) BookKind, record the kinds of books;(12) SystemLog, log records system;1.1.1 user table表格 01 user表字段名数据类型字段说明备注UserIDint用户编号PKUserLogNamenvarchar用户登录名UserNamenvarchar用户姓名UserSexchar用户性别UserRoleint用户所属角色FK，关联角色表中的角色编号 UserPhonenvarchar用户电话UserEmailnvarchar用户邮箱UserPassnvarchar用户登录密码UserIsBorrowint用户是否可借阅书籍值为1时可借，否则不可借Database diagramUsed to store the User entity class User list.UserID items in a list items is User table primary key for the uniquely identifies a User and UserRole UserRole items from the introduction of the foreign key in the table.Used to store the administrator of the entity class Administration tables.AdminID is Administration in table item tables primary key.Used to store all the user roles UserRole table.RoleID in table entries is the primary key table UserRole, introduce the foreign key UserRights RoleRights from table.Used to store user permissions UserRights tables.In table item RightsID UserRights tables primary key.Entity class Book table for storing books.Table of BookID is a primary key is used to uniquely identifies a book, BookKind BookKind introduced foreign key in the table, BookLibary items from BookLibary introducing foreign key in the table, BookCategory