When drawing their first use case diagrams, my students (including some
of my best) sometimes identify the system under development as an actor.
I've been telling them not to do this, since my favorite sources don't
do it, but lately it has been bothering me.
When the system is doing something like scheduling activities for
regular or delayed execution, I have seen authorities use a "system
clock" actor. Also, in some environments it is quite right to say that
the system provides services such as printing. If the system looks like
an actor, walks like an actor, and quacks like an actor, what is it?
-Eric
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
