This is a project done when sophomore training learning JavaSE, now sorted out small partners need to learn.
A. Demand
1. Management also borrow books
For books add, delete, search, change, generate a corresponding library, but also record book
2. User management
Increase the user points, information, library and other times, change.
3. database (MySQL) store user information, book information and the reservation information record table library book.
II. Requires entity classes
User (user, administrator), books, appointment, book circulation records
III. Uses a three-tier architecture
IV. Item Function Display
1. The main interface
2. The administrator interface
3. The administrator after successful login interface
4. Library Management Interface
5. User Management Interface
6. User Interface of successful login
7. Personal information interface
8. The book interface
9. View Book Information
V. Features
1. First, we library management system is divided into two kinds of levels of VIP and ordinary users, ordinary users can only borrow three books, VIP users can borrow 5, where ordinary users and VIP users to borrow books under my demo process
(1) Common User library
(2) VIP user library
2. Also book process, when we borrowed library books will generate a record when we click on the book will also show that we also need books, but also books successful user points plus 1, as shown below
3. Review the book also records Click to view the personal information also borrow a book you can see his record library records, as shown below
4. appointment books, when stacks of books for this time of 0:00 we can not borrow, and can only go to the appointment books or books was also added to the number of books you can borrow, and will remind you when you log can borrow your appointment books. If we make an appointment books others already booked we will not be able to make an appointment (in real life this logic is wrong, a book should be more than a personal appointment, but I tried to get this the wrong here under, you need to change, then you can follow to realize their own logic)
5. appointment reminders, we manually go into the database ID number of books the books of 7 to 1, to see whether there will be an appointment reminder.
Then we login ID 7 users to see lc
6. Next we look at the administrator to view all users borrow books also record, click User Management, view the user also borrow books, view all library records, as shown below
VI. Project Description Framework
We use a three-tier architecture, which built several packages were view view layer, dao logic layer, biz control layer, db.properties file to fill in the relevant content database configuration, lib folder is stored in a database and connect jar to write a jar package called jdbcUtil (before I wrote an article about how to connect to the database JDBC packaged into a utility class https://blog.csdn.net/wyf2017/article/details/79589544 )
VII. Database (my database using Navicat is built directly in there table)
We built a database where five tables are as follows
(1) administrators
(2) User
(3) Books
(4) by also record book
(5) reserved
VIII. Summary
Is almost more than the basic content of the project, there are some features not 11 show, the junior partner needed for this project can go to download, address where https://download.csdn.net/download/wyf2017/12279569 , you can I am concerned about the number of the public for more learning resources, public concern number of links here https://blog.csdn.net/wyf2017/article/details/96638855
