Railway Management System UML Diagram

Posted By freeproject on March 23, 2018

Railway Management System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Railway Management System which shows the flows between the activity of Customer, Booking, Train Schedule, Train Route, Payment. The main activity involved in this UML Activity Diagram of Railway Management System are as follows:

  • Customer Activity
  • Booking Activity
  • Train Schedule Activity
  • Train Route Activity
  • Payment Activity

Features of the Activity UML diagram of Railway Management 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 Train Schedule, Train Route, Payment
  • All objects such as ( Customer, Booking, Payment) are interlinked
  • Its shows the full description and flow of Customer, Train Route, Payment, Train Schedule, Booking
Railway Management System Activity Diagram

Railway Management System Class Diagram

Posted By freeproject on August 2, 2017

Railway Management System Class Diagram describes the structure of a Railway Management System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Railway Management System are Stations, Booking, Customers, Trains, Timetable, Employee.

Classes of Railway Management System Class Diagram:

  • Stations Class : Manage all the operations of Stations
  • Booking Class : Manage all the operations of Booking
  • Customers Class : Manage all the operations of Customers
  • Trains Class : Manage all the operations of Trains
  • Timetable Class : Manage all the operations of Timetable
  • Employee Class : Manage all the operations of Employee

Classes and their attributes of Railway Management System Class Diagram:

  • Stations Attributes : station_id, station_name, station_type, station_description
  • Booking Attributes : booking_id, booking_title, booking_type, booking_ticket, booking_date, booking_description
  • Customers Attributes : customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Trains Attributes : train_id, train_name, train_number, train_seat_number, train_ticket, train_type, train_description
  • Timetable Attributes : timetable_id,rain_id, timetable_name, timetable_type, timetable_description timetable_t
  • Employee Attributes : employee_id, employee_name, employee_mobile, employee_email, employee_username, employee_password, employee_address

Classes and their methods of Railway Management System Class Diagram:

  • Stations Methods : addStations(), editStations(), deleteStations(), updateStations(), saveStations(), searchStations()
  • Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
  • Customers Methods : addCustomers(), editCustomers(), deleteCustomers(), updateCustomers(), saveCustomers(), searchCustomers()
  • Trains Methods : addTrains(), editTrains(), deleteTrains(), updateTrains(), saveTrains(), searchTrains()
  • Timetable Methods : addTimetable(), editTimetable(), deleteTimetable(), updateTimetable(), saveTimetable(), searchTimetable()
  • Employee Methods : addEmployee(), editEmployee(), deleteEmployee(), updateEmployee(), saveEmployee(), searchEmployee()

Class Diagram of Railway Management System :

Class Diagram Image: 
Railway Management System Class Diagram

Railway Management System Component Diagram

Posted By freeproject on February 8, 2018

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

Components of UML Component Diagram of Railway Management System:

  • Customer Component
  • Train Schedule Component
  • Payment Component
  • Booking Component
  • Ticket Component

Featues of Railway Management System Component Diagram:

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

Railway Management System Dataflow Diagram

Posted By namita on July 8, 2017

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


Zero Level Data flow Diagram(0 Level DFD) of Railway Management System :

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

High Level Entities and proccess flow of Railway Management System:

  • Managing all the Trains
  • Managing all the Timetable
  • Managing all the Fare
  • Managing all the Stations
  • Managing all the Booking
  • Managing all the Customers
  • Managing all the Ticket
Zero Level Data flow Diagram(0 Level DFD) of Railway Management System

First Level Data flow Diagram(1st Level DFD) of Railway Management System :

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

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

  • Processing Trains records and generate report of all Trains
  • Processing Timetable records and generate report of all Timetable
  • 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 Customers records and generate report of all Customers
  • Processing Ticket records and generate report of all Ticket
First Level Data flow Diagram(1st Level DFD) of Railway Management System

Second Level Data flow Diagram(2nd Level DFD) of Railway Management System :

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

Low level functionalities of Railway Management System

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

Railway Management System ER Diagram

Posted By freeproject on July 17, 2017

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

Railway Management System entities and their attributes :

  • Stations Entity : Attributes of Stations are station_id, station_name, station_type, station_description
  • Booking Entity : Attributes of Booking are booking_id, booking_title, booking_type, booking_ticket, booking_date, booking_description
  • Customers Entity : Attributes of Customers are customer_id, customer_name, customer_mobile, customer_email, customer_username, customer_password, customer_address
  • Trains Entity : Attributes of Trains are train_id, train_name, train_number, train_seat_number, train_ticket, train_type, train_description
  • Timetable Entity : Attributes of Timetable are timetable_id,rain_id, timetable_name, timetable_type, timetable_description timetable_t
  • Employee Entity : Attributes of Employee are employee_id, employee_name, employee_mobile, employee_email, employee_username, employee_password, employee_address

Description of Railway Management System Database :

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

Railway Management System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Railway Management System which shows the interaction between the objects of Booking, Train Route, Customer, Payment, Ticket. The instance of class objects involved in this UML Sequence Diagram of Railway Management System are as follows:

  • Booking Object
  • Train Route Object
  • Customer Object
  • Payment Object
  • Ticket Object

This is the UML sequence diagram of Railway Management System which shows the interaction between the objects of Booking, Train Route, Customer, Payment, Ticket. The instance of class objects involved in this UML Sequence Diagram of Railway Management System are as follows:

  • Booking Object
  • Train Route Object
  • Customer Object
  • Payment Object
  • Ticket Object

Railway Management 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 Railway Management System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Railway Management System. The main actors of Railway Management System in this Use Case Diagram are: Super Admin, System User, Station Masters, Anonymous Users, who perform the different type of use cases such as Manage Trains, Manage Timetable, Manage Fare, Manage Stations, Manage Seats Availability, Manage Routes, Manage Train Schedule, Manage Users and Full Railway Management System Operations. Major elements of the UML use case diagram of Railway Management System are shown on the picture below.

The relationships between and among the actors and the use cases of Railway Management System:

  • Super Admin Entity : Use cases of Super Admin are Manage Trains, Manage Timetable, Manage Fare, Manage Stations, Manage Seats Availability, Manage Routes, Manage Train Schedule, Manage Users and Full Railway Management System Operations
  • System User Entity : Use cases of System User are Manage Trains, Manage Timetable, Manage Fare, Manage Stations, Manage Seats Availability, Manage Routes, Manage Train Schedule
  • Station Masters Entity : Use cases of Station Masters are Add Train Timetable, View Schedules, Update Arrivals, Update Departures
  • Anonymous Users Entity : Use cases of Anonymous Users are View Information, Fill Contact Us, Search Content

Use Case Diagram of Railway Management System :

Railway Management System Use Case Diagram

Project Category