use case problem
6 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   voros_sandrine
Posted On:   Wednesday, February 4, 2004 08:36 AM

Hello,

I would like to develop an application in which a user controls a robot that holds a camera. The images provided by the camera are analysed by the system to define "high level" commands (such as track a target). Thus, the system has a model of the targets. Some of the target's positions are also known thanks to position sensors

My problem is that I don't know how to define my actors : is the only actor the surgeon or can/must the robot, the camera and the position sensors be considered as actors too ?

thanks for your help

Re: use case problem

Posted By:   Simon_Ablett  
Posted On:   Monday, February 9, 2004 08:26 AM

Any object that does not form part of your system and which your system interacts with is an actor. So if your program merely sends commands to or receives them from the robot then I would say that the robot is probably an actor. If, on the other hand, your program forms part of the robot then it should not be an actor. Personally, from your description, I would say that the surgeon, camera and robot are probably all actors.

Regards.

Re: use case problem

Posted By:   Anonymous  
Posted On:   Sunday, February 8, 2004 05:35 PM

My site URL should be:
[Visit: All about UML]

Re: use case problem

Posted By:   Anonymous  
Posted On:   Sunday, February 8, 2004 04:43 PM

I think the only actor is "User".

Actor is the role that can get benefits from the system.
I think the robot is a part of the system.

[Visit: All about UML]

Re: use case problem

Posted By:   c_m  
Posted On:   Friday, February 6, 2004 02:44 AM

You must first answer the question what is the boundary of the system/application you are describing? Actors are external to this boundary.


If your application (the system) receives messages from the user, position sensors and interacts with other external devices/users (camera), and these are not considered part of the system then these are all actors.


However, components (image analyser) which are part of the system will not be actors.


Although system boundary definition may appear trivial and is often neglected in use case analysis, it is an essential step in order to build an accurate use case model and fully understand what your system does.


Hopes this helps


CM

www.liemur.com

Re: use case problem

Posted By:   Anonymous  
Posted On:   Thursday, February 5, 2004 04:51 AM

Who will be reading the use cases? What will they use the information for? What difference would it make to them?

Re: use case problem

Posted By:   Christopher_Koenigsberg  
Posted On:   Wednesday, February 4, 2004 08:55 AM

I think only the surgeon would be an "actor"

About | Sitemap | Contact