Course project use case diagram using the Include dependency: Each of the use cases in the extension of the problem statement shares the logic to update the seat status and immediately notifies anyone who might be trying to view the show for the affected seat. To show this, we have pulled out the common flow of events that updates the seats and notified the Select Seat use case.
The new use case is called Update Seat Status.
The existing use cases now depend on the Update Seat Status use case. Dependency arrows (dashed lines) now point from the existing use cases to the new use case. The dependency is stereotyped as an <<include>> dependency. Because the new Update Seat Status use case has to communicate with the Select Seat use case, add an association to indicate that there is an interaction between the use cases. The association uses a solid line without an arrowhead.
Includes Stereotype Solution: The existing use cases now depend on the Update Seat Status use case.
Dependency arrows (dashed lines) now point from the existing use cases to the new use case.