In following UML component diagram for a Library Management System, the process of checking a user's rental history before renting out a new book is shown. Dotted-Arrowed lines represent dependencies between components, with the Rental History component dependent on the Member component. The rental history component checks for unpaid dues or if the member has reached the maximum rental limit. If allowed, the transaction for book rental is executed, taking the Member details and Rental History as required interfaces. Also, the book status is updated in the Inventory Management System.
