
🎓 Student Projects (College Reports) · Database ERD
The database of a railway reservation system: trains, coaches and seats, stations and routes, passengers, bookings with a PNR, tickets, payments, cancellations and refunds.
Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.
Drawing diagram…
ER diagram for a railway reservation system: trains with coaches and seats, stations, routes as an ordered list of stations per train with arrival and departure times, passengers, bookings with a PNR for a journey date, tickets per passenger with seat and status (confirmed, RAC, waiting list), payments, and cancellations with refunds.
erDiagram
TRAIN ||--o{ COACH : "configures"
TRAIN ||--o{ ROUTE_STATION : "runs_along"
TRAIN ||--o{ BOOKING : "scheduled_for"
STATION ||--o{ ROUTE_STATION : "located_at"
COACH ||--o{ SEAT : "contains"
PASSENGER ||--o{ BOOKING : "initiates"
BOOKING ||--o{ TICKET : "issues"
BOOKING ||--o{ PAYMENT : "settled_by"
SEAT ||--o| TICKET : "assigned_to"
TICKET ||--o| CANCELLATION : "cancelled_via"
PAYMENT ||--o| REFUND : "processes"
CANCELLATION ||--o| REFUND : "triggers"
TRAIN {
uuid id PK
string train_number
string train_name
string train_type
timestamp created_at
}
STATION {
uuid id PK
string station_code
string station_name
string city
timestamp created_at
}
ROUTE_STATION {
uuid id PK
uuid train_id FK
uuid station_id FK
integer stop_sequence
string scheduled_arrival
string scheduled_departure
}
COACH {
uuid id PK
uuid train_id FK
string coach_code
string coach_class
int total_seats
}
SEAT {
uuid id PK
uuid coach_id FK
string seat_number
string berth_type
}
PASSENGER {
uuid id PK
string full_name
integer age
string gender
string identity_number
timestamp created_at
}
BOOKING {
uuid id PK
uuid passenger_id FK
uuid train_id FK
string pnr_number
date journey_date
string booking_status
timestamp created_at
}
TICKET {
uuid id PK
uuid booking_id FK
uuid seat_id FK
string passenger_name
string ticket_status
decimal fare_amount
}
PAYMENT {
uuid id PK
uuid booking_id FK
string transaction_reference
decimal total_amount
string payment_status
timestamp payment_time
}
CANCELLATION {
uuid id PK
uuid ticket_id FK
string cancellation_reason
decimal fee_deducted
timestamp cancelled_at
}
REFUND {
uuid id PK
uuid payment_id FK
uuid cancellation_id FK
decimal refund_amount
string refund_status
timestamp processed_at
}An entity relationship diagram with 11 tables, 61 columns and 12 relationships.
Describe your own system in plain English and the AI ER diagram generator draws it in seconds, in the same style as this template.
Who uses a college library system and what each of them can do: members, the librarian and the system administrator.
The database of a library system: books and their copies, authors, members, loans, reservations and fines, with keys and cardinality.
How data moves through a library system: members and the librarian, the main processes, and the data stores they read and write.
The main classes of a library system with attributes, methods and UML relationships.
The steps when a member borrows a book: checks, loan record and the copy status update.
What students, examiners and the administrator do in an online examination system.