UML modeling design (Exercise) of the Library Management System)

1. Requirement Analysis description

The library information management system is an electronic file management system that uses computers to process a large amount of books. It mainly meets the requirements of borrowers, librarians, and system administrators. For the borrower, it mainly queries personal information, books, books that are currently being borrowed by others, borrowing books, and returning books. The librarians are the primary users of the system, the System Administrator is responsible for handling borrowing and Returning books. When a specified book is lent to a specified book, the system administrator cancels the Book Reservation. The system administrator is mainly responsible for system maintenance, including reader information management and book information management, system status maintenance.

2. Model Creation

1) create a case model

The system sets up four activists. They are people, Registrar, reader, and database. Where "people" refers to the person who has a relationship with the system. "Registrar" is the system administrator and is responsible for adding and modifying book information. "Reader" refers to all readers. Readers may borrow, continue, or repay books; database is a database object that stores various information. In addition, considering that there is still a "library administrator" role in the real library, its role is only to complete various system operations on behalf of the reader, so this activity is not set up. There are five use cases in the system. Addinfo, modifyinfo, borrow, renew, and return. Addinfo indicates that the Administrator adds the book information; modifyinfo indicates that the book information is modified; borrow indicates that the reader borrows the book; Renew indicates that the reader renews the book; return indicates that the reader returns the book.

 

The usage diagram is shown in the figure above:

 

 

System collaboration diagram:

The following figure shows the reader's collaboration by borrowing books:

 

 

 

 

The administrator can modify the reader information collaboration diagram and the reader's predefined collaboration diagram, as shown in:

 

 

 

The object diagram of the library management system is as follows:

 

 

2) 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. For example, for a static library management class chart, each online line in the figure with direct and multiple associations has indicated multiple features, which provides better reference value for future programming, it also lays the foundation for uniformity of classes throughout the development.

 

 

 

 

 

Library personnel class librarystaff System Administrator class systemmanager

Library administrator class librarymanager library leader class libratyboss

 

 

Library Resources

Bookresources

Electronic books, electronic nicresources

Book

CATEGORY magazine

 

 

Static Model:

Dynamic Model:

Addinfo activity diagram

Modifyinfo activity diagram:

Boorrow activity diagram:

Return activity diagram:

Renew activity diagram:

Library Management System Configuration map instance:

Business Object component diagram: