Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Cade's Class Diagram

 
Giju George
Ranch Hand
Posts: 333
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't know whether this is a "beaten to death" topic or not. I am confused with the cade's class diagram. The navigability between creditcard and customer is from creditcard->customer. I suppose it should be in the other way. You can reach creditcard only through customer.

I read an article posted in this thread :-
http://www.coderanch.com/t/152852/java-Architect-SCEA/certification/Cade-Class-Diagram-Please-Help

But if we do it in either way, it will only create more confusion, especially when the more and more classes are added to it.

The same problem happens with the relationship between ProductCategories and Product. It should be ProductCategories -> Product (each productcategories can containmultiple products)

Also, the many-to-many relationship between productcategories and product in the class diagram is violating the BDOM which shows one-to-many relationship between productcategories and product .. each product belongs to ONLY ONE productcategory

Am I missing something, or confusing myself ???

Please guys, your thought on this one much appreciated !!!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic