- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Railway Reservation System Activity Diagram
This is the Activity UML diagram of Railway Reservation System which shows the flows between the activity of Ticket, Customer, Payment, Booking, Train Schedule. The main activity involved in this UML Activity Diagram of Railway Reservation System are as follows:
- Ticket Activity
- Customer Activity
- Payment Activity
- Booking Activity
- Train Schedule Activity
Features of the Activity UML diagram of Railway 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 Customer
- User will be able to search and generate report of Payment, Booking, Train Schedule
- All objects such as (Ticket, Customer, Train Schedule) are interlinked
- Its shows the full description and flow of Ticket, Booking, Train Schedule, Payment, Customer
Login Activity Diagram of Railway Reservation System:
This is the Login Activity Diagram of Railway Reservation 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 Payment, Ticket, Customer, Train Schedule, Booking. All the pages such as Customer, Train Schedule, Booking are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Railway Reservation System. The various objects in the Train Schedule, Payment, Ticket, Customer, and Booking 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
Railway Reservation System Class Diagram
Railway Reservation System Class Diagram describes the structure of a Railway Reservation System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Railway Reservation System are Train, Ticket, Booking, Customer, Payment, Train Route.
Classes of Railway Reservation System Class Diagram:
- Train Class : Manage all the operations of Train
- Ticket Class : Manage all the operations of Ticket
- Booking Class : Manage all the operations of Booking
- Customer Class : Manage all the operations of Customer
- Payment Class : Manage all the operations of Payment
- Train Route Class : Manage all the operations of Train Route
Classes and their attributes of Railway Reservation System Class Diagram:
- Train Attributes : train_id, train_name, train_number, train_seat_number, train_ticket, train_type, train_description
- Ticket Attributes : ticket_id, ticket_customer_id, ticket_type, ticket_date, ticket_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
- Payment Attributes : payment_id, payment_customer_id, payment_date, payment_amount, payment_description
- Train Route Attributes : train_route_id, train_route_name, train_route_type, train_route_description
Classes and their methods of Railway Reservation System Class Diagram:
- Train Methods : addTrain(), editTrain(), deleteTrain(), updateTrain(), saveTrain(), searchTrain()
- Ticket Methods : addTicket(), editTicket(), deleteTicket(), updateTicket(), saveTicket(), searchTicket()
- Booking Methods : addBooking(), editBooking(), deleteBooking(), updateBooking(), saveBooking(), searchBooking()
- Customer Methods : addCustomer(), editCustomer(), deleteCustomer(), updateCustomer(), saveCustomer(), searchCustomer()
- Payment Methods : addPayment(), editPayment(), deletePayment(), updatePayment(), savePayment(), searchPayment()
- Train Route Methods : addTrain Route(), editTrain Route(), deleteTrain Route(), updateTrain Route(), saveTrain Route(), searchTrain Route()
Class Diagram of Railway Reservation System :
- Posted By: freeproject
- Comments: 0
Railway Reservation System Component Diagram
This is a Component diagram of Railway Reservation System which shows components, provided and required interfaces, ports, and relationships between the Train Schedule, Ticket, Booking, Customer and Payment. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Railway Reservation System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Railway Reservation System:
- Train Schedule Component
- Ticket Component
- Booking Component
- Customer Component
- Payment Component
Featues of Railway Reservation System Component Diagram:
- You can show the models the components of Railway Reservation System.
- Model the database schema of Railway Reservation System
- Model the executables of an application of Railway Reservation System
- Model the system's source code of Railway Reservation System
- Posted By: freeproject
- Comments: 0
Railway Reservation System Dataflow Diagram
Railway Reservation System Data flow diagram is often used as a preliminary step to create an overview of the Railway Reservation without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Railway Reservation process. It contains all of the userflow and their entities such all the flow of Trains, Booking, Ticket, Train Shedule, Train Route, Customer, Payment. All of the below diagrams has been used for the visualization of data processing and structured design of the Railway Reservation process and working flow.
Zero Level Data flow Diagram(0 Level DFD) of Railway Reservation System :
This is the Zero Level DFD of Railway Reservation System, where we have eloborated the high level process of Railway Reservation. It’s a basic overview of the whole Railway Reservation System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Train Route,Customer and Payment showing the system as a single high-level process, with its relationship to external entities of Trains,Booking and Ticket. It should be easily understood by a wide audience, including Trains,Ticket and Train Route In zero leve DFD of Railway Reservation System, we have described the high level flow of the Railway Reservation system.High Level Entities and proccess flow of Railway Reservation System:
- Managing all the Trains
- Managing all the Booking
- Managing all the Ticket
- Managing all the Train Shedule
- Managing all the Train Route
- Managing all the Customer
- Managing all the Payment
First Level Data flow Diagram(1st Level DFD) of Railway Reservation System :
First Level DFD (1st Level) of Railway 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 Railway Reservation System system as a whole. It also identifies internal data stores of Payment, Customer, Train Route, Train Shedule, Ticket that must be present in order for the Railway Reservation system to do its job, and shows the flow of data between the various parts of Trains, Ticket, Customer, Payment, Train Route 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 Reservation.Main entities and output of First Level DFD (1st Level DFD):
- Processing Trains records and generate report of all Trains
- Processing Booking records and generate report of all Booking
- Processing Ticket records and generate report of all Ticket
- Processing Train Shedule records and generate report of all Train Shedule
- Processing Train Route records and generate report of all Train Route
- Processing Customer records and generate report of all Customer
- Processing Payment records and generate report of all Payment
Second Level Data flow Diagram(2nd Level DFD) of Railway Reservation System :
DFD Level 2 then goes one step deeper into parts of Level 1 of Railway Reservation. It may require more functionalities of Railway Reservation to reach the necessary level of detail about the Railway Reservation functioning. First Level DFD (1st Level) of Railway Reservation System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Payment, Customer, Train Route, Train Shedule, Ticket, Booking, Trains.Low level functionalities of Railway Reservation System
- Admin logins to the system and manage all the functionalities of Railway Reservation System
- Admin can add, edit, delete and view the records of Trains, Ticket, Train Route, Payment
- Admin can manage all the details of Booking, Train Shedule, Customer
- Admin can also generate reports of Trains, Booking, Ticket, Train Shedule, Train Route, Customer
- Admin can search the details of Booking, Train Route, Customer
- Admin can apply different level of filters on report of Trains, Train Shedule, Train Route
- Admin can tracks the detailed information of Booking, Ticket, Train Shedule, , Train Route
- Posted By: freeproject
- Comments: 0
Railway Reservation System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Railway Reservation System Entity. The entity-relationship diagram of Railway Reservation System shows all the visual instrument of database tables and the relations between Ticket, Customer, Train, Train Route etc. It used structure data and to define the relationships between structured data groups of Railway Reservation System functionalities. The main entities of the Railway Reservation System are Train, Ticket, Booking, Customer, Payment and Train Route.
Railway Reservation System entities and their attributes :
- Train Entity : Attributes of Train are train_id, train_name, train_number, train_seat_number, train_ticket, train_type, train_description
- Ticket Entity : Attributes of Ticket are ticket_id, ticket_customer_id, ticket_type, ticket_date, ticket_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
- Payment Entity : Attributes of Payment are payment_id, payment_customer_id, payment_date, payment_amount, payment_description
- Train Route Entity : Attributes of Train Route are train_route_id, train_route_name, train_route_type, train_route_description
Description of Railway Reservation System Database :
- The details of Train is store into the Train tables respective with all tables
- Each entity ( Train Route, Booking, Payment, Ticket, Train) contains primary key and unique keys.
- The entity Booking, Payment has binded with Train, Ticket entities with foreign key
- There is one-to-one and one-to-many relationships available between Payment, Customer, Train Route, Train
- All the entities Train, Payment, Booking, Train Route are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Railway Reservation System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Railway Reservation System Sequence Diagram
This is the UML sequence diagram of Railway Reservation System which shows the interaction between the objects of Customer, Ticket, Train Route, Train Schedule, Booking. The instance of class objects involved in this UML Sequence Diagram of Railway Reservation System are as follows:
- Customer Object
- Ticket Object
- Train Route Object
- Train Schedule Object
- Booking Object
Login Sequence Diagram of Railway Reservation System:
This is the Login Sequence Diagram of Railway Reservation System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Train Route, Customer, Ticket, Booking, Train Schedule. All the pages such as Ticket, Booking, Train Schedule are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Railway Reservation System. The various objects in the Booking, Train Route, Customer, Ticket, and Train Schedule 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 Railway Reservation System which shows the interaction between the objects of Customer, Ticket, Train Route, Train Schedule, Booking. The instance of class objects involved in this UML Sequence Diagram of Railway Reservation System are as follows:
- Customer Object
- Ticket Object
- Train Route Object
- Train Schedule Object
- Booking Object
- Posted By: freeproject
- Comments: 0
Railway Reservation System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Railway Reservation System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Railway Reservation System. The main actors of Railway Reservation System in this Use Case Diagram are: Super Admin, System User, Ticket Agent, Customers, who perform the different type of use cases such as ManageTrain, Manage Ticket, Manage Booking, Manage Customer, Manage Payment, Manage Train Route, Manage Train Schedule, Manage Users and Full Railway Reservation System Operations. Major elements of the UML use case diagram of Railway Reservation System are shown on the picture below.
The relationships between and among the actors and the use cases of Railway Reservation System:
- Super Admin Entity : Use cases of Super Admin are ManageTrain, Manage Ticket, Manage Booking, Manage Customer, Manage Payment, Manage Train Route, Manage Train Schedule, Manage Users and Full Railway Reservation System Operations
- System User Entity : Use cases of System User are ManageTrain, Manage Ticket, Manage Booking, Manage Customer, Manage Payment, Manage Train Route, Manage Train Schedule
- Ticket Agent Entity : Use cases of Ticket Agent are Book Tickets, Search Vacant Seats, Collect Payment
- Customers Entity : Use cases of Customers are Search Trains, Book Tickets, Make Payments
Use Case Diagram of Railway Reservation System :
