Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Questions about a Class diagram

 
Deepak Bala
Bartender
Posts: 6663
5
Firefox Browser Linux MyEclipse IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have two question which I hope someone can clarify for me.

How much detail should I show for an analysis level class diagram in terms of navigability ? Should all classes contain information about navigability ? What about classes that are part of the BDM ? My guess is that if you are certain about the navigation, mention it. Which would mean that I would be left with specifying the navigation for a few classes and leaving the other ones undetermined (upto the developers).

If a processor component searches classes X,Y,Z,V to form class A, is it necessary to show a dependency from that processor on all four classes ? If the gist of the search operation is covered in searching X, is it enough to mention that the processor depends (searches) on X alone ?

Any replies are greatly appreciated.
 
Gabriel Claramunt
Ranch Hand
Posts: 375
Monad Scala
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
IMHO dependencies add very little value to a class diagram, and should be used only in very special cases. The other relationships (association, aggregation/composition, extension) should be reflected in the diagram.
In a component diagram, dependency is the important relationship because indicates compilation dependency.
The class diagram is a static logical view of your system, put only the relevant things :-D
 
Deepak Bala
Bartender
Posts: 6663
5
Firefox Browser Linux MyEclipse IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Gabriel, thank you for your reply. I agree with you about the dependency relationships in a class diagram. I would also be inclined only to mention general associations and extensions in the class diagram without going too deep into it. But that still leaves me a touch (only a touch ) confused about the depth of navigation that I should show in the class diagram.

Do you think all classes should definitely have navigation shown for them ? I tend to leave that to developers to figure out. They would need to determine only a few of the navigations when they begin digging into the lower levels of design. What is your opinion ?
 
Gabriel Claramunt
Ranch Hand
Posts: 375
Monad Scala
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, I don't think that all the classes should have navigation.
In a web shop application, for example, I'll definitely show a relationship between order and product, and between order and customer, but not between the shopping cart session bean and those classes, as that is a tactical decision that could be done at coding time...
I guess I could say you should show only the important relationships.
(whatever "important" means )
Is what you were thinking?
 
Deepak Bala
Bartender
Posts: 6663
5
Firefox Browser Linux MyEclipse IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is what you were thinking?


Bulls eye Thank you for your time Gabriel
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic