I am creating a use case diagram for a Go-Karting booking system. I have identified the actors and use cases for my diagram, however I am unsure as to their validity.
For example I have a Member Actor which is connected to a Booking use case, the problem is if the Member is booking online they need to Login first, but they don’t have to Login if they are booking at a bookings office, further more after Login a member can also check is account details and statistical data.
My use case diagram:
[Member] -------- Login <–uses— View Account Details and Statistical Data
| ^
| |
Booking —uses----
Would I include the “View account details” use case in the main diagram or describe them in the detail description of the “Login” use case (using a sub diagram)? And would I show the uses association of “Booking” and “Login”.
“View Account Details” seems like a worthwhile use case to use in your main diagram.
As for regular booking versus online booking, I would use inheritance where the online booking use case would then include the log-in and view account details use cases.
“View Account Details” seems like a worthwhile use case to use in your main diagram.
As for regular booking versus online booking, I would use inheritance where the online booking use case would then include the log-in and view account details use cases.