• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

UML stereotypes

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,


I tried to find something about UML stereotypes form Sun, however everything I've found is this page:
http://java.sun.com/developer/technicalArticles/J2EE/patterns/UseOfUML.html

And now my question - the SessionEJB does no specify if bean is statefull or stateless. How can I mark that on my diagram?

The same goes for EntityEJB - how can I mark it as CMP or BMP?

Thanks
 
Ranch Hand
Posts: 190
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
maybe the following link is of some help :

EJB components to UML elements mapping

Regards
 
Ranch Hand
Posts: 128
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I used to put <<Stateless>>, <<Stateful>> to the session beans or <<Entity Bean>>, I usually don't specify if its a EJB 3.0 or 2.1 that will clutter the diagram and will not add any new information about it.

I don't put the Home, Remote and creation objects (like InitialContext) in the diagrams, if you do that your diagram will be 30% bigger and will confuse your developers, they know how to create that kind of components unless you are creating a framework components like a ServiceLocator Cache which will have a special implementation.

if you want to go to a higher level of detail then you will put that, for example if your developers are not well experienced with the EJB behavior.
 
Ranch Hand
Posts: 208
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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 ]
 
Leszek Sliwko
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks guys!

I guess if it's not so clear for current SCEAs, then Sun also won't be so picky.
 
Ranch Hand
Posts: 213
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Or it might be what we lost points on.

Sorry, I shouldn't try and scare you like that.
 
Leszek Sliwko
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have bought a assigment already - too late to be scared ;-)
Anyway - I spend more time drawing uml than designing a system :-)

Can you point to some uml-perfect example uml diagrams for comparsion?

I have a Distilled UML, Cade and other books, but those are not 'how-to-draw-perfect-uml-fot-dummies-and-even-more-stupid-dummies' books.

Something useful for anyone reading this - simple and stupid - just type "uml j2ee" in Google Images...
[ January 29, 2008: Message edited by: Leszek Sliwko ]
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic