Development and Realization of Book Loan System Based on SSM
Description
This system is a book lending system based on the SSM environment. With the widespread use of computers, it has gradually become a symbol of modernization. In the normal operation of a library or some enterprises, or even a bookstore, it is always faced with a large amount of reader information, book information, and borrowing and returning information generated by the interaction between the two. Therefore, it is necessary to manage reader resources, book resources, borrowing information, and returning information, and to keep abreast of the changes in information in each link, and to process the resulting documents in a timely manner. In order to improve the library or enterprise internal Automated management can more quickly meet the reader's requirements and improve the efficiency of various work. Now we design corresponding systems to achieve the above purpose.
Table of Contents
Abstract
1 Introduction
2 System Requirements Analysis
3 System Detailed Design
4 System Technical Route
Summary :
Book borrowing system is an indispensable part of some units, books are indispensable spiritual food for human beings, especially for some enterprises and schools, it is particularly important. Therefore, the book lending system should be able to provide users with sufficient information and quick query methods. However, people have always used traditional manual methods to manage books. This management method has many shortcomings, such as low efficiency and poor confidentiality. In addition, a large amount of documents and data will be generated over a long period of time, which brings many difficulties to book borrowing. With the continuous development of computer technology, the use of computers to manage book resource information will provide users with more convenience. (The main function of the book lending system is to realize the automation of the management of book lending and return within the library or enterprise. Around this main function, this system involves the following core functions: book lending, book return.)
1 Introduction
1.1 System Background History The history
of the development of the book loan management system can be traced back to the late 1960s. At that time, computer technology had entered the practical stage, and large libraries used manual search for book information or statistical borrowing information, which was time-consuming, laborious, and very error-prone. In order to solve this contradiction, the first generation of book borrowing management system came into being. At that time, due to the limitations of technical conditions and requirements, there were very few users. Its appearance showed a bright prospect for the management of book borrowing, that is, the high speed and automation of the computer were used to replace the huge manual workload, and the high accuracy of the computer was used to Avoid manual errors and errors.
1.2 System Objectives
To solve the problems of slow retrieval, low efficiency, large
book return and borrowing, large book statistical workload, and the inability to complete timely updating of book collections, many small book management is still caused by manual management . The system realizes the convenience of user borrowing Return books to facilitate librarians to add, delete, and modify book information.
2 System requirements analysis
Demand analysis is mainly based on the following aspects of the book lending system:
2.1 User needs analysis
2.1.1 User objects
(1) Librarian: can create, modify, and delete reader information and book information, namely reader management and book management,
borrow and return books Fines, etc. are loan management.
(2) Readers: log in through the Internet to check book information and personal borrowing information, and can also apply for book renewal on their own if they meet the conditions for renewal.
2.1.2 Organizational structure
The user group of the book lending system is not very limited, so the user is not limited to the organizational structure, and can be used in the name of an individual, or as a school unit or company user.
2.1.3 Basic functions
(1) System user management: system login, password modification, administrator addition, etc.
(2) Book information management: add, modify, delete, and query book information.
(3) Reader information management: add, modify, delete, and query reader information.
(4) Borrowing information management: adding, modifying, deleting, and inquiring information.
(5) Book return information management: add, modify, delete, and query information.
2.2 Performance requirements analysis
2.2.1 Software and hardware performance requirements
(1) Server-side operating system: cross-platform system independent of operating system, client Windows XP and above.
(2) The application database is the open source free relational database MySql.
(3) Open source free Tomcat server software.
(4) Client running tools: Firefox, Google Chrome, etc.
(5) Development tool: Eclipse.
2.2.2 Security requirements
(1) The system should authenticate the logged-in user to determine whether the user is an authorized user.
(2) The system should have a log record of the operations of different users on the system.
2.2.3 Integrity requirements
(1) Domain integrity: the integrity of various information records, the content of the information record cannot be empty
(2) entity integrity: unique primary key
2.2.4 system operation requirements
(1) normal user login, In order to operate the book borrowing system.
(2) Each operating system of the user can give timely feedback, even if it is an error or illegal operation, it should return the relevant prompt information to help the user perform the correct operation.
(3) When running, you need to open the connection between the server and the database.
3 Detailed system design
3.1 Generate user activity diagram
According to the processing requirements of the overall information needs, analyze and generate the global business flow chart of the system. The user operation process is shown in the figure:
Description: The user enters the user name and password on the system login interface, and the system is related to the background database For comparison, if there is no correct input, relevant prompts will be given.
Generate main partial business flow charts for different business logics, mainly including "book information management", "reader information management", book borrowing and return management and other business flow charts.
(1) There are two types of "information management", one: book information management, and two: reader information management.
3.2 Generate system functional structure diagram
According to the activities of authorized users and business flow charts, the system functional structure diagram of Figure 3-3 is obtained, as shown in the figure:
According to the business flow chart and the functional structure diagram of the system, the interface design requirements are described as follows:
( 1) Book information management: add, modify, delete, and inquire about book information.
(3) Reader information management: add, modify, delete, and query reader information.
(4) Borrowing information management: adding, modifying, deleting, and inquiring information.
(5) Book return information management: add, modify, delete, and query information.
4 System technical route
4.1 Application development language-Java
in the design and development of the system, based on the consideration of flexibility, chose to use B / S mode development. Using Java language as its background processing program, its platform independence, support for Web development and its powerful functions can fully meet the needs of this development. For example, this time is to use a combination of Servlet and JSP to develop the Web application; at the same time, Java also contains a lot of class libraries, by calling these class libraries, not only to facilitate the developers' programming, but also in the development of the project system Save a lot of time. The reason for adopting Java is not only because it provides support for multi-threading, but also provides support for network communication. In addition, the garbage collector is its most important advantage, which can avoid the need for project developers. To care about memory management issues. The code of the system is divided into two parts, the main Java code is concentrated in the Servlet layer, and the code part of JSP only involves a small amount of Java code.
4.2 Web application interface development environment—
JSP technology JSP is the reference program interface development technology of my choice. Generally speaking, it is because it can first write java code in html, which is more convenient. Second, the inserted Java program segment can operate the database , Redirect web pages, etc., to achieve the functions required to build dynamic web pages.
4.3 Database development environment-MySql database
Currently, the mainstream relational databases are Oracle, SQLServer, MySql, etc. Because Oracle requires money, the cost is higher; SQLServer is less cross-platform; MySql is unique compared to them:
① MySql is open source, Free when used.
② Support multiple column types, such as: CHAR, VARCHAR, TEXT, BLOB, DATE, TIME, DATETIME, TIMESTAMP, YEAR, etc.
③ All columns have default values.
④ It can handle large-scale data with tens of millions of records;
⑤ It is simple and convenient to install, and it is compact compared to other databases, and has the largest cost performance compared to Oracle and SQLServer in terms of portability and operating efficiency. In addition, MySql is simpler than Oracle and SQLServer in debugging, management and optimization.
4.4 Web Application Server—
The specifications of Tomcat Servlet and JSP can be reflected in the Tomcat server to a great extent. Simply put, the result of Tomcat operation is the combined effect of Servlet and JSP.
The Tomcat server configuration is simple and easy to deploy and has a strong portability, which is sought after by many developers. And because Tomcat is open source, free, and its flexibility, stability, and security can be guaranteed, so I decided to use Tomcat as the server for this development.
Controller and mybatisMapper
