• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
  • Piet Souris
  • Himai Minh

Cade's Class Diagram

Ranch Hand
Posts: 333
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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 :-

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 !!!
no wonder he is so sad, he hasn't seen this tiny ad:
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earth
    Bookmark Topic Watch Topic
  • New Topic