(responding toTomer Lev)
> Hi , A question for the Forum. > When describing a system with specifying Use cases, as we all do, what is > your favorite way to deal with Internal periodic actions that no actor > initiates (and some actor might-or might not- consume the action results > later). > There are many examples for such actions: > + Periodic internal functioning tests. > + Collection of received, but not yet handled, data/communication. > and so on. > > your educated opinions are welcome. I usually use an Actor called something like "Time" or "Timer" for periodic activity. With respect to deferring of handling of input, I don't decompose Use Cases that far, so I never need to deal with that situation - but I guess if you need to, then again "Time" or perhaps a more specific "Thread Scheduler" may be appropriate as an Actor to initiate the Use Case. I tend to think this latter sort of depth of decomposition is straying well into the province of the designer, and whether or not this is acceptable will depend on your development process. But that's not what you were asking about. HTH Paul Oldfield any opinions expressed herein are not necessarily those of Mentors of Cally ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum *************************************************************************
