Database design mainly included requirement analysis,
concept structure design stage, the logic structure design stage,physical
structure design stage,database implementation stage, database operation and
maintenance stage, there’re six steps altogether. Among them;Conceptual
structure design was the user’s data needs which was got in demand analysis
stage to be synthesize and abstracted, then turn them into a unified conceptual
model. It was mainly expressed by the Entity-Relationship model;Logical
structure design was to make sure the logical structure of database, it was to
turn E-R model which was got in the concept structure design stage into
relation model;Physical structure design stage was to choose a logical data
model which was the most suitable for applications environment for physical
structure (including storage structure and access method)
A.Concept Structure Design Through analyzing the function of
the library management information system,we could draw a conclusion that was
an entity of a system mainly includes books information entity, readers’
information entity, borrowing information entity and employee information
Figure 1. Books Information Entity E-R Diagram
Description:the book information entity recorded mainly the
basic information of a book to get data which was to meet the needs of
management . Among them, the “BookISBN” was an only standard Numbers of a legal
publication. It was considered as the entity of the primary key. “Inventory
Number” refered to how many books there were in the library. “Surplus” refered
to how many books could be lent out yet.
Figure 2. Reader Information E-R Diagram
Description:the reader information entity mainly recorded
the reader’s personal information and his borrowing state information from the
library .Among them,”ReaderID” was the main key. “LibraryCardState” displayed
if you could borrow books now. “ReaderType” showed the reader was a teacher, student
or a worker.
Figure 3. Reader Category E-R Diagram
Description:It was used to set up the restrictions about
borrowing books among different category readers. Among them ? “ReaderType” was the main key.
“DaysLimit” showed how many days could be borrowed. “NumberLimit” showed the
number of books that could be borrowed.
Figure 4. Borrow Information E-R Diagram
Description:The entity recorded which readers borrowed the
book and what the date was. Among them,”BorrowDate” said the date of lending
Figure 5. Employee Information E-R Diagram
Description:The entity said library staff’s information.
Among them,”EmployeeID” was employee numbers ,and it was primary
key;”EmployeePwd” was login password?
“EmployeePermissions” was used to determine that the employee could use which
parts of function of the system.
Design Turned above E-R diagram into relation model :
(1) Book(BookISBN ? BookClaNum ? BookTitle ? BookCategory?BookAuthor?BookPress?BookEdition? BookFormat ? BookWordNum ? BookPrice ? BookInvNum?BookSur);
(2) Reader(ReaderID ? ReaderName ? ReaderType ? LibraryCardState ? ReaderSex ? ReaderDepartment ? ReaderPhone?ReaderEmail);
(3) ReaderCategory(ReaderType ? NumbersLimit ? DaysLimit);
(5) Employee(EmpID ?
EmpName ? EmpSex ? EmpPosition?EmpTel?EmpPwd?EmpPermissions);
C. The Realization of
Database According to all of above analysis and design system database, the
lists was main used as follows:
Figure 6. Books Information Table
Figure 7. Reader Information Table
Figure 8. Reader Category Table
Figure 9. Borrow Information Table
Figure 10. Employee Information Table
Started SQL Server Management Studio Express, then connected
the server .After creating database we could get the new user list through the
analysis. It would be ok that the data was put into the corresponding list.