d6chung
![[Avatar]](/images/avatar/22b1cd168ec628442b3d4dc00fca434b.png)
Joined: 2009/07/22 11:30
Messages: 68
Location: Honolulu, HI, USA
Offline
|
|
|
|
Actors take action on the system you are describing. Are you asking whether it is possible for a system to take action on itself? Does it make sense to model that in a use case? If you really feel the need to model this, ask yourself whether you're within the scope of the domain you're modelling and consider using a different diagram to illustrate what you're trying to describe.
Keep in mind that the use case descriptions describe the interaction between the system and the actor(s). If the system is doing some self-processing then you would simply state that in your flow of events and how the results of the processing is presented to the actor(s) for them to take further action.
However, by "a system", one could assume you mean some system acting upon the system you are describing. I've seen "time" used as an actor and I've seen sensor devices used as actors as well. If that's your case, then yes, it would make sense to depict these as actors in your use cases.
Hope that helps.
|