RE: (ROSE) Periodic Internal Action - Use case specification answer

[Eeles, Peter]

Hi Tomer,   Since use-cases are always initiated by an actor, then we need an actor! One option is to introduce an actor such as a Timer. This is a common technique for representing time-based actions.   Regards, Pete ===================================== Peter Eeles Architecture and Technology Team Lead Regional Services Organization (UK) Rational Software Email: [EMAIL PROTECTED] Mobile: +44 (0)7796 331061 ===================================== -----Original Message----- From: Tomer Lev [mailto:[EMAIL PROTECTED]] Sent: 13 January 2002 07:32 To: [EMAIL PROTECTED] Subject: (ROSE) Periodic Internal Action - Use case specification answer 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. Thanks Tomer Tomer Lev SW Team Leader Taldor-Tici Software Systems. Voice: 972-8-9484876 Fax:   972-8-9484897 Email: [EMAIL PROTECTED] http://www.tici.co.il Mailing Address: 10 Plaut St. Tamar science Park P.O.B 2244 Rehovot 76122, ISRAEL