• 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
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
Bartenders:
  • Piet Souris
  • Himai Minh

DAO's in Component and Sequence Diagram

 
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ranchers,
Need your advice.

I am showing the DAO's in the Component and Sequence diagram but i stop at that and do not mention anywhere the persistence technology that i intend to use(JAP3,Hibernate,IBatis etc etc).

Is this fine or do i need to mention the technology that i intend to use(if yes then where ?).

Thanks
ashu
 
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You can show DAO layer while interacting with Database. It is a best practise to show the layer from which your control is interacting to the database.
 
Ranch Hand
Posts: 1936
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In architecture level, I don't think we need to mention what is the technology/framework we're using.

For me, I document frameworks in other places (I'm not talking about SCEA).
 
Vamsi Mohan
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
At the high level architecture level, no need to explain about the technology. But need to mention the layers. Hence, I suggest show the DAO layer not the hibernate persistance classes.
 
Ashu Sharma
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks a lot for your valuable guidance.

I have one more question related to Component diagram.

Is it necessary that i make a component diagram per functionality or i can make only one component diagram altogether .
Mark Cade's book shows multiple component diagrams which i think could be shown in one diagram itself.

Thanks
Ashu

 
Vamsi Mohan
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It is better to create different component diagrams for different functionalities. Then, you can establish relationship between the components(if required).
 
Don't sweat petty things, or pet sweaty things. But cuddle this tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
reply
    Bookmark Topic Watch Topic
  • New Topic