- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Hotel Booking System Activity Diagram
This is the Activity UML diagram of Hotel Booking System which shows the flows between the activity of Hotel, Rooms, Services, Customers, Booking. The main activity involved in this UML Activity Diagram of Hotel Booking System are as follows:
- Hotel Activity
- Rooms Activity
- Services Activity
- Customers Activity
- Booking Activity
Features of the Activity UML diagram of Hotel Booking System
- Admin User can search Hotel, view description of a selected Hotel, add Hotel, update Hotel and delete Hotel.
- Its shows the activity flow of editing, adding and updating of Rooms
- User will be able to search and generate report of Services, Customers, Booking
- All objects such as (Hotel, Rooms, Booking) are interlinked
- Its shows the full description and flow of Hotel, Customers, Booking, Services, Rooms
Login Activity Diagram of Hotel Booking System:
This is the Login Activity Diagram of Hotel Booking System, which shows the flows of Login Activity, where admin will be able to login using their username and password. After login user can manage all the operations on Services, Hotel, Rooms, Booking, Customers. All the pages such as Rooms, Booking, Customers are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Hotel Booking System. The various objects in the Booking, Services, Hotel, Rooms, and Customers page—interact over the course of the Activity, and user will not be able to access this page without verifying their identity.
- Posted By: freeproject
- Comments: 0
Hotel Booking System Class Diagram
Hotel Booking System Class Diagram describes the structure of a Hotel Booking System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Hotel Booking System are Payments, Booking, Customers, Hotel, Rooms, Services.
Classes of Hotel Booking System Class Diagram:
- Payments Class : Manage all the operations of Payments
- Booking Class : Manage all the operations of Booking
- Customers Class : Manage all the operations of Customers
- Hotel Class : Manage all the operations of Hotel
- Rooms Class : Manage all the operations of Rooms
- Services Class : Manage all the operations of Services
Classes and their attributes of Hotel Booking System Class Diagram:
- Payments Attributes : payment_id, payment_customer_id, payment_date, payment_amount, payment_description
- Booking Attributes : booking_id, booking_title, booking_type, booking_date, booking_description
- Customers Attributes : customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
- Hotel Attributes : hotel_id, hotel_name, hotel_type, hotel_rent, hotel_description, hotel_address
- Rooms Attributes : room_id, room_hotel_id, room_number, room_category, room_type, room_description
- Services Attributes : service_id, service_hotel_id, service_name, service_type, service_description
Classes and their methods of Hotel Booking System Class Diagram:
- Payments Methods : addPayments(), editPayments(), deletePayments(), updatePayments(), savePayments(), searchPayments()
- Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
- Customers Methods : addCustomers(), editCustomers(), deleteCustomers(), updateCustomers(), saveCustomers(), searchCustomers()
- Hotel Methods : addHotel(), editHotel(), deleteHotel(), updateHotel(), saveHotel(), searchHotel()
- Rooms Methods : addRooms(), editRooms(), deleteRooms(), updateRooms(), saveRooms(), searchRooms()
- Services Methods : addServices(), editServices(), deleteServices(), updateServices(), saveServices(), searchServices()
Class Diagram of Hotel Booking System :
- Posted By: freeproject
- Comments: 0
Hotel Booking System Component Diagram
This is a Component diagram of Hotel Booking System which shows components, provided and required interfaces, ports, and relationships between the Rooms, Services, Payments, Customers and Booking. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Hotel Booking System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Hotel Booking System:
- Rooms Component
- Services Component
- Payments Component
- Customers Component
- Booking Component
Featues of Hotel Booking System Component Diagram:
- You can show the models the components of Hotel Booking System.
- Model the database schema of Hotel Booking System
- Model the executables of an application of Hotel Booking System
- Model the system's source code of Hotel Booking System
- Posted By: freeproject
- Comments: 0
Hotel Booking System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Hotel Booking System Entity. The entity-relationship diagram of Hotel Booking System shows all the visual instrument of database tables and the relations between Booking, Hotel, Payments, Services etc. It used structure data and to define the relationships between structured data groups of Hotel Booking System functionalities. The main entities of the Hotel Booking System are Payments, Booking, Customers, Hotel, Rooms and Services.
Hotel Booking System entities and their attributes :
- Payments Entity : Attributes of Payments are payment_id, payment_customer_id, payment_date, payment_amount, payment_description
- Booking Entity : Attributes of Booking are booking_id, booking_title, booking_type, booking_date, booking_description
- Customers Entity : Attributes of Customers are customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
- Hotel Entity : Attributes of Hotel are hotel_id, hotel_name, hotel_type, hotel_rent, hotel_description, hotel_address
- Rooms Entity : Attributes of Rooms are room_id, room_hotel_id, room_number, room_category, room_type, room_description
- Services Entity : Attributes of Services are service_id, service_hotel_id, service_name, service_type, service_description
Description of Hotel Booking System Database :
- The details of Payments is store into the Payments tables respective with all tables
- Each entity (Services, Customers, Rooms, Booking, Payments) contains primary key and unique keys.
- The entity Customers, Rooms has binded with Payments, Booking entities with foreign key
- There is one-to-one and one-to-many relationships available between Rooms, Hotel, Services, Payments
- All the entities Payments, Rooms, Customers, Services are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Hotel Booking System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Hotel Booking System Sequence Diagram
This is the UML sequence diagram of Hotel Booking System which shows the interaction between the objects of Hotel, Services, Booking, Rooms, Customers. The instance of class objects involved in this UML Sequence Diagram of Hotel Booking System are as follows:
- Hotel Object
- Services Object
- Booking Object
- Rooms Object
- Customers Object
Login Sequence Diagram of Hotel Booking System:
This is the Login Sequence Diagram of Hotel Booking System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Booking, Hotel, Services, Customers, Rooms. All the pages such as Services, Customers, Rooms are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Hotel Booking System. The various objects in the Customers, Booking, Hotel, Services, and Rooms page—interact over the course of the sequence, and user will not be able to access this page without verifying their identity.
This is the UML sequence diagram of Hotel Booking System which shows the interaction between the objects of Hotel, Services, Booking, Rooms, Customers. The instance of class objects involved in this UML Sequence Diagram of Hotel Booking System are as follows:
- Hotel Object
- Services Object
- Booking Object
- Rooms Object
- Customers Object
- Posted By: freeproject
- Comments: 0
Hotel Booking System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Hotel Booking System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Hotel Booking System. The main actors of Hotel Booking System in this Use Case Diagram are: Super Admin, System User, Hotel, Customer, who perform the different type of use cases such as Manage Payments, Manage Booking, Manage Customers, Manage Hotel, Manage Rooms, Manage Services, Manage Users and Full Hotel Booking System Operations. Major elements of the UML use case diagram of Hotel Booking System are shown on the picture below.
The relationships between and among the actors and the use cases of Hotel Booking System:
- Super Admin Entity : Use cases of Super Admin are Manage Payments, Manage Booking, Manage Customers, Manage Hotel, Manage Rooms, Manage Services, Manage Users and Full Hotel Booking System Operations
- System User Entity : Use cases of System User are Manage Payments, Manage Booking, Manage Customers, Manage Hotel, Manage Rooms, Manage Services
- Hotel Entity : Use cases of Hotel are Check Booking Request, Allot Rooms, Create Invoice, Collect Payments
- Customer Entity : Use cases of Customer are Search Hotels, Book Rooms, Make Payment
Use Case Diagram of Hotel Booking System :
