UML Analysis and Design of B/S-based library management system

[Guide] analyzes the Book Management System Based on B/S mode, and uses the static and dynamic model diagrams of UML to visually model the system analysis results, and General demonstration of the system model diagram.

　1 Preface

Using computer software to manage books is part of computer applications. In order to achieve rapid retrieval, high reliability, large storage capacity, long life, and low cost of books, it can greatly improve the efficiency of book management and is also an inevitable trend of information and normalization management of book management.

To meet the functional requirements of users for the effective use and management of library resources, modeling technology is used to describe the library management resources in an object-oriented manner. Before the implementation of specific system functions, it is necessary to establish a system model. The system model is built using a visual, flexible, and unified modeling language for analysis, design, and development of the system. In addition, we recommend that you use the B/S (Brower/Server) System Structure Based on Component Technology in combination with the most popular browser-based data management mode.

2. Case Analysis of the Library Management System

To develop a software system, you must first analyze the requirements of the software system. The task is to describe the functions and performance of the target system in depth, determine the limits of software design and Interface Details between the software and other system elements, and define other validity requirements of the software. The purpose of using UML (Unified Modeling Language) can capture the functional requirements and Analysis of the System, extract classes in the developed system field, and describe the cooperation between them, on the basis of the system's OOA (object-oriented analysis: object-oriented analysis), the system is designed with the object-oriented design: object-oriented design ).

The use case diagram of UML describes the functional requirements of users in detail and accurately, so that the system responsibilities are clearly put in place and lays the foundation for UML to model the system, the construction and development of other model diagrams depend on the content described in the use case diagram until the system can implement the functions described in the use case diagram. The Use Case chart describes three types of users: readers, librarians, and system administrators. There are multiple readers, several librarians, and one system administrator. For the system, readers can query their own borrowing conditions, query books in different categories, and log on to the renewal book if the renewal period cannot exceed one operation. The librarians are mainly engaged in the following daily operations: book ordering, new book verification, bibliography entry, Book Registration, reader information management, borrowing book registration, book information cancellation, and reader information cancellation, the system administrator manages the system related matters of books, such as permission maintenance, log maintenance, addition and deletion of users, and management of system Background Data. The relationships between use cases, between users and use cases, and between use cases are shown in 1.

 

　　　　　　　　　　　　　　Figure 1: Analysis of Book Management Use Cases

3. Static System Modeling

Based on case analysis, you can establish a static data model of the system as needed, that is, to create a system class diagram and related relationships and methods. In object-oriented analysis, only objects related to the Problem description domain and system functions are considered. During the analysis of the system, the class objects of the system are abstracted into two aspects: library management and book circulation. These two parts can be divided into the following categories: Library Class (lib_book), graph class (lib_category), book class (lib_order), Report class (lib_form), reader class (lib_reader) lib_cirbook, lib_department, and lib_publish. We can use simple associations between these classes for a brief expression. 2. It is a static library management class chart. In this figure, each online line with direct and multiple associations has identified multiple features, which provides better reference value for future programming, it also lays the foundation for uniformity of classes throughout the development.

 

　　　　　　　　　　　　　　　Figure 2: static library management class diagram

4. System Dynamic Modeling

After observing the static structure of the simple relationship between objects and objects at a certain time point of the system, we should pay attention to the changes of objects and their relationships at any time point, these situations can be visually described using the dynamic model of UML, and can be described using the state diagram in UML. In the state diagram, the state of the system at each time point is abstracted into states and events, A network is formed to describe the dynamic behavior of each type of objects. It is a summary of the attribute features at a certain time point, and there is a migration between each State, the migration indicates when such objects will respond to what events occur inside and outside the system. The state chart design is generally expressed based on the refined sequence diagram of the operation sequence. Here, we take the borrowing state chart as an example. After the above Object-Oriented Analysis and Design and grasping the static structure of the system, we will establish a logical view of the system's dynamic data, as shown in figure 3, with this as the point, you can establish the State Process Analysis of the entire system, which is not described here.

 

　　　　　　　　　　　　　　　　Figure 3: borrowing status chart

5. B/S-based System Structure

After completing the system case analysis, modeling static data description, and State control of local dynamic data, the system basically master the process of Logical Data Processing. In the end, to become a system management system, we need to grasp the acquisition, processing and storage of system data. In B/S-based software development, its architecture is generally divided into three layers using component technology, browser layer, Web Logic processing layer and database management layer. Here, we recommend that you use Java-based object-oriented development technology to run the designed logical components and Data Access Components in the runtime environment of JavaBean and COM + combinations, underlying data processing uses Oracle 9i, which is secure and stable in data management. This not only enhances the security of system access data, but also supports concurrent, remote, and cross-platform access to the background database. The database management layer also uses the JavaBean object component to access the background database service. The entire logic process is shown in step 4.

 

5. B/S-based System Structure

After completing the system case analysis, modeling static data description, and State control of local dynamic data, the system basically master the process of Logical Data Processing. In the end, to become a system management system, we need to grasp the acquisition, processing and storage of system data. In B/S-based software development, its architecture is generally divided into three layers using component technology, browser layer, Web Logic processing layer and database management layer. Here, we recommend that you use Java-based object-oriented development technology to run the designed logical components and Data Access Components in the runtime environment of JavaBean and COM + combinations, underlying data processing uses Oracle 9i, which is secure and stable in data management. This not only enhances the security of system access data, but also supports concurrent, remote, and cross-platform access to the background database. The database management layer also uses the JavaBean object component to access the background database service. The entire logic process is shown in step 4.