• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Part II: questions regarding the class diagram

 
Mark Egloff
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello

I just started with the Part II and I have now some questions.

I have read in some other posts, that the class diagramm should be technology independent, this confuses me:

- Where is this defined? I did'nt find anything in my received assingment.jar regarding this?
- Does this mean my class diagram should only contain classes related to the BDOM? What is about Servlets, Business Delegates, Service Locator, Session Beans, DAO, Factories? Have these not to appear in the class diagram?

Detail Level of the class diagram:

- Is it genough if I list for the entity classes the relevant attributes or should I instead model "get" and "set" methods?
- Is it a good idea to mark them with a StereoType "JavaBean" if I go to use POJO instead of entity beans?

Thanks for your comments
regards
Mark
[ December 30, 2004: Message edited by: Mark Egloff ]
 
Mark Egloff
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Nobody? Please don't let me tumbling around. Thanks for any helpful comments...
 
Parag Doshi
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Mark Egloff:
Hello

I just started with the Part II and I have now some questions.

I have read in some other posts, that the class diagramm should be technology independent, this confuses me:

- Where is this defined? I did'nt find anything in my received assingment.jar regarding this?
- Does this mean my class diagram should only contain classes related to the BDOM? What is about Servlets, Business Delegates, Service Locator, Session Beans, DAO, Factories? Have these not to appear in the class diagram?

Detail Level of the class diagram:

- Is it genough if I list for the entity classes the relevant attributes or should I instead model "get" and "set" methods?
- Is it a good idea to mark them with a StereoType "JavaBean" if I go to use POJO instead of entity beans?

Thanks for your comments
regards
Mark

[ December 30, 2004: Message edited by: Mark Egloff ]



Mark,
Its generally "good" to make the class diagram technologically independent. Thats the most common approach taken by folks here. I passed my cert. by that approach. There are 2 reasons I could think of:

1. Listing only the core BDOM classes, it makes ur class diagram cleaner, less cluttered and easier to read.
2. Choosing between a POJO or a EJB is a implementation detail..its better to leave it for later stages. Same goes for J2EE design pattern classes (Business delegates, service locators etc).

The approach I have listed above is more specification class diagram rather than implementation class diagram. There is nothing wrong with going with implementation view, as you have rightly mentioned, its not listed anywhere that you cannot show servlets, ejbs etc in class diagram.

I didnt show any attributes or methods for my class diagram. I just showed the relationship, cardinality, navigability etc.
I didnt stereotype the classes either. You could do that, if you feel that it adds to the readability and communicates your design in a better way.

Again, there are no set rules for the class diagram and different people have chosen different views for the same thing with different success results

HTH
Parag
 
Mark Egloff
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
great... your answer is really that what I needed... Why we didn't met us earlier ? ; )... I think your statement would help a lot of other tumbling alices in the j2ee wonderland....
 
Deepak Pant
Ranch Hand
Posts: 446
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mark - Thanks for asking the question.

Parag - Thanks for answering it in such simple & clear terms.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic