question on DAO

Is it required to show the DAOFactory and OracleDAO and the subsequents DAO e.g. SegmentDAO, IternaryDAO, PriceDAO and FlightDAO in the component diagram ?

What are the ranchers thoughts on these.

i plan to show the system related DAOs in the component diagram. still to draw. hope will not change my mind !!.

what is this oracleDAO??

Are you providing all diagrams (gifs) as links in the word document. later convert the word document to html...right? Put the html and gifs in the jar file ...right?

Hi,

Please note that I haven�t gotten my results yet.

I haven�t shown any factories in my diagrams. I also wrote a statement about that in my assumptions. This and other classes are in too lower detail level to be shown in an architectural design.

I am not alone in this opinion, because I have gotten this idea from many messages in the forum.

I have created a folder will all GIFs and HTMLs inside.

i make a small clas diagram to show some components as daos ... and show interfaces, classes subclases and factorys of daos

Originally posted by veena madhukar:
i plan to show the system related DAOs in the component diagram. still to draw. hope will not change my mind !!.

what is this oracleDAO??

Veena: Look at J2EE blueprints for DAO Explanation. The purpose of DAO is to seperate in layer your database access code. one of the goals is to make the business logic independent of the underlying datastore so theoretically you would have a factory which creates different types of dao(s) , oracle being one of them. I have one just for oracle to convey the idea. After then have dao for the rest of the entities i.e. segment, iternary, price and seat.