Re: Archetypes vs Stereotypes


Doug-
I have one slight clarification about role stereotypes...you
characterize them as being good for application objects (not the domain
layer), I find them useful to think about domain objects, too (although
not as the soul source for behaviorial inspiration). Other authors who
have focused on domain layer persistent objects have ideas that can be
integrated with the notion of role stereotypes..I have been able in my
own design work (and I teach others to do so too), to combine the idea
of role stereotypes with their work. Eric Evans , for example. alks
about aggregate rools (a structurer role in role stereotype terms) and
value objects (typically information holders). Again, the my use of
role stereotyping is to see and understand behaviors and
responsibilities arranged among a "neighborhood" of objects--whether
they are in a domain layer or elsewhere.

Likewise, Coad's archetypes can be assigned typical role stereotypes,
too. (Not just because you can, but because it can be useful to
crosscheck to see whether their design is reasonable).

.