Design Question about an "actor" in a use case

Design Question about an "actor" in a use case

• Chryso

  Ido Flatow wrote:

  Hi, (for example - an external system that sends requests)

  Do u have an example for me, about an actor not being real human :) so that I understand better

  or for example: in the bug tracking system, or a billing solution or CRM. do u know if we can have actors not being persons

  Thank you

  
  
  

• Rakesh Bhardwaj

  i think if you are good at modeling like mda or uml, it is a good place, but there is a specific area about modeling, this maybe better place
  

• SillyMS

  Hi,

  1. An actor is either a person or something that interacts with the system (for example - an external system that sends requests). An Account is more of a business entity than an actor.

  2. I guess it's a good place as any. Also you might want to try the modeling forum (id 229).

  Best of luck,

  Ido.

  
  
  

• Gerrit L

  http://www.agilemodeling.com/artifacts/useCaseDiagram.htm
  
  

• Rudemusik

  we pretty often divide the problem into different level of abstraction in order to simplify the problem and solve them one by one, thus people and invoice and account is not mingled in one view because they are researching different domain of problem, or it will increase complexity
  

• D.R.B.

  thanks a lot for giving me the tip that i can have off-topic discussion
  

• H Reyes

  thanks a lot for the url

  
  
  
• Design Question about an "actor" in a use case