This week's book giveaway is in the Agile and other Processes forum.
We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line!
See this thread for details.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Eliminate BD, SL and DAOs in the class diagram Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of The Mikado Method this week in the Agile and other Processes forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Reply Bookmark "Eliminate BD, SL and DAOs in the class diagram " Watch "Eliminate BD, SL and DAOs in the class diagram " New topic
Author

Eliminate BD, SL and DAOs in the class diagram

shan gupta
Greenhorn

Joined: Jul 07, 2011
Posts: 7
Hi,

I am planning to eliminate Managed Beans, Business Delegates, Service Locator and DAOs in the class diagram as it is seems to distract the reader from the entity class modelling. To do this I may have to show some indirect dependencies as direct ones (example Session Facade -> Entities, instead of Session Facade -> DAO -> Entities)- similar to what is shown in CADEs book. I would be putting some notes around this in my description. Do you think this would be fine?

Any comments from those who have cleared SCEA and followed a similar strategy would help.

Joao Bosco Jares
Ranch Hand

Joined: May 13, 2011
Posts: 40
shan gupta wrote:Hi,

I am planning to eliminate Managed Beans, Business Delegates, Service Locator and DAOs in the class diagram as it is seems to distract the reader from the entity class modelling. To do this I may have to show some indirect dependencies as direct ones (example Session Facade -> Entities, instead of Session Facade -> DAO -> Entities)- similar to what is shown in CADEs book. I would be putting some notes around this in my description. Do you think this would be fine?

Any comments from those who have cleared SCEA and followed a similar strategy would help.




I advise you to use all the features needed to show your design the best possible way. Not excluding the DAO.
 
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
 
subject: Eliminate BD, SL and DAOs in the class diagram
 
Similar Threads
Dependencies to JAP entities
Class Diagram - Domain Model & Architecture Classes
Class Diagram
Are there too many classes?
JPA entities in Integration Tier