Use cases question
- From: Antonio Santiago <santiago@xxxxxxxxxxxxx>
- Date: Thu, 28 Jul 2005 09:47:21 +0200
Hi,
I am reading "UML 2 for dummmies" (for me :) ). It says when I have collected the use cases and describe it as seen by the actors. After that says I represent the system as a class with use cases as operations.
My problem is the system I am modeling has three subsystems:
-Reader: Reads data.
-Visualizer: Show data on screen.
-Timer: Generates events to Reader and Visualizer subsystems. For exampe: orders to read every minute a refresh visualizer every twenty seconds.
Here exists use cases that user doesn't see (those use cases where Timer is the actor).
I need to represent every subsystem as a class with its use cases as operations? or only one big class representing entery system? I last, then I need to put operations (use cases) that are generated by Timer subsystem??
Any ideas? Thanks.
.
- Follow-Ups:
- Re: Use cases question
- From: H. S. Lahman
- Re: Use cases question
- Prev by Date: Re: OO Design induces an existential crisis
- Next by Date: Re: OO Design induces an existential crisis
- Previous by thread: Repositories, package dependencies, and domain-flavoured exceptions
- Next by thread: Re: Use cases question
- Index(es):