How itsmariodias/vehicle-management-java works
This is a desktop vehicle-management app: customers and public users browse/filter listings, customers submit purchase requests, and dealers manage listings and accept or deny requests. Project.java is the Swing entry point and UI coordinator; account and vehicle packages hold in-memory vectors, so state ends when the app closes. The README documents signup/login, account management, and sorting; sampled source confirms the UI-to-model coordination and request-state methods, but not every panel action.
Main entry points: Project.java App and panels · Dealer.java Dealer accounts · Customer.java Customer accounts · Vehicle.java Listings and requests
Components 6
Desktop UI
- App and panels
Project.java
Accounts
- Dealer accounts
pDealer/Dealer.java - Customer accounts
pCustomer/Customer.java
Vehicle marketplace
- Listings and requests
pVehicle/Vehicle.java
Shared user model
- User details
pDetails/Details.java
Other components
- Customer or dealer
Connections 8
- Customer or dealer → App and panels: uses
- App and panels → Dealer accounts: authenticates, manages
- App and panels → Customer accounts: authenticates, manages
- App and panels → Listings and requests: lists, filters, requests
- Dealer accounts → Listings and requests: deletes listings
- Customer accounts → Listings and requests: cancels orders
- Dealer accounts → User details: inherits
- Customer accounts → User details: inherits