- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Railway Enquiry System Activity Diagram
This is the Activity UML diagram of Railway Enquiry System which shows the flows between the activity of Booking, , Stations, Trains, Customers Timetable. The main activity involved in this UML Activity Diagram of Railway Enquiry System are as follows:
- Booking Activity
- Activity
- Stations Activity
- Trains Activity
- Customers Timetable Activity
Features of the Activity UML diagram of Railway Enquiry System
- Admin User can search Booking, view description of a selected Booking, add Booking, update Booking and delete Booking.
- Its shows the activity flow of editing, adding and updating of
- User will be able to search and generate report of Stations, Trains, Customers Timetable
- All objects such as ( Booking, , Customers Timetable) are interlinked
- Its shows the full description and flow of Booking, Trains, Customers Timetable, Stations,
Login Activity Diagram of Railway Enquiry System:
This is the Login Activity Diagram of Railway Enquiry 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 Stations, Booking, , Customers Timetable, Trains. All the pages such as , Customers Timetable, Trains are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Railway Enquiry System. The various objects in the Customers Timetable, Stations, Booking, , and Trains 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 Enquiry System Class Diagram
Railway Enquiry System Class Diagram describes the structure of a Railway Enquiry System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Railway Enquiry System are Trains, Timetable, Fare, Stations, Seats Availability, Routes.
Classes of Railway Enquiry System Class Diagram:
- Trains Class : Manage all the operations of Trains
- Timetable Class : Manage all the operations of Timetable
- Fare Class : Manage all the operations of Fare
- Stations Class : Manage all the operations of Stations
- Seats Availability Class : Manage all the operations of Seats Availability
- Routes Class : Manage all the operations of Routes
Classes and their attributes of Railway Enquiry System Class Diagram:
- Trains Attributes : train_id, train_name, train_number, train_seat_number, train_ticket, train_type, train_description
- Timetable Attributes : timetable_id, timetable_name, timetable_type, timetable_description timetable_t
- Fare Attributes : fare_id, fare_ticket_id, fare_title, fare_type, fare_description
- Stations Attributes : station_id, station_name, station_type, station_description
- Seats Availability Attributes : seat_id, seat_train_id, seat_customer_id, seat_number, seat_type, seat_description
- Routes Attributes : train_route_id, train_route_name, train_route_type, train_route_description
Classes and their methods of Railway Enquiry System Class Diagram:
- Trains Methods : addTrains(), editTrains(), deleteTrains(), updateTrains(), saveTrains(), searchTrains()
- Timetable Methods : addTimetable(), editTimetable(), deleteTimetable(), updateTimetable(), saveTimetable(), searchTimetable()
- Fare Methods : addFare(), editFare(), deleteFare(), updateFare(), saveFare(), searchFare()
- Stations Methods : addStations(), editStations(), deleteStations(), updateStations(), saveStations(), searchStations()
- Seats Availability Methods : addSeats Availability(), editSeats Availability(), deleteSeats Availability(), updateSeats Availability(), saveSeats Availability(), searchSeats Availability()
- Routes Methods : addRoutes(), editRoutes(), deleteRoutes(), updateRoutes(), saveRoutes(), searchRoutes()
Class Diagram of Railway Enquiry System :
- Posted By: freeproject
- Comments: 0
Railway Enquiry System Component Diagram
This is a Component diagram of Railway Enquiry System which shows components, provided and required interfaces, ports, and relationships between the Booking, Trains, , Stations and Customers Timetable. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Railway Enquiry System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Railway Enquiry System:
- Booking Component
- Trains Component
- Component
- Stations Component
- Customers Timetable Component
Featues of Railway Enquiry System Component Diagram:
- You can show the models the components of Railway Enquiry System.
- Model the database schema of Railway Enquiry System
- Model the executables of an application of Railway Enquiry System
- Model the system's source code of Railway Enquiry System
- Posted By: namita
- Comments: 0
Railway Enquiry System Dataflow Diagram
Railway Enquiry 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, Seats Availability, Routes, Train Schedule. 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 Enquiry System :
This is the Zero Level DFD of Railway Enquiry System, where we have eloborated the high level process of Railway. It’s a basic overview of the whole Railway Enquiry System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Seats Availability,Routes and Train Schedule 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 Seats Availability In zero leve DFD of Railway Enquiry System, we have described the high level flow of the Railway system.High Level Entities and proccess flow of Railway Enquiry System:
- Managing all the Trains
- Managing all the Timetable
- Managing all the Fare
- Managing all the Stations
- Managing all the Seats Availability
- Managing all the Routes
- Managing all the Train Schedule
First Level Data flow Diagram(1st Level DFD) of Railway Enquiry System :
First Level DFD (1st Level) of Railway Enquiry 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 Enquiry System system as a whole. It also identifies internal data stores of Train Schedule, Routes, Seats Availability, 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, Routes, Train Schedule, Seats Availability 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 Seats Availability records and generate report of all Seats Availability
- Processing Routes records and generate report of all Routes
- Processing Train Schedule records and generate report of all Train Schedule
Second Level Data flow Diagram(2nd Level DFD) of Railway Enquiry 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 Enquiry System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Train Schedule, Routes, Seats Availability, Stations, Fare, Timetable, Trains.Low level functionalities of Railway Enquiry System
- Admin logins to the system and manage all the functionalities of Railway Enquiry System
- Admin can add, edit, delete and view the records of Trains, Fare, Seats Availability, Train Schedule
- Admin can manage all the details of Timetable, Stations, Routes
- Admin can also generate reports of Trains, Timetable, Fare, Stations, Seats Availability, Routes
- Admin can search the details of Timetable, Seats Availability, Routes
- Admin can apply different level of filters on report of Trains, Stations, Seats Availability
- Admin can tracks the detailed information of Timetable, Fare, Stations, , Seats Availability
- Posted By: freeproject
- Comments: 0
Railway Enquiry System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Railway Enquiry System Entity. The entity-relationship diagram of Railway Enquiry System shows all the visual instrument of database tables and the relations between Timetable, Stations, Trains, Routes etc. It used structure data and to define the relationships between structured data groups of Railway Enquiry System functionalities. The main entities of the Railway Enquiry System are Trains, Timetable, Fare, Stations, Seats Availability and Routes.
Railway Enquiry 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
- Timetable Entity : Attributes of Timetable are timetable_id, timetable_name, timetable_type, timetable_description timetable_t
- 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
- Seats Availability Entity : Attributes of Seats Availability are seat_id, seat_train_id, seat_customer_id, seat_number, seat_type, seat_description
- Routes Entity : Attributes of Routes are train_route_id, train_route_name, train_route_type, train_route_description
Description of Railway Enquiry System Database :
- The details of Trains is store into the Trains tables respective with all tables
- Each entity ( Routes, Fare, Seats Availability, Timetable, Trains) contains primary key and unique keys.
- The entity Fare, Seats Availability has binded with Trains, Timetable entities with foreign key
- There is one-to-one and one-to-many relationships available between Seats Availability, Stations, Routes, Trains
- All the entities Trains, Seats Availability, Fare, Routes are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Railway Enquiry System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Railway Enquiry System Sequence Diagram
This is the UML sequence diagram of Railway Enquiry System which shows the interaction between the objects of Trains, , Booking, Stations, Customers Timetable. The instance of class objects involved in this UML Sequence Diagram of Railway Enquiry System are as follows:
- Trains Object
- Object
- Booking Object
- Stations Object
- Customers Timetable Object
Login Sequence Diagram of Railway Enquiry System:
This is the Login Sequence Diagram of Railway Enquiry System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Booking, Trains, , Customers Timetable, Stations. All the pages such as , Customers Timetable, Stations are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Railway Enquiry System. The various objects in the Customers Timetable, Booking, Trains, , and Stations 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 Enquiry System which shows the interaction between the objects of Trains, , Booking, Stations, Customers Timetable. The instance of class objects involved in this UML Sequence Diagram of Railway Enquiry System are as follows:
- Trains Object
- Object
- Booking Object
- Stations Object
- Customers Timetable Object
- Posted By: freeproject
- Comments: 0
Railway Enquiry System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Railway Enquiry System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Railway Enquiry System. The main actors of Railway Enquiry System in this Use Case Diagram are: Super Admin, System User, Call Centers, 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 Enquiry System Operations. Major elements of the UML use case diagram of Railway Enquiry System are shown on the picture below.
The relationships between and among the actors and the use cases of Railway Enquiry 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 Enquiry 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
- Call Centers Entity : Use cases of Call Centers are Check Enquiry, Reply for Statu Update, Update Timetables
- Users Entity : Use cases of Users are Do Enquiries, Check Train Fares, Check Train Schedules, Check Seat Availibility
Use Case Diagram of Railway Enquiry System :
