What I learned
One booking across four screens
A Java Swing booking flow is easier to follow when every screen reads the same reservation.
In GlampEase, the room selection sets the room name, nightly rate and capacity. A shared Booking object carries those details into the booking, payment and confirmation screens.
A useful test is to go back and choose a different room. The total and the receipt should both reflect that choice. Checking the handoff tells me more than testing each screen in isolation.
Turning a shuttle complaint into a requirement
“Where is the bus?” is a better starting point for a design discussion than a list of dashboard features.
For the KLUST shuttle project, our team used a survey, observation and document review to understand the trip from a student’s perspective.
Knowing the location of a bus answers only part of the question. A student also needs to know whether there is room to board. That distinction explains why our design paired tracking with seat availability.
Walk through the ticket, not just the registration form
An event prototype has to work for someone arriving at the door as well as someone signing up.
The EventHub prototype covers discovery, registration and ticket management. Those tasks happen at different moments, even when the interface presents them side by side.
For a walkthrough, I would start with a specific situation: the attendee has already registered and needs the ticket now. Counting the decisions between opening the app and finding the ticket gives the review a concrete focus.