• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

actors and domain models

 
Ronald Wouters
Ranch Hand
Posts: 190
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

are there any guidelines on when you should put an actor also on a domain model ? By that I mean should you put things like Customer, Supplier, Employee which are actually users/actors for the system under design, also on the domain model. Maybe more interestingly, when should you not do this ?

Regards.
 
Hong Anderson
Ranch Hand
Posts: 1936
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
An actor is a person or thing that initiates use cases.

It is different from Entity in domain model, for example, a customer who starts a use case is different from Customer Entity in domain model.

To be more specific, a customer actor is a real person (or an example person) who exists in real world, but Customer Entity is only a abstract thing that exists in software.

So the question is not should or not, but it's in domain model or not. If Customer needs to be in domain model, put it.
[ December 18, 2008: Message edited by: Kengkaj Sathianpantarit ]
 
Scott Soo
Ranch Hand
Posts: 83
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

In addition to Kengkaj's advice, I think "Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition) - Craig Larman " will help to enhance understanding.

Thank you.
 
Ronald Wouters
Ranch Hand
Posts: 190
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for both your advise.
It is most helpful.
 
Hong Anderson
Ranch Hand
Posts: 1936
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You're welcome.

It's good that my comment is useful.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic