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 ?
Sun Certified Developer for the Java 2 Platform
Sun Certified Enterprise Architect for the Java Platform, Enterprise Edition 5
Joined: Jul 05, 2005
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 ]
SCJA 1.0, SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJP 5.0, SCEA 5, SCBCD 5; OCUP - Fundamental, Intermediate and Advanced; IBM Certified Solution Designer - OOAD, vUML 2; SpringSource Certified Spring Professional
Joined: Oct 02, 2008
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.