Hall Booking System UML Diagram

Posted By freeproject on March 19, 2018

Hall Booking System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Hall Booking System which shows the flows between the activity of Booking, Hall, Payment, Inventory, Customers. The main activity involved in this UML Activity Diagram of Hall Booking System are as follows:

  • Booking Activity
  • Hall Activity
  • Payment Activity
  • Inventory Activity
  • Customers Activity

Features of the Activity UML diagram of Hall Booking System

  • Admin User can search Booking, view description of a selected Booking, add Booking, update Booking and delete Booking.
  • Its shows the activity flow of editing, adding and updating of Hall
  • User will be able to search and generate report of Payment, Inventory, Customers
  • All objects such as ( Booking, Hall, Customers) are interlinked
  • Its shows the full description and flow of Booking, Inventory, Customers, Payment, Hall
Hall Booking System Activity Diagram

Hall Booking System Class Diagram

Posted By freeproject on August 2, 2017

Hall Booking System Class Diagram describes the structure of a Hall Booking System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Hall Booking System are Hall, Booking, Payment, Customers, Inventory, Bill.

Classes of Hall Booking System Class Diagram:

  • Hall Class : Manage all the operations of Hall
  • Booking Class : Manage all the operations of Booking
  • Payment Class : Manage all the operations of Payment
  • Customers Class : Manage all the operations of Customers
  • Inventory Class : Manage all the operations of Inventory
  • Bill Class : Manage all the operations of Bill

Classes and their attributes of Hall Booking System Class Diagram:

  • Hall Attributes : hall_id, hall_name, hall_place, hall_charge, hall_type, hall_description
  • Booking Attributes : booking_id, booking_title, booking_type, booking_hall, booking_date, booking_description
  • Payment Attributes : payment_id, payment_customer_id, payment_date, payment_amount, payment_description
  • Customers Attributes : customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Inventory Attributes : inventory_id, inventory_items, inventory_number, inventory_type, inventory_description
  • Bill Attributes : bill_id, bill_customer_id, bill_number, bill_type, bill_receipt, bill_description

Classes and their methods of Hall Booking System Class Diagram:

  • Hall Methods : addHall(), editHall(), deleteHall(), updateHall(), saveHall(), searchHall()
  • Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
  • Payment Methods : addPayment(), editPayment(), deletePayment(), updatePayment(), savePayment(), searchPayment()
  • Customers Methods : addCustomers(), editCustomers(), deleteCustomers(), updateCustomers(), saveCustomers(), searchCustomers()
  • Inventory Methods : addInventory(), editInventory(), deleteInventory(), updateInventory(), saveInventory(), searchInventory()
  • Bill Methods : addBill(), editBill(), deleteBill(), updateBill(), saveBill(), searchBill()

Class Diagram of Hall Booking System :

Class Diagram Image: 
Hall Booking System Class Diagram

Hall Booking System Component Diagram

Posted By freeproject on February 8, 2018

This is a Component diagram of Hall Booking System which shows components, provided and required interfaces, ports, and relationships between the Payment, Booking, Inventory, Hall and Customers. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Hall Booking System UML component diagram, describes the organization and wiring of the physical components in a system.

Components of UML Component Diagram of Hall Booking System:

  • Payment Component
  • Booking Component
  • Inventory Component
  • Hall Component
  • Customers Component

Featues of Hall Booking System Component Diagram:

  • You can show the models the components of Hall Booking System.
  • Model the database schema of Hall Booking System
  • Model the executables of an application of Hall Booking System
  • Model the system's source code of Hall Booking System
Component Diagram: 

Hall Booking System Dataflow Diagram

Posted By namita on July 4, 2017

Hall Booking System Data flow diagram is often used as a preliminary step to create an overview of the Hall without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Hall process. It contains all of the userflow and their entities such all the flow of Hall, Booking, Payment, Customers, Booking Dates, Inventory, Login. All of the below diagrams has been used for the visualization of data processing and structured design of the Hall process and working flow.


Zero Level Data flow Diagram(0 Level DFD) of Hall Booking System :

This is the Zero Level DFD of Hall Booking System, where we have eloborated the high level process of Hall. It’s a basic overview of the whole Hall Booking System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Booking Dates,Inventory and Login showing the system as a single high-level process, with its relationship to external entities of Hall,Booking and Payment. It should be easily understood by a wide audience, including Hall,Payment and Booking Dates In zero leve DFD of Hall Booking System, we have described the high level flow of the Hall system.

High Level Entities and proccess flow of Hall Booking System:

  • Managing all the Hall
  • Managing all the Booking
  • Managing all the Payment
  • Managing all the Customers
  • Managing all the Booking Dates
  • Managing all the Inventory
  • Managing all the Login
Zero Level Data flow Diagram(0 Level DFD) of Hall Booking System

First Level Data flow Diagram(1st Level DFD) of Hall Booking System :

First Level DFD (1st Level) of Hall Booking System shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the Hall Booking System system as a whole. It also identifies internal data stores of Login, Inventory, Booking Dates, Customers, Payment that must be present in order for the Hall system to do its job, and shows the flow of data between the various parts of Hall, Payment, Inventory, Login, Booking Dates of the system. DFD Level 1 provides a more detailed breakout of pieces of the 1st level DFD. You will highlight the main functionalities of Hall.

Main entities and output of First Level DFD (1st Level DFD):

  • Processing Hall records and generate report of all Hall
  • Processing Booking records and generate report of all Booking
  • Processing Payment records and generate report of all Payment
  • Processing Customers records and generate report of all Customers
  • Processing Booking Dates records and generate report of all Booking Dates
  • Processing Inventory records and generate report of all Inventory
  • Processing Login records and generate report of all Login
First Level Data flow Diagram(1st Level DFD) of Hall Booking System

Second Level Data flow Diagram(2nd Level DFD) of Hall Booking System :

DFD Level 2 then goes one step deeper into parts of Level 1 of Hall. It may require more functionalities of Hall to reach the necessary level of detail about the Hall functioning. First Level DFD (1st Level) of Hall Booking System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Login, Inventory, Booking Dates, Customers, Payment, Booking, Hall.

Low level functionalities of Hall Booking System

  • Admin logins to the system and manage all the functionalities of Hall Booking System
  • Admin can add, edit, delete and view the records of Hall, Payment, Booking Dates, Login
  • Admin can manage all the details of Booking, Customers, Inventory
  • Admin can also generate reports of Hall, Booking, Payment, Customers, Booking Dates, Inventory
  • Admin can search the details of Booking, Booking Dates, Inventory
  • Admin can apply different level of filters on report of Hall, Customers, Booking Dates
  • Admin can tracks the detailed information of Booking, Payment, Customers, , Booking Dates
Second Level Data flow Diagram(2nd Level DFD) of Hall Booking System

Hall Booking System ER Diagram

Posted By freeproject on July 17, 2017

This ER (Entity Relationship) Diagram represents the model of Hall Booking System Entity. The entity-relationship diagram of Hall Booking System shows all the visual instrument of database tables and the relations between Booking, Customers, Hall, Bill etc. It used structure data and to define the relationships between structured data groups of Hall Booking System functionalities. The main entities of the Hall Booking System are Hall, Booking, Payment, Customers, Inventory and Bill.

Hall Booking System entities and their attributes :

  • Hall Entity : Attributes of Hall are hall_id, hall_name, hall_place, hall_charge, hall_type, hall_description
  • Booking Entity : Attributes of Booking are booking_id, booking_title, booking_type, booking_hall, booking_date, booking_description
  • Payment Entity : Attributes of Payment are payment_id, payment_customer_id, payment_date, payment_amount, payment_description
  • Customers Entity : Attributes of Customers are customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Inventory Entity : Attributes of Inventory are inventory_id, inventory_items, inventory_number, inventory_type, inventory_description
  • Bill Entity : Attributes of Bill are bill_id, bill_customer_id, bill_number, bill_type, bill_receipt, bill_description

Description of Hall Booking System Database :

  • The details of Hall is store into the Hall tables respective with all tables
  • Each entity (Bill, Payment, Inventory, Booking, Hall) contains primary key and unique keys.
  • The entity Payment, Inventory has binded with Hall, Booking entities with foreign key
  • There is one-to-one and one-to-many relationships available between Inventory, Customers, Bill, Hall
  • All the entities Hall, Inventory, Payment, Bill are normalized and reduce duplicacy of records
  • We have implemented indexing on each tables of Hall Booking System tables for fast query execution.
Hall Booking System ER Diagram

Hall Booking System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Hall Booking System which shows the interaction between the objects of Customers, Booking, Hall, Payment, Inventory. The instance of class objects involved in this UML Sequence Diagram of Hall Booking System are as follows:

  • Customers Object
  • Booking Object
  • Hall Object
  • Payment Object
  • Inventory Object

This is the UML sequence diagram of Hall Booking System which shows the interaction between the objects of Customers, Booking, Hall, Payment, Inventory. The instance of class objects involved in this UML Sequence Diagram of Hall Booking System are as follows:

  • Customers Object
  • Booking Object
  • Hall Object
  • Payment Object
  • Inventory Object

Hall Booking System Use Case Diagram

Posted By freeproject on July 24, 2017

This Use Case Diagram is a graphic depiction of the interactions among the elements of Hall Booking System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Hall Booking System. The main actors of Hall Booking System in this Use Case Diagram are: Super Admin, System User, Hall Owner, Customer, who perform the different type of use cases such as Manage Hall, Manage Booking, Manage Payment, Manage Customers, Manage Booking Dates, Manage Inventory, Manage Users and Full Hall Booking System Operations. Major elements of the UML use case diagram of Hall Booking System are shown on the picture below.

The relationships between and among the actors and the use cases of Hall Booking System:

  • Super Admin Entity : Use cases of Super Admin are Manage Hall, Manage Booking, Manage Payment, Manage Customers, Manage Booking Dates, Manage Inventory, Manage Users and Full Hall Booking System Operations
  • System User Entity : Use cases of System User are Manage Hall, Manage Booking, Manage Payment, Manage Customers, Manage Booking Dates, Manage Inventory
  • Hall Owner Entity : Use cases of Hall Owner are Check Requests, Approve Requests, Create Itiniary, Create Invoice, Collect Payments
  • Customer Entity : Use cases of Customer are Search Halls, View Reviews, Book Hall, Make Payments

Use Case Diagram of Hall Booking System :

Hall Booking System Use Case Diagram