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

[Jesper Rugaard Jensen]

This is an old discussion. I've sometimes felt that it feels wrong to use time as an actor (or thread scheduler or whatever), as this clouds the real purpose of the use case. I often usethe role responsible for configuring the "Internal periodic action" and make this role the actor. The actor then initiates the use case. This has the beneficial side effect that it is suddently possible to change the settings, which can be a problem if there is no mention of this in the other use cases/requirements. I have seen cases where it is not specified that e.g. the interval of running paychecks can be changed or how and how much to log of internal actions. Often, the actors are the ones with an interest in this use case and shold therefore be connected to it. On the downside many people don't like use cases that are not finished in a setting and this scheme makes use cases that can be stretched out over a long period of time.   The use case thus reads something along the lines of:   Run Paycheck: The Accontant tells when and how often paycheck calculation should be done. At the specified time the system: a) Calculates paycheck for the employes using .... b) Prints the paychecks and mails them to the .... c) ....   A collection of received but not yet handled data/communication are not relevant unless they are used (I thing). I would describe the collecting of these data in the use case that uses them (or in the use case that receives them (either by creating them (a log) or by receiving them from an external system (actor))   Best wishes -----Original Message----- From: Tomer Lev [mailto:[EMAIL PROTECTED]] Sent: 13. januar 2002 08: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