• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Part II: usage of sterotypes within the class & sequence diagrams

 
Ranch Hand
Posts: 42
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have read that technology specific stereotypes should be added to the class diagram - I have decided on <<JPA entity class>> for my entities, <<JSP page>> for my views, <<stateless session bean>> for my managers/helpers and <<stateful session bean>> for my controllers. I was wondering if the classes should carry those stereotypes also when referenced within sequence diagrams...

Also, I guess it is safe to assume that when using JPA entity classes, no DAOs are needed. Furthermore I have refrained from referencing the EntityManager within my diagrams, similar to the rest of JEE services & classes.

Finally, I have assumed that persist calls don't have to be shown within the sequence diagrams, unless they are explicitly stated within the use case description (especially when using JPA).
 
reply
    Bookmark Topic Watch Topic
  • New Topic