Stereotypes are always a tricky issue, as clear and concise guidelines are hard to find... in strick UML, is <<stateless session bean>> a stereotype? I don't know.
Use stereotypes to add value to your diagram. These are some of the stereotypes I used in the class diagram for my SCEA-assignment:
<<stateless session bean>>
<<stateful session bean>>
<<message>>
<<message-driven bean>>
<<abstract factory>>
<<factory method>>
<<singleton>>
<<managed bean>>
<<business delegate>>
<<
JSF>>
Now, I did not get a full score on my class diagram, I scored 37 or 38 out of 44. It might be that this is partially due to the stereotype-usage - I don't know. But in RL, I find that most developers find using design
patterns as stereotypes to be very helpful.
[ January 22, 2008: Message edited by: �dne Brunborg ]