Metro Rail Ticket Booking System UML Diagram

Posted By freeproject on March 22, 2018

Metro Rail Ticket Booking System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Metro Rail Ticket Booking System which shows the flows between the activity of Stations, Booking Counter, Ticket, Route, Fare. The main activity involved in this UML Activity Diagram of Metro Rail Ticket Booking System are as follows:

  • Stations Activity
  • Booking Counter Activity
  • Ticket Activity
  • Route Activity
  • Fare Activity

Features of the Activity UML diagram of Metro Rail Ticket Booking System

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

Metro Rail Ticket Booking System Class Diagram

Posted By freeproject on August 2, 2017

Metro Rail Ticket Booking System Class Diagram describes the structure of a Metro Rail Ticket Booking System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Metro Rail Ticket Booking System are Metro, Routes, Tickets, Fare, Booking Counter, Stations.

Classes of Metro Rail Ticket Booking System Class Diagram:

  • Metro Class : Manage all the operations of Metro
  • Routes Class : Manage all the operations of Routes
  • Tickets Class : Manage all the operations of Tickets
  • Fare Class : Manage all the operations of Fare
  • Booking Counter Class : Manage all the operations of Booking Counter
  • Stations Class : Manage all the operations of Stations

Classes and their attributes of Metro Rail Ticket Booking System Class Diagram:

  • Metro Attributes : metro_id, metro_name, metro_number, metro_seat_number, metro_ticket, metro_type, metro_description
  • Routes Attributes : metro_route_id, metro_route_name, metro_route_type, metro_route_description
  • Tickets Attributes : ticket_id, ticket_customer_id, ticket_type, ticket_date, ticket_description
  • Fare Attributes : fare_id, fare_ticket_id, fare_title, fare_type, fare_description
  • Booking Counter Attributes : booking_id, booking_title, booking_type, booking_ticket, booking_date, booking_description
  • Stations Attributes : station_id, station_name, station_type, station_description

Classes and their methods of Metro Rail Ticket Booking System Class Diagram:

  • Metro Methods : addMetro(), editMetro(), deleteMetro(), updateMetro(), saveMetro(), searchMetro()
  • Routes Methods : addRoutes(), editRoutes(), deleteRoutes(), updateRoutes(), saveRoutes(), searchRoutes()
  • Tickets Methods : addTickets(), editTickets(), deleteTickets(), updateTickets(), saveTickets(), searchTickets()
  • Fare Methods : addFare(), editFare(), deleteFare(), updateFare(), saveFare(), searchFare()
  • Booking Counter Methods : addBooking Counter(), editBooking Counter(), deleteBooking Counter(), updateBooking Counter(), saveBooking Counter(), searchBooking Counter()
  • Stations Methods : addStations(), editStations(), deleteStations(), updateStations(), saveStations(), searchStations()

Class Diagram of Metro Rail Ticket Booking System :

Class Diagram Image: 
Metro Rail Ticket Booking System Class Diagram

Metro Rail Ticket Booking System Component Diagram

Posted By freeproject on February 8, 2018

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

Components of UML Component Diagram of Metro Rail Ticket Booking System:

  • Ticket Component
  • Metro Component
  • Stations Component
  • Route Component
  • Booking Counter Component

Featues of Metro Rail Ticket Booking System Component Diagram:

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

Metro Rail Ticket Booking System Dataflow Diagram

Posted By namita on July 7, 2017

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


Zero Level Data flow Diagram(0 Level DFD) of Metro Rail Ticket Booking System :

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

High Level Entities and proccess flow of Metro Rail Ticket Booking System:

  • Managing all the Metro
  • Managing all the Routes
  • Managing all the Tickets
  • Managing all the Fare
  • Managing all the Booking Counter
  • Managing all the Stations
  • Managing all the Login
Zero Level Data flow Diagram(0 Level DFD) of Metro Rail Ticket Booking System

First Level Data flow Diagram(1st Level DFD) of Metro Rail Ticket Booking System :

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

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

  • Processing Metro records and generate report of all Metro
  • Processing Routes records and generate report of all Routes
  • Processing Tickets records and generate report of all Tickets
  • Processing Fare records and generate report of all Fare
  • Processing Booking Counter records and generate report of all Booking Counter
  • Processing Stations records and generate report of all Stations
  • Processing Login records and generate report of all Login
First Level Data flow Diagram(1st Level DFD) of Metro Rail Ticket Booking System

Second Level Data flow Diagram(2nd Level DFD) of Metro Rail Ticket Booking System :

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

Low level functionalities of Metro Rail Ticket Booking System

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

Metro Rail Ticket Booking System ER Diagram

Posted By freeproject on July 17, 2017

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

Metro Rail Ticket Booking System entities and their attributes :

  • Metro Entity : Attributes of Metro are metro_id, metro_name, metro_number, metro_seat_number, metro_ticket, metro_type, metro_description
  • Routes Entity : Attributes of Routes are metro_route_id, metro_route_name, metro_route_type, metro_route_description
  • Tickets Entity : Attributes of Tickets are ticket_id, ticket_customer_id, ticket_type, ticket_date, ticket_description
  • Fare Entity : Attributes of Fare are fare_id, fare_ticket_id, fare_title, fare_type, fare_description
  • Booking Counter Entity : Attributes of Booking Counter are booking_id, booking_title, booking_type, booking_ticket, booking_date, booking_description
  • Stations Entity : Attributes of Stations are station_id, station_name, station_type, station_description

Description of Metro Rail Ticket Booking System Database :

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

Metro Rail Ticket Booking System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Metro Rail Ticket Booking System which shows the interaction between the objects of Stations, Booking Counter, Metro, Route, Fare. The instance of class objects involved in this UML Sequence Diagram of Metro Rail Ticket Booking System are as follows:

  • Stations Object
  • Booking Counter Object
  • Metro Object
  • Route Object
  • Fare Object

This is the UML sequence diagram of Metro Rail Ticket Booking System which shows the interaction between the objects of Stations, Booking Counter, Metro, Route, Fare. The instance of class objects involved in this UML Sequence Diagram of Metro Rail Ticket Booking System are as follows:

  • Stations Object
  • Booking Counter Object
  • Metro Object
  • Route Object
  • Fare Object

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

The relationships between and among the actors and the use cases of Metro Rail Ticket Booking System:

  • Super Admin Entity : Use cases of Super Admin are Manage Metro, Manage Routes, Manage Tickets, Manage Fare, Manage Booking Counter, Manage Stations, Manage Users and Full Metro Rail Ticket Booking System Operations
  • System User Entity : Use cases of System User are Manage Metro, Manage Routes, Manage Tickets, Manage Fare, Manage Booking Counter, Manage Stations
  • Ticket Agent Entity : Use cases of Ticket Agent are Create Pass, Book Customer Tickets, Collect Payment, Search Stations
  • Customer Entity : Use cases of Customer are Book Ticket, View Transactions, Make Payment

Use Case Diagram of Metro Rail Ticket Booking System :

Metro Rail Ticket Booking System Use Case Diagram

Project Category