Köker Ticket Automation 1.0 (Java)

This was one of my early Java desktop-automation projects. The objective was to manage passenger, trip and ticket operations for a bus-company scenario through a single graphical application. Looking back, the useful engineering aspect is not the amount of CRUD code but the need to keep related state consistent across several workflows.

Data and Workflow

Passenger and trip records could be created, edited, deleted, listed and searched. Adding seat selection and ticket sales introduced relationships between those records: a sale depended on a passenger, a trip and the availability of a specific seat.

That makes the application more than a collection of independent forms. A seat should not appear available twice for the same trip, and changes to one record should not silently leave related operations in an invalid state. The project was an early practical example of why a data model and state transitions should be considered before the user interface is finalized.

Users and Reporting

Administrator/member menus, sign-in/sign-out behavior and password-controlled access represented the user-role side of the application. Reporting turned stored records back into information that could be reviewed through the interface.

Authentication and authorization were implemented at the scale of an early student project. The lasting engineering value is the integration of user roles, persistent data, reporting and transaction-like business operations inside one desktop application.

Engineering Context

The project combined Java programming, graphical interfaces and database access. My later work on database and data systems deals with transactions, integrity, concurrency and capacity at a much deeper level; this project was one of the earlier places where those concerns first appeared as application requirements.

Historical distribution reference: indir.com