- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Bus Ticket Booking System Activity Diagram
This is the Activity UML diagram of Bus Ticket Booking System which shows the flows between the activity of Customer, Booking, Bus, Ticket, Route. The main activity involved in this UML Activity Diagram of Bus Ticket Booking System are as follows:
- Customer Activity
- Booking Activity
- Bus Activity
- Ticket Activity
- Route Activity
Features of the Activity UML diagram of Bus Ticket Booking System
- Admin User can search Customer, view description of a selected Customer, add Customer, update Customer and delete Customer.
- Its shows the activity flow of editing, adding and updating of Booking
- User will be able to search and generate report of Bus, Ticket, Route
- All objects such as ( Customer, Booking, Route) are interlinked
- Its shows the full description and flow of Customer, Ticket, Route, Bus, Booking
Login Activity Diagram of Bus Ticket Booking System:
This is the Login Activity Diagram of Bus Ticket 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 Bus, Customer, Booking, Route, Ticket. All the pages such as Booking, Route, Ticket are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Bus Ticket Booking System. The various objects in the Route, Bus, Customer, Booking, and Ticket 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
Bus Ticket Booking System Class Diagram
Bus Ticket Booking System Class Diagram describes the structure of a Bus Ticket Booking System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Bus Ticket Booking System are Bus, Booking, Customer, Bus Route, Ticket Booking, Seat.
Classes of Bus Ticket Booking System Class Diagram:
- Bus Class : Manage all the operations of Bus
- Booking Class : Manage all the operations of Booking
- Customer Class : Manage all the operations of Customer
- Bus Route Class : Manage all the operations of Bus Route
- Ticket Booking Class : Manage all the operations of Ticket Booking
- Seat Class : Manage all the operations of Seat
Classes and their attributes of Bus Ticket Booking System Class Diagram:
- Bus Attributes : bus_id, bus_name, bus_number, bus_seat_number, bus_ticket, bus_type, bus_description
- Booking Attributes : booking_id, booking_title, booking_type, booking_ticket, booking_date, booking_description
- Customer Attributes : customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
- Bus Route Attributes : bus_route_id, bus_route_name, bus_route_type, bus_route_description
- Ticket Booking Attributes : ticket booking_id, ticket booking_type, ticket booking_Date, ticket booking_description
- Seat Attributes : seat_id, seat_bus_id, seat_customer_id, seat_number, seat_type, seat_description
Classes and their methods of Bus Ticket Booking System Class Diagram:
- Bus Methods : addBus(), editBus(), deleteBus(), updateBus(), saveBus(), searchBus()
- Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
- Customer Methods : addCustomer(), editCustomer(), deleteCustomer(), updateCustomer(), saveCustomer(), searchCustomer()
- Bus Route Methods : addBus Route(), editBus Route(), deleteBus Route(), updateBus Route(), saveBus Route(), searchBus Route()
- Ticket Booking Methods : addTicket Booking(), editTicket Booking(), deleteTicket Booking(), updateTicket Booking(), saveTicket Booking(), searchTicket Booking()
- Seat Methods : addSeat(), editSeat(), deleteSeat(), updateSeat(), saveSeat(), searchSeat()
Class Diagram of Bus Ticket Booking System :
- Posted By: freeproject
- Comments: 0
Bus Ticket Booking System Component Diagram
This is a Component diagram of Bus Ticket Booking System which shows components, provided and required interfaces, ports, and relationships between the Ticket, Bus, Booking, Customer and Route. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Bus Ticket Booking System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Bus Ticket Booking System:
- Ticket Component
- Bus Component
- Booking Component
- Customer Component
- Route Component
Featues of Bus Ticket Booking System Component Diagram:
- You can show the models the components of Bus Ticket Booking System.
- Model the database schema of Bus Ticket Booking System
- Model the executables of an application of Bus Ticket Booking System
- Model the system's source code of Bus Ticket Booking System
- Posted By: namita
- Comments: 0
Bus Booking System Dataflow Diagram
Bus Booking System Data flow diagram is often used as a preliminary step to create an overview of the Bus without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Bus process. It contains all of the userflow and their entities such all the flow of Bus, Booking, Customer, Sales, Ticket Booking, Operators, Login. All of the below diagrams has been used for the visualization of data processing and structured design of the Bus process and working flow.
Zero Level Data flow Diagram(0 Level DFD) of Bus Booking System :
This is the Zero Level DFD of Bus Booking System, where we have eloborated the high level process of Bus. It’s a basic overview of the whole Bus Booking System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Ticket Booking,Operators and Login showing the system as a single high-level process, with its relationship to external entities of Bus, Booking and Customer. It should be easily understood by a wide audience, including Bus, Customer and Ticket Booking In zero leve DFD of Bus Booking System, we have described the high level flow of the Bus system.High Level Entities and proccess flow of Bus Booking System:
- Managing all the Bus
- Managing all the Booking
- Managing all the Customer
- Managing all the Sales
- Managing all the Ticket Booking
- Managing all the Operators
- Managing all the Login
First Level Data flow Diagram(1st Level DFD) of Bus Booking System :
First Level DFD (1st Level) of Bus 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 Bus Booking System system as a whole. It also identifies internal data stores of Login, Operators, Ticket Booking, Sales, Customer that must be present in order for the Bus system to do its job, and shows the flow of data between the various parts of Bus, Customer, Operators, Login, Ticket Booking 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 Bus.Main entities and output of First Level DFD (1st Level DFD):
- Processing Bus records and generate report of all Bus
- Processing Booking records and generate report of all Booking
- Processing Customer records and generate report of all Customer
- Processing Sales records and generate report of all Sales
- Processing Ticket Booking records and generate report of all Ticket Booking
- Processing Operators records and generate report of all Operators
- Processing Login records and generate report of all Login
Second Level Data flow Diagram(2nd Level DFD) of Bus Booking System :
DFD Level 2 then goes one step deeper into parts of Level 1 of Bus. It may require more functionalities of Bus to reach the necessary level of detail about the Bus functioning. First Level DFD (1st Level) of Bus Booking System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Login, Operators, Ticket Booking, Sales, Customer, Booking, Bus.Low level functionalities of Bus Booking System
- Admin logins to the system and manage all the functionalities of Bus Booking System
- Admin can add, edit, delete and view the records of Bus, Customer, Ticket Booking, Login
- Admin can manage all the details of Booking, Sales, Operators
- Admin can also generate reports of Bus, Booking, Customer, Sales, Ticket Booking, Operators
- Admin can search the details of Booking, Ticket Booking, Operators
- Admin can apply different level of filters on report of Bus, Sales, Ticket Booking
- Admin can tracks the detailed information of Booking, Customer, Sales, , Ticket Booking
- Posted By: freeproject
- Comments: 0
Bus Ticket Booking System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Bus Ticket Booking System Entity. The entity-relationship diagram of Bus Ticket Booking System shows all the visual instrument of database tables and the relations between Booking, Bus Route, Bus, Seat etc. It used structure data and to define the relationships between structured data groups of Bus Ticket Booking System functionalities. The main entities of the Bus Ticket Booking System are Bus, Booking, Customer, Bus Route, Ticket Booking and Seat.
Bus Ticket Booking System entities and their attributes :
- Bus Entity : Attributes of Bus are bus_id, bus_name, bus_number, bus_seat_number, bus_ticket, bus_type, bus_description
- Booking Entity : Attributes of Booking are booking_id, booking_title, booking_type, booking_ticket, booking_date, booking_description
- Customer Entity : Attributes of Customer are customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
- Bus Route Entity : Attributes of Bus Route are bus_route_id, bus_route_name, bus_route_type, bus_route_description
- Ticket Booking Entity : Attributes of Ticket Booking are ticket booking_id, ticket booking_type, ticket booking_Date, ticket booking_description
- Seat Entity : Attributes of Seat are seat_id, seat_bus_id, seat_customer_id, seat_number, seat_type, seat_description
Description of Bus Ticket Booking System Database :
- The details of Bus is store into the Bus tables respective with all tables
- Each entity (Seat, Customer, Ticket Booking, Booking, Bus) contains primary key and unique keys.
- The entity Customer, Ticket Booking has binded with Bus, Booking entities with foreign key
- There is one-to-one and one-to-many relationships available between Ticket Booking, Bus Route, Seat, Bus
- All the entities Bus, Ticket Booking, Customer, Seat are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Bus Ticket Booking System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Bus Ticket Booking System Sequence Diagram
This is the UML sequence diagram of Bus Ticket Booking System which shows the interaction between the objects of Customer, Booking, Route, Ticket, Bus. The instance of class objects involved in this UML Sequence Diagram of Bus Ticket Booking System are as follows:
- Customer Object
- Booking Object
- Route Object
- Ticket Object
- Bus Object
Login Sequence Diagram of Bus Ticket Booking System:
This is the Login Sequence Diagram of Bus Ticket Booking System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Route, Customer, Booking, Bus, Ticket. All the pages such as Booking, Bus, Ticket are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Bus Ticket Booking System. The various objects in the Bus, Route, Customer, Booking, and Ticket 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 Bus Ticket Booking System which shows the interaction between the objects of Customer, Booking, Route, Ticket, Bus. The instance of class objects involved in this UML Sequence Diagram of Bus Ticket Booking System are as follows:
- Customer Object
- Booking Object
- Route Object
- Ticket Object
- Bus Object
- Posted By: freeproject
- Comments: 0
Bus Ticket Booking System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Bus Ticket Booking System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Bus Ticket Booking System. The main actors of Bus Ticket Booking System in this Use Case Diagram are: Super Admin, System User, Agent, Customer, who perform the different type of use cases such as Manage Bus, Manage Booking, Manage Customer, Manage Sales, Manage Ticket Booking, Manage Operators, Manage Users and Full Bus Ticket Booking System Operations. Major elements of the UML use case diagram of Bus Ticket Booking System are shown on the picture below.
The relationships between and among the actors and the use cases of Bus Ticket Booking System:
- Super Admin Entity : Use cases of Super Admin are Manage Bus, Manage Booking, Manage Customer, Manage Sales, Manage Ticket Booking, Manage Operators, Manage Users and Full Bus Ticket Booking System Operations
- System User Entity : Use cases of System User are Manage Bus, Manage Booking, Manage Customer, Manage Sales, Manage Ticket Booking, Manage Operators
- Agent Entity : Use cases of Agent are Book Customer Tickets, View Booking History, Booking Payments
- Customer Entity : Use cases of Customer are Search Bus, Book Tickets, Make Payments
Use Case Diagram of Bus Ticket Booking System :
