How devanshumarkam/airline_management_system works
Project type and purpose
• This is a standalone desktop “full-stack” airline management system written in Java Swing/AWT, using a MySQL backend.
• It supports two user roles (Admin, Customer) for adding customers, booking/canceling flights, viewing journey details, and generating boarding passes.
File structure
Top-level Java classes (each one is a Swing form + controller logic):
• Login.java
• Home.java
• AddCustomer.java
• Flightinfo.java
• BookFlight.java
• JourneyDetails.java
• Cancel.java
• BoardingPass.java
Data-access helper:
• Conn.java (manages JDBC connection & executes SQL)
UI resources folder:
README insights
• Technologies: Java Swing/AWT (presentation), MySQL (storage), NetBeans (IDE)
• Workflow: CRUD operations on customer, flight, reservation, cancellation, boarding pass; PNR generation; lookups by Aadhaar/PNR.
Main components
a. Presentation Layer (Desktop Client)
• Sub-components: Login Screen, Home Dashboard, Customer Form, Flight Search, Booking Form, Journey Details Viewer, Cancellation Form, Boarding Pass Generator
• Resource bundle: Images/
b. Data Access Layer
• Conn.java (JDBC Connection Pool or singleton)
• SQL operations: INSERT (customers, reservations), SELECT (flight list, customer data, journey details), UPDATE/DELETE (cancellations)
c. Database
• MySQL Server
• Schema with tables: login, customer, flight, reservation (PNR), cancellation, boarding_pass
d. External/Infrastructure
• MySQL JDBC Driver
• NetBeans Project configuration (build scripts, library references)
Relationships & data flow
• User interacts with a Swing form → form logic invokes Conn.java → Conn opens JDBC socket to MySQL → executes SQL → returns ResultSet → form renders data or confirmation.
• PNR generator resides in BookFlight.java (business logic).
• Cancellation and boarding-pass screens fetch all data from DB using PNR.
Architectural patterns & principles
• Layered Architecture: UI layer (Swing) → Data Access layer (Conn.java) → Database
• Single-process monolith: no microservices or HTTP/API.
• MVC‐inspired separation: Forms = view + controller, Conn.java = model/DAO.