Question 2: Reservation states (20 points) Draw a UML state diagram which indicates the states that a reservation can be in. You will need to infer the appropriate states from the description provided to you by the client; examples include scheduled, missed, overdue, and complete. Use "event[guard]/action" syntax where appropriate to indicate what causes state transitions in your diagram: the event describes what causes the state transition, the guard describes the condition that must hold, and the action describes some step which occurs as a result of the transition. You may assume that reservations cannot be reopened. Question 3: Reservation activity (20 points) Draw a UML activity diagram that shows the process of a customer creating and keeping (or missing) a reservation. Remember to include cases for ordering services, canceling the reservation, and so forth. As above, assume that reservations are not reopened even if they are canceled. Question 4: Comparing diagrams (10 points) UML has different diagram syntaxes to address different problems. Above, you created a state diagram and an activity diagram for the same purpose: tracking reservations. Which diagram was easier to use for this purpose? What about it made it more suitable to the task? For the other diagram, what things were harder to express using that syntax? Question 5: When not to diagram? (10 points) Some requirements are best expressed as a simple textual description. Given the above requirements outlining how the business runs, identify two rules which cannot be expressed easily using the syntax of these three UML diagrams. Question 6: Requirements discovery (10 points) Requirements are rarely complete the first time they are provided. Consider the above requirements, the domain of hotel reservations, and the billing process. Suggest a requirement which may exist even though the client has not expressed it. Then, explain how you would adjust one of the above diagrams to accommodate this change