How bellmcp/decibel-airlines-reservation-system works
This repository is a standalone Java desktop application for airline seat reservation, packaged as a NetBeans project and built with Ant. The architecture is centered on a Swing-based GUI with a small set of domain classes behind it, rather than a separate server/database backend.
Main subsystems
1. Presentation layer: NetBeans-generated Swing forms
• main.java / main.form: the entry screen or landing window for the reservation system.
• RegisterForm.java / RegisterForm.form: collects passenger and booking information.
• Confirmation.java / Confirmation.form: confirms a booking or seat assignment.
• Cancellation.java / Cancellation.form: handles seat cancellation.
• ShowData.java / ShowData.form: displays reservation/seat data in a table or read-only view.
• About.java / About.form: informational screen about the application.
These forms are the user-facing boundary of the system. The .form files indicate the UI was designed visually in NetBeans, and the app relies on the generated Swing layout code. The bundled AbsoluteLayout.jar in dist/lib suggests the UI uses absolute positioning rather than a more adaptive layout manager.
2. Domain/model layer
• Seat.java
• Flight.java
These classes likely represent the core reservation state: seat identity, availability, passenger assignment, and flight-related data. Based on the README, seat operations such as CancelSeat, ConfirmSeat, UpdateSeat, and ShowData are implemented through object-oriented interaction with these classes.
3. Workflow/control logic
The application appears to be event-driven, with each form triggering actions that update shared reservation state and then transition to another form or refresh a display.
Typical flow:
• User starts in main
• User enters booking details in RegisterForm
• The app creates or updates a seat/flight object
• Confirmation is used to finalize the reservation
• ShowData displays current booking state
• Cancellation reverses or clears a reservation when needed
This is a client-only workflow: there is no visible service layer, API layer, or database layer in the repository structure.
4. Output/artifact generation
• dist/A1_broadingPass.txt
• dist/E5_broadingPass.txt
These files show that the app can emit boarding-pass-like text artifacts. That implies a file-generation path in the application where booking state is serialized into a printable text output. The README also references SaveBoardingPass and SaveData, which strongly suggests local file output is one of the app’s key persistence mechanisms.
5. Build and packaging
• build.xml, nbproject/*: NetBeans/Ant build configuration
• dist/DecibelAirline.jar: packaged runnable application
• manifest.mf: JAR entry-point metadata
This is a self-contained desktop distribution. The runtime dependency footprint is small and local; the only explicit external library visible in the tree is AbsoluteLayout.jar, used for GUI layout.
Data flow and boundaries
• Input boundary: the user interacts through Swing forms.
• State boundary: reservation state is held in Java objects (Seat, Flight) and passed between forms.
• Display boundary: ShowData and Confirmation present the current state back to the user.
• File/output boundary: boarding pass text files are generated in the distribution/output area, providing a durable local artifact.
• No evidence of network, database, or multi-user synchronization appears in the repository structure.
Architectural summary
This is a single-process, monolithic desktop reservation system:
• UI-centric
• form-driven navigation
• object-based seat/flight state
• local file output for boarding passes and saved data
• built and packaged via NetBeans/Ant
If you are drawing an architecture diagram, the cleanest decomposition is:
• Top: Swing UI forms
• Middle: reservation workflow and domain objects
• Bottom/right: local file output and packaged JAR/runtime dependencies
One useful note: the repository reflects a school/project-style desktop app rather than an enterprise booking platform. The README’s “future ideas” section also confirms that multi-flight management, database persistence, and admin authentication are not yet part of the implemented architecture.
Main entry points: RegisterForm.java Register · Confirmation.java Confirm · build.xml Ant build · ShowData.java Show data
Components 14
UI forms
Swing screens and NetBeans-generated desktop UI
- Home · Landing window for the reservation app
src/seat/main.java - Register · Collects passenger and booking details
src/seat/RegisterForm.java - Confirm · Finalizes a booking or seat assignment
src/seat/Confirmation.java - Cancel · Handles seat cancellation
src/seat/Cancellation.java - Show data · Displays reservation or seat data
src/seat/ShowData.java - About · Application information screen
src/seat/About.java
Domain
Core reservation objects and workflow state
Build & output
Ant/NetBeans packaging and local artifacts
- Ant build · NetBeans Ant project build pipeline
build.xml - NetBeans config · Generated NetBeans project configuration
nbproject/project.xml - App JAR · Packaged desktop application
dist/DecibelAirline.jar - Pass files · Local boarding-pass text artifacts
dist/A1_broadingPass.txt - Layout lib · Swing absolute positioning dependency
dist/lib/AbsoluteLayout.jar
Connections 16
- Home → Register: start booking · User moves from landing screen into booking entry
- Home → About: info · Landing screen can open the about screen
- Register → Reservation state: capture · Form populates shared booking state
- Register → Seat: assign seat · Booking details update seat allocation
- Register → Flight: select flight · Booking is associated with a flight
- Register → Confirm: submit · Completed booking advances to confirmation
- Confirm → Reservation state: finalize · Confirmation reads and finalizes reservation state
- Confirm → Show data: view data · Confirmed booking can be displayed
- Cancel → Reservation state: clear · Cancellation removes or resets reservation state
- Cancel → Show data: refresh · Updated state can be shown after cancellation
- Show data → Reservation state: read · Read-only view of current reservation data
- Reservation state → Pass files: save · Booking state is written to local boarding-pass text files
- Ant build → App JAR: package · Ant build produces the runnable JAR
- NetBeans config → Ant build: configure · NetBeans project metadata drives the build
- Ant build → Layout lib: depends on · Build includes the layout library for Swing forms
- App JAR → Pass files: runtime output · Packaged app produces local text artifacts