Railway Ticketing

Service
190204093 Fardin Jaman Aranyak
190204099 Tahmid Bin Rafique
190204111 Shovon Chowdhury
190204113 Mehedi Islam Remon

1
 INTRODUCTION

1. Railway e-service is a service from where passenger can easily process

their train ticket reservation & the administration of train service can
easily control their time schedule as well as update current train list

2. While there is various ways to build complex functionality contained

application, our project railway e-service only focused on passenger &
administrator’s advantage.

2
 PROCESS MODEL
Spiral:

3
 PROJECT FEATURES

1. Admin account can Add train, station, class and journey.

2. User can search about station, coach and train availability.
3. User can Purchase ticket.

4
 USE CASE DIAGRAM

Actors:-
1. User
2. Admin

5
 Activities Of The Project

1. Registration and Login.

2. Update profile.
3. Searching information about train.
4. Purchase ticket.
5. Payment and printing ticket.
6. Information about Coach and Stations.
7. Add train, station, journey and coach.

6
 PROCESS NAMES OF DFD

Main Processes:-
1. Create Account
2. Login
3. Search
4. Purchase ticket
5. Make Payment and Print ticket

7
 PROCESS NAMES OF DFD

Sub Processes:-
1. New user registration
2. Registered user login
3. Admin Login
4. User profile update
5. Admin adds train, station, journey and coach
6. User search about train according to arrival station, departure station and
date.

8
 PROCESS NAMES OF DFD

Sub processes:-
7. User make payment
8. User get generated ticket to print or download

9
 ENTITY AND DB NAMES OF DFD

Entity names:-
1. User
2. Admin

Db Names:-
1. railway_eservice

10
CONTEXT/LEVEL-0 DIAGRAM

11
LEVEL 1 DIAGRAM

12
LEVEL 1-N DIAGRAMS

13
LEVEL 1-N DIAGRAMS

14
LEVEL 1-N DIAGRAMS

15
LEVEL 1-N DIAGRAMS

16
LEVEL 1-N DIAGRAMS

17
 ENTITY SET NAMES (ATTRIBUTES SPECIFIES WITH DATA TYPE)

station Table:
"user" Table: s_id: int [PK]
id: int [PK] s_name: varchar(256)
name: varchar(100) s_master: varchar(100)
email: varchar(100) sm_number: varchar(11)
mobile: varchar(11)  
pass varchar(20)
nid: varchar(17) train Table:
t_id: int [PK]
  t_name: varchar(256)
admin Table: from_st: int
username: varchar(11) [PK] to_st: int
pass: varchar(20) startTime: time
endTime: time

18
 ENTITY SET NAMES (ATTRIBUTES SPECIFIES WITH DATA TYPE)

coach Table:
c_id: int [PK] ticket Table:
c_name: varchar(100) tk_id: int [PK]
c_fare: int tk_j_id: int [FK]
  tk_u_id: int [FK
journey Table:
tk_seats: int
j_id: int [PK] tk_fare: int
j_train: int [FK]
j_date: Date
j_coach: int [FK]
j_vacancy: int

19
PRIMARY ERD

20
NORMALIZATION
a. 1NF

Train Table

T_id T_name From_st To_st startTime endTime Coach_name Coach_fare

1 Shonar Bangla Dhaka Chittagong 7:00 12:45 Snigdha, AC_S, 720, 985, 700,
F_SEAT, 500
Shovon

Modified after 1NF

t_id t_name from_st to_st startTime endTime coach_name coach_fare
1 Shonar Dhaka Chittagong 7:00 12:45 Snigdha 720
Bangla  
1 Shonar Dhaka Chittagong 7:00 12:45 AC_S 985
Bangla
1 Shonar Dhaka Chittagong 7:00 12:45 F_SEAT 700
Bangla

21
NORMALIZATION
b. 2NF

Train Table
t_id t_name from_st to_st startTime endTime

Coach Table
c_id c_name c_fare

Journey Table
j_id j_train j_coach j_date J_vacancy

Ticket Table
tk_id tk_j_id tk_seats tk_fare tk_u_id

22
FINAL ERD

23
Relationship among entity sets

User-Ticket: One-to-many
Ticket-Journey: Many-to-one
Journey-Coach: One-to-One
Journey-Train: One-to-One
Station-Train: One-to-many
Train-Coach: One-to-many
Admin has many-to-many relationship with Ticket, Journey, Station, Train
and Coach

24
COST BENEFIT ANALYSIS
  Year 0 Year 1 Year 2
Cash Flow
Revenue 0 17000 35000
Analysis Cost      
Hardware 43000 25000 13000
Software 15000 12000 7000
Maintenance 8000 8200 8500
Total 66000 45200 28500
Cash Flow (CF) -66000 -28200 6500

Year CF PV
0 -66000 -66000
Rate of Risk, R = 10% 1 -28200 -25636.36
Net Present Value 2 6500 5371.9
NPV -86264.46

B103 9/8/2022 25
25
LOGIN PAGE

26
REGISTRATION PAGE

27
TRAIN DETAILS

28
29
SELECT YOUR TICKET

30
PAYMENT PAGE

31
PAYMENT CONFIRMATION MAIL

32
GENERATED PDF TICKET

33
FEEDBACK

34
FEEDBACK MAIL

35
Conclusion

We are very optimistic that our railway e-service will set a

great precedent in Bangladesh railway. It will be very easy to
use, reliable and user friendly railway e-service. We hope that
this application will fulfil the need very easily and fastly.

36
 Thank You
Any Questions?

37