![use case diagram for ebook management system use case diagram for ebook management system](https://sourcemaking.com/files/sm/images/uml/img_31.jpg)
![use case diagram for ebook management system use case diagram for ebook management system](https://www.researchgate.net/profile/Emmanuel-Renaux/publication/228987707/figure/fig1/AS:340723883888654@1458246312327/Use-case-diagram-of-the-Hotel-room-management-system_Q640.jpg)
The implementation details are left as an exercise for additional specification, but this indicates that the in order to either check out a book or place a reservation, the librarian must first look up the book. Both checking out books and recording reservations use the look up book use case, but add additional behaviors. In this example, the Librarian can perform three functions - looking up books, checking out books, and recording reservations. I'm not sure that this is what you are going for. However, the search functionality is not available as a stand-alone entity. Both examples require the librarian to look up the book using the information provided by the member. In this example, the Librarian can perform two functions - check out a book or reserve a book.
#Use case diagram for ebook management system software#
It appears that the person actually interacting with the software is not the library member, but the librarian. In both, I changed the actor from "Member" to "Librarian". Looking at your particular example, I developed two use case models that I feel are more appropriate. In this type of relationship, the included use case is usually not available as a stand-alone use case. The specific behavior is not important, but the end result is, which means that the included use case could have a different implementation, but the same steps and end result. The include relationship is used when one use case includes the functionality of another use case. This also indicates some level of reuse between the features. Note that it's not required that an extension actually be executed - it's just a possibility. Then, depending on what happens during execution of that one use case, one or more other use cases could possibly be executed. In this situation, the base case would be executed. The extend relationship is used when one use case adds behavior to another use case. There are two relationships in a use case diagram - include and extend.