Book Management system design diagram

Book Management system design diagram

System Requirements:

The librarian can browse, inquire, statistic, add the basic information of borrowing books and delete the basic information of the books that have been returned, but can not delete and modify the books related information which has been borrowed, when deleting the basic information record of a book borrowing, it should realize the cascade delete of the book borrower's borrowing record. This function realizes the management and statistics of the book information.

The library administrator has the highest amount of information, data security and confidentiality requirements. This function realizes the management and statistics of library information, borrower information, information about the overall lending situation, and the information of staff and management personnel to view and maintain. The librarian can browse, query, add, delete, modify, statistics the basic information of the book, browse, query, statistics, add, delete and modify the basic information of the book borrower, browse, inquire, statistics library borrowing information, but can not add, delete and modify lending information, This part of the functionality should be performed by the library staff information manager. However, when deleting the basic information record of a book borrower, it should realize the cascade deletion of the book borrower's borrowing record, and should also have the report of generating the reminder book. and print out the function.

According to demand, make paper like:

1. Use case diagram:

2. Activity diagram:

3. Class Diagram:

　　

4. Flowchart:

Summarize:

In software design, various diagrams are more important than documents.

The diagram can directly react to the construction of the software. Especially in object-oriented software design.

Graphs allow us to intuitively understand the direct interactions and relationships of each class and object.

Book Management system design diagram