DAO's in Component and Sequence Diagram
posted 16 years ago
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
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
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
posted 16 years ago
-
- Number of slices to send:Optional 'thank-you' note:
-
-
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.
VAMSI MOHAN.V
(SCJP5.0, IBM Rational Solution Designer, IBM Rational Architect, IBM RUP Designer)
posted 16 years ago
-
- Number of slices to send:Optional 'thank-you' note:
-
-
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).
For me, I document frameworks in other places (I'm not talking about SCEA).
SCJA 1.0, SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJP 5.0, SCEA 5, SCBCD 5; OCUP - Fundamental, Intermediate and Advanced; IBM Certified Solution Designer - OOAD, vUML 2; SpringSource Certified Spring Professional
Vamsi Mohan
Ranch Hand
Posts: 80
posted 16 years ago
-
- Number of slices to send:Optional 'thank-you' note:
-
-
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.
VAMSI MOHAN.V
(SCJP5.0, IBM Rational Solution Designer, IBM Rational Architect, IBM RUP Designer)
Ashu Sharma
Ranch Hand
Posts: 53
posted 16 years ago
-
- Number of slices to send:Optional 'thank-you' note:
-
-
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
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
posted 16 years ago
-
- Number of slices to send:Optional 'thank-you' note:
-
-
It is better to create different component diagrams for different functionalities. Then, you can establish relationship between the components(if required).
VAMSI MOHAN.V
(SCJP5.0, IBM Rational Solution Designer, IBM Rational Architect, IBM RUP Designer)
| Opportunity is missed by most people because it is dressed in overalls and looks like work - Edison. Tiny ad: The new gardening playing cards kickstarter is now live! https://www.kickstarter.com/projects/paulwheaton/garden-cards |