An aircraft has 200 seats; each row has 4 seats with an isle in the middle. In other words, two seats on the left side of the airplane, a space, and then two seats on the right side of the airplane. There are 50 rows. Seat reservation is problematic because multiple users attempt to reserve seats at the same time and they are not aware of one another. Obvious conflicts can occur, for example, two users attempting to reserve the same seat at the same time. For this problem, three threads that will attempt seat reservations. These threads will represent brokers who provide this service to customers. Two threads will be automated producer functions that randomly attempt seat reservations. The third producer will not be automated; instead it is a GUI Swing form that you will use to make manual reservations, as the third broker. Each producer has an ID number: 1, 2, and 3. These ID numbers will be recorded with the seat reservation so that we can know which producer did what. The GUI displays the airplane seats together with the producer ID number and if the seat is available.
To do this a white box will be drawn for each seat. An empty white box means the seat is available. A successfully reserved seat will have the producer's ID number written within the box.
To summarize, this swing GUI displays the reservation form and the airplane seating availability "diagram".
Construct a Use-Case diagram for this airline reservation problem.