> Using "Time" instead of "System Clock" as an actor is an interesting
> idea -- sort of an Ingmar Bergman thing. The "grim reaper" has already
> been used for death, but "father time" is very similar -- do you think
> it would be suitable as an icon?
>
Time as an actor comes under both (1) and (2). Both timers and the actual
time start to become important in the design of real-time systems. Yet, I
have found stating that a use case activates/starts every ten minutes or
daily at midnight is enough. Or you could mention that an alternative flow
takes place if some actor (or some included use case) does not finish its
task in 30 microseconds.
As soon as you have time as an actor, you have to start thinking about the
messages we send to Time and the messages that we receive from it. Are the
contents of these messages important? Or are we interested in just
receiving
timely reminders?
[Les]
Just one small point, which is that the only reason I could see a system
sending messages to 'Time' would be if you were trying to build a time
machine.
Could it really be that simple :-)
Les.
************************************************************************
* 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
*
*************************************************************************