Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

use of creates accesses,delagates streoytpes in relationship in class diagrams

 
rethna pillai
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
Some authors use the streotype <<creates>>,<<accesses>>,<<uss>>,<<delegates>>,when drawing relation ship between entity and session beans and also between session bean in class diagrams..Is it UML complaint or what is the correct approcah to handle this..
Appreciate your response
 
Nishant Anshul
Ranch Hand
Posts: 72
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Rethna...i dont think these r UML compliant but for understanding only. Even Sun uses it extensively and not only these but many other routine verbs....
thnx n rgds
 
noel angel
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Stereotypes are a UML extension technique. They are used to convey additional information on a diagram. They can pretty much be used anywhere that you need to add more explanation iff they add more understanding. There are a few like <<uses>> and <<extends>> that are recognized as extensions to the use case diagramming notation and should probably not be used in other places. In addition stereotypes like <<subsystem>> , <<system>>, <<component>> might be most useful on a component diagram or deployment diagram.
Noel
SCJP, SCWCD, SCEA(part 1)
 
Ajith Kallambella
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Also make sure that the terminology that is used does not confuse the evaluator. For instance, what is the difference between <<uses>> and <<delegates>>? Isn't delegation a kind of use ? What if the class both creates the delegate entity first and then delegates the method? Now you have to make up something like <<CreatesAndDelegates>> or <<CreatesAndDelegatesAndUses>>.... : Now think of all the possible combinations and you will have to include a stereotype dictionary as a supplementary documentation
The point I am trying to make is this - agreed stereotypes are extensibility mechanisms, but don't over use them. Use them when the diagrammatic notations are either insufficient or vague in describing the nature of a particular relationship. When in doubt, try to explore alternatives that can convey the idea better and reduce the confusion. For instance, if you named your delegate as DoctorDelegate or if you used a stereotype for the delegate itself as <<delegate>> then the arrow between the client( say and EJB ) and the delegate naturally implies it has a <<uses>> relationship and it will take away the need to explicitly name that relationship.
Hope that helps,
 
Juan Rolando Prieur-Reza
Ranch Hand
Posts: 237
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by noel angel:
a few like <<uses>> and <<extends>> that are recognized as extensions to the use case diagramming notation

I agree entirely with Noel's description. Although, I think the Use Case notation he was referring to is <<include>> rather than <<uses>>.
Agree these should be used sparringly and only if they help clarify something.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic