I've got the Assistant as a separate actor to Manager and I have drawn the relationships according to the question...but I don't know whether the question covers everything that happens. For example, it may be the case that Kim the manager does issue videos sometimes. But I haven't drawn that relationship in because it would be an assumption. Would it be ok to make assumptions, or should we only work from what we have in front of us?
EDIT: I have found out the answer. The actors don't represent specific named people - they represent roles, so Kim the manager wears an Assistant's hat in the use case 'process video return' and a Manager's hat in 'update video list'.
Therefore, in both of these these diagrams, the Manager should only have one relationship - with the use case 'update video list'.
2 comments:
Absolutely right - the roles are the "jobs" of the actors. These are specific and distinct. each actual person who works with the system may be different actors in terms of the use cases at different times
Don't you just love a simple, direct Use Case diagram.
This is who needs to do what.
:)
And it all flows out from there.
Post a Comment