Ticket Reservation System UML Diagram

Posted By freeproject on March 23, 2018

Ticket Reservation System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Ticket Reservation System which shows the flows between the activity of Ticket, Booking, Train, Seats, Fare. The main activity involved in this UML Activity Diagram of Ticket Reservation System are as follows:

  • Ticket Activity
  • Booking Activity
  • Train Activity
  • Seats Activity
  • Fare Activity

Features of the Activity UML diagram of Ticket Reservation System

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

Ticket Reservation System Class Diagram

Posted By freeproject on August 2, 2017

Ticket Reservation System Class Diagram describes the structure of a Ticket Reservation System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Ticket Reservation System are Trains, Seats Availability, Fare, Stations, Booking, Passengers.

Classes of Ticket Reservation System Class Diagram:

  • Trains Class : Manage all the operations of Trains
  • Seats Availability Class : Manage all the operations of Seats Availability
  • Fare Class : Manage all the operations of Fare
  • Stations Class : Manage all the operations of Stations
  • Booking Class : Manage all the operations of Booking
  • Passengers Class : Manage all the operations of Passengers

Classes and their attributes of Ticket Reservation System Class Diagram:

  • Trains Attributes : train_id, train_name, train_number, train_seat_number, train_ticket, train_type, train_description
  • Seats Availability Attributes : seat_id, seat_train_id, seat_customer_id, seat_number, seat_type, seat_description
  • Fare Attributes : fare_id, fare_ticket_id, fare_title, fare_type, fare_description
  • Stations Attributes : station_id, station_name, station_type, station_description
  • Booking Attributes : booking_id, booking_ticket_id, booking_title, booking_type, booking_date, booking_description
  • Passengers Attributes : passenger_id, passenger_name, passenger_mobile, passenger_email, passenger_username, passenger_password, passenger_address

Classes and their methods of Ticket Reservation System Class Diagram:

  • Trains Methods : addTrains(), editTrains(), deleteTrains(), updateTrains(), saveTrains(), searchTrains()
  • Seats Availability Methods : addSeats Availability(), editSeats Availability(), deleteSeats Availability(), updateSeats Availability(), saveSeats Availability(), searchSeats Availability()
  • Fare Methods : addFare(), editFare(), deleteFare(), updateFare(), saveFare(), searchFare()
  • Stations Methods : addStations(), editStations(), deleteStations(), updateStations(), saveStations(), searchStations()
  • Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
  • Passengers Methods : addPassengers(), editPassengers(), deletePassengers(), updatePassengers(), savePassengers(), searchPassengers()

Class Diagram of Ticket Reservation System :

Class Diagram Image: 
Ticket Reservation System Class Diagram

Ticket Reservation System Component Diagram

Posted By freeproject on February 8, 2018

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

Components of UML Component Diagram of Ticket Reservation System:

  • Stations Component
  • Fare Component
  • Seats Component
  • Booking Component
  • Passengers Component

Featues of Ticket Reservation System Component Diagram:

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

Ticket Reservation System Dataflow Diagram

Posted By namita on July 11, 2017

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


Zero Level Data flow Diagram(0 Level DFD) of Ticket Reservation System :

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

High Level Entities and proccess flow of Ticket Reservation System:

  • Managing all the Trains
  • Managing all the Seats
  • Managing all the Fare
  • Managing all the Stations
  • Managing all the Booking
  • Managing all the Passengers
  • Managing all the Ticket
Zero Level Data flow Diagram(0 Level DFD) of Ticket Reservation System

First Level Data flow Diagram(1st Level DFD) of Ticket Reservation System :

First Level DFD (1st Level) of Ticket Reservation 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 Ticket Reservation System system as a whole. It also identifies internal data stores of Ticket, Passengers, Booking, Stations, Fare that must be present in order for the Ticket system to do its job, and shows the flow of data between the various parts of Trains, Fare, Passengers, 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 Ticket.

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

  • Processing Trains records and generate report of all Trains
  • Processing Seats records and generate report of all Seats
  • Processing Fare records and generate report of all Fare
  • Processing Stations records and generate report of all Stations
  • Processing Booking records and generate report of all Booking
  • Processing Passengers records and generate report of all Passengers
  • Processing Ticket records and generate report of all Ticket
First Level Data flow Diagram(1st Level DFD) of Ticket Reservation System

Second Level Data flow Diagram(2nd Level DFD) of Ticket Reservation System :

DFD Level 2 then goes one step deeper into parts of Level 1 of Ticket. It may require more functionalities of Ticket to reach the necessary level of detail about the Ticket functioning. First Level DFD (1st Level) of Ticket Reservation System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Ticket, Passengers, Booking, Stations, Fare, Seats, Trains.

Low level functionalities of Ticket Reservation System

  • Admin logins to the system and manage all the functionalities of Ticket Reservation System
  • Admin can add, edit, delete and view the records of Trains, Fare, Booking, Ticket
  • Admin can manage all the details of Seats, Stations, Passengers
  • Admin can also generate reports of Trains, Seats, Fare, Stations, Booking, Passengers
  • Admin can search the details of Seats, Booking, Passengers
  • Admin can apply different level of filters on report of Trains, Stations, Booking
  • Admin can tracks the detailed information of Seats, Fare, Stations, , Booking
Second Level Data flow Diagram(2nd Level DFD) of Ticket Reservation System

Ticket Reservation System ER Diagram

Posted By freeproject on July 17, 2017

This ER (Entity Relationship) Diagram represents the model of Ticket Reservation System Entity. The entity-relationship diagram of Ticket Reservation System shows all the visual instrument of database tables and the relations between Seats Availability, Stations, Trains, Passengers etc. It used structure data and to define the relationships between structured data groups of Ticket Reservation System functionalities. The main entities of the Ticket Reservation System are Trains, Seats Availability, Fare, Stations, Booking and Passengers.

Ticket Reservation System entities and their attributes :

  • Trains Entity : Attributes of Trains are train_id, train_name, train_number, train_seat_number, train_ticket, train_type, train_description
  • Seats Availability Entity : Attributes of Seats Availability are seat_id, seat_train_id, seat_customer_id, seat_number, seat_type, seat_description
  • Fare Entity : Attributes of Fare are fare_id, fare_ticket_id, fare_title, fare_type, fare_description
  • Stations Entity : Attributes of Stations are station_id, station_name, station_type, station_description
  • Booking Entity : Attributes of Booking are booking_id, booking_ticket_id, booking_title, booking_type, booking_date, booking_description
  • Passengers Entity : Attributes of Passengers are passenger_id, passenger_name, passenger_mobile, passenger_email, passenger_username, passenger_password, passenger_address

Description of Ticket Reservation System Database :

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

Ticket Reservation System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Ticket Reservation System which shows the interaction between the objects of Fare, Ticket, Passengers, Stations, Train. The instance of class objects involved in this UML Sequence Diagram of Ticket Reservation System are as follows:

  • Fare Object
  • Ticket Object
  • Passengers Object
  • Stations Object
  • Train Object

This is the UML sequence diagram of Ticket Reservation System which shows the interaction between the objects of Fare, Ticket, Passengers, Stations, Train. The instance of class objects involved in this UML Sequence Diagram of Ticket Reservation System are as follows:

  • Fare Object
  • Ticket Object
  • Passengers Object
  • Stations Object
  • Train Object

Ticket Reservation 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 Ticket Reservation System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Ticket Reservation System. The main actors of Ticket Reservation System in this Use Case Diagram are: Super Admin, System User, Agents, Customer, who perform the different type of use cases such as Trains, Manage Seats, Manage Fare, Manage Stations, Manage Booking, Manage Passengers, Manage Ticket, Manage Users and Full Ticket Reservation System Operations. Major elements of the UML use case diagram of Ticket Reservation System are shown on the picture below.

The relationships between and among the actors and the use cases of Ticket Reservation System:

  • Super Admin Entity : Use cases of Super Admin are Trains, Manage Seats, Manage Fare, Manage Stations, Manage Booking, Manage Passengers, Manage Ticket, Manage Users and Full Ticket Reservation System Operations
  • System User Entity : Use cases of System User are Trains, Manage Seats, Manage Fare, Manage Stations, Manage Booking, Manage Passengers, Manage Ticket
  • Agents Entity : Use cases of Agents are Book Tickets, Send Tickets, Collect Payments, Search History
  • Customer Entity : Use cases of Customer are Book Tickets, Make Payment, Download Tickets

Use Case Diagram of Ticket Reservation System :

Ticket Reservation System Use Case Diagram

Project Category