Booking System Use Case Diagram
Activity diagram for admin login 3 2 1 6.
Booking system use case diagram. The use case diagram for a hotel reservation system includes the following use cases. Booking manage use case name booking manage goal view customer booking payment status primary actors admin 65 secondary actors none precondition login to the system. Order room cancel reservation add room add room type remove room remove room type add room photo remove room photo check in check out ask late check out book room issue card reset card check late check out availability activate late check out.
Use pdf export for high quality prints and svg export for large sharp images or embed your diagrams anywhere with the creately viewer. Below are the use case description and participating actors and roles. Use case description for uc 005 63 figure 50.
System sequence diagram for admin login 64 figure 51. The various participants of the same are detailed below actors registered user visitor admin the corresponding use cases for these actors are. It represents the methodology used in system analysis to identify clarify and organize system requirements of hotel booking system.
Reserve rooms at a hotel you can edit this template and create your own diagram creately diagrams can be exported and added to word ppt powerpoint excel visio or any other document. Use pdf export for high quality prints and svg export for large sharp images or embed your diagrams anywhere with the creately viewer. A use case is a functionality of how the system works it describes the interaction between an actor and the system.
This use case diagram is a graphic depiction of the interactions among the elements of hotel booking system. Participating actors and roles. An association describes the relationship between an actor and a business use case in the use case diagram.
Below is the use case diagram for this project hotel reservation system. This is not a must but doing so makes the whole use case diagram well organized. This use case diagram uses system boundary and package shapes in organizing the use cases.