File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Cade's Class Diagram Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Cade Watch "Cade New topic

Cade's Class Diagram

Giju George
Ranch Hand

Joined: Jun 08, 2004
Posts: 333
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 !!!

SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCEA
I agree. Here's the link:
subject: Cade's Class Diagram
It's not a secret anymore!