• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Stereotypes

 
Jim Janssens
Ranch Hand
Posts: 210
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have two questions about stereotyping:

1. When I have a 'service' on my class diagram, but I do not want to call it a session bean, which stereotype should I use ? First I was thinking about naming it myself, like: <<facade>> . But then again, <<boundary>> is more standard I guess. Are there any rules about this ?

2. Is it valid to use stereotypes to indicate patterns ? Like; <<AbstractFactory>>

Thanks.
 
Required Field
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

1. What do you mean "'service' on my class diagram"? Is your class a strict service class? If yes, then that brings us to the next question - whether it is a stateless or stateful service? 'Boundary' is used for classes that are supposedly external facades to the component/sub-system you are writing. I suppose from a certification standpoint, you would be more correct if you choose standard notations like 'boundary' instead of 'facade'.

2. One almost conventional method for indicating design pattern usage in UML diagrams is using collaborations (dotted ovals, connected to elements on your diagram and giving them roles).
http://www.jot.fm/issues/issue_2002_07/article3
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic