System consultants created the following series of steps related to make a flight reservation.
1a1. The customer aborts the use case.
2a1. The system determines that flights are not available.
2a2. The system displays an unavailable message to the customer.
2a3. The system refers the customer back to step 1.
4a1. The customer aborts the use case.
1. A systems analyst has developed the following classes that are related to this use case: ReserveUI, ReserveWF, FlightsLC, ReservationLC, Reservation, Seat, Flight. (Control objects end with WF, boundary objects end with UI, and lifecycle objects end with LC). Create a sequence diagram for the normal flow of events for the make a flight reservation use case. On a class diagram, the Seat objects are part of the Reservation object. You can create additional objects if necessary.
2. Create Sequence diagram for the exception listed for step 2.
3. A flight object can have several states including: Available for reservations, Sold-out, Cancelled, Boarding, Waiting for takeoff, In Transit (i.e., in the air), Arrived at Destination, and At Destination Gate. Draw a state diagram for the flight object.
4. Create a Sequence diagram for the use case associated with reserving a picnic in the PRU scenario (see page 236-237 Exercise H). This sequence diagram should be done in a CASE Tool (e.g., Visio).
5. Create a collaboration diagram that is consistent with problem 4.
6. Create a state diagram for the reservation object. This object may go through several states including: Pending Contract, Signed Contract, and Finished. This diagram should be done in a CASE tool (e.g., Visio)