• 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:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

Part 2- Sequence diagram and component diagram

 
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi I have few questions about approach I took, kindly advise

1) I prepared a general sequence diagram to show general flow, where I did show jsp-->faces servlet -->managed bean-->bus delgt -->service loc-->session bean-->entity manager.
In the sequence diagram specific to usecase i am planning to skip showin EntityManager and FacesServlet, rather will use a stereo type <update> from session bean to entity.
Does it sounnd OK?

2) I did not show FacesServlet and EntityManager in class diagram, is it still OK to use them in generic sequence diagram (Not business usecase sequence diagram)?

3) Is it OK to show FacesServlet and EntityManager in component diagram? as I cant show session bean directly accessing database.
I have used DAO but not for DB access, as I was planning to show EntityManager as a component in integration tier.
reply
    Bookmark Topic Watch Topic
  • New Topic