This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
Hello Friends I had been going through a lot of posts here esp Parag and Harish. They have mentioned that their class diagram is technology independent. Does that means that the class diagram is just an extension of Business domain model ? If yes then how would you relate the classes in sequence & component diagram to that in the class diagram ? In my view class diagram would consist of FrontController, RequestHandler/Action class, Managers (which would be session beans), entities(which would be termed as VO & entity beans), MailManager etc. Am I going in the right direction or losing track ? Would request your valuable opinion on this. Thanks
Hi Vinays, Even I was going through some of the old forums, and what I found out was : the class diagram should be very simple. It should be an extension of the BDOM. If you start including all your Front controller, Business Delegate etc.. the class diagram will be huge and will only confuse the grader. There are people who passed with just 12 classes , so your task is to identify the "correct classes" to be included in the class diagram. All the other classes should be mentioned in the component/sequence diagram. Refer to cade's book.
Class diagram is the one which talks purely about business.
Your component diagram should talk about technologies and patterns used.
The idea is that the business and technology should not be mixed up. [ July 20, 2005: Message edited by: Sujatha Kumar ]
SCJP,SCWCD,SCBCD,SCEA Part I
Joined: Dec 15, 2004
Thanks Giju and Sujatha Sujatha, then can we co relate the classes in class diagram top that in sequence and componnent diagram ? I mean I have entity Filght in class diagram , which would be a VO as well as entity bean. Should this be explained with documentation in class diagram or assumptions doc?