NOAKHALI SCIENCE AND TECHNOLOGY UNIVERSITY

Assignment -02
Course Title : Database Management System
Course code : CSTE-3105
Submission Date : 12-06-2023
Department of computer science & Telecommunication Engineering

Submitted By: Submitted to :

Jannatul Ferdous Dr. Syful Islam

Roll: BFH2001031F Assistant Professor
Y ~ 03 ; T~01 Dept. of CSTE
Dept. of CSTE Noakhali Science & Technology
Noakhali Science & Technology University.
University.

1|Page
 1.Title of the Project :

Design of an E-R diagram on Bangladesh Railway E-Ticketing System..

2.Description: By E-ticketing service user usually login to their account and searched for the
desired destination ticket and booked the ticket .Now we will design an entity
relationship diagram for this service.which will show the relationship between
customer, ticket,train and train route etc.

3.1 Railway E-Ticketing Systems Entity Identification : An entity is an object that exists and
is distinguishable from other objects. An entity set is a set of entities of the same type that share
the same properties.
There are following set of entity as the have attribuets .Those entity sets are ,

• 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

3.2 listing all attributes and their types :

• Train Entity :

Single attribute : train _id ,train_ticket , train_seat_number, train_number

Composite attribute : train_name, train_type, train_description
2|Page
 • Ticket Entity :

Single attribute ticket_id, ticket_customer_id,

Composite attribute : ticket_description

• Booking Entity :

Single attribute : booking_id,, booking_ticket, booking_date,

Composite attribute : booking_title, booking_type,booking_description

• Customer Entity :

Single attribute : customer_id

Composite attribute : customer_name,customer_address
Multivalued attribute : customer_mobile, customer_email,

• Payment Entity :

Single attribute : payment_id, payment_customer_id,date,

Composite attribute : payment_amount, payment_description

• Train Route Entity :

Single attribute : train_route_id,
Composite attribute : train_route_name, train_route_type, train_route_description

3.3 listing primary key of each entity set :

• Train Entity : train_id, train_type

• Ticket Entity : ticket_id, ticket_type
• Booking Entity : booking_id, booking_ticket
• Customer Entity : customer_id,
• Payment Entity payment_id, payment_customer_id,
• Train Route Entity : train_route_id, train_route_name

3|Page
 Fig; ER diagram of Railway E-ticketing System

I drew the diagram by EDRAW MaX software

4|Page
3.4. Identifing relationships among entities and mapping cardinalities.

There are the following relationships in the ER diagram.

1. Issues : the relationship between the customer entity and ticket entity .and its one to many

relationship as customer can issue many tickets .

2. Check : relationship between customer & train_info .its many to many relationship .

3. Travel through : relationship between train_info and route .its many-to-many mapping cardinality

as many routes can be followed by a train.

4. Done : relationship between customer & payment. it follows one-to-many mapping cardinality as

a customer can make several payments . but a payment can’t be done by many customer

5. HAS-A : it’s a specialization method to check whether a payment has been made against a booked

ticket or not .its one-to-many mapping cardinality also.

5|Page