Designing a use case diagram, we face a challenge with three actors: Visitor, Client, and Administrator. Each has unique roles, but we must accurately capture their interactions and relationships. Specifically, the Client reserves parking spots, while the Administrator deletes them, and we need to differentiate these capabilities clearly while maintaining diagram clarity.
How can we effectively model these distinct functionalities and ensure a concise and understandable representation?Image may be NSFW.
Clik here to view.
I attempted to model the interactions between three actors and their unique functionalities in a use case diagram. I expected to find a clear and concise way to represent their relationships and actions, specifically for reserving and deleting parking spots, while maintaining diagram simplicity.
