Hi,
I have just read the case study from Cade & Roberts' book and it gave me a picture about how to approach the diagrams. However, I have some questions about the diagrams in the book if you can help me.
DOM and Class Diagram:
1. The relationship between Product and ProductCategories is not the same. In the DOM it's 1-N while in the Class Diagram it's M-N.
2. How the relationship between ProductCategoris and Manufacturer is maintained? It's kinda hidden in the Class Diagram behind the M-N relation between Product and ProductCategories.
Class Diagram:
1. Why is the association between Address and Customer is pointing to Customer and not the other way around?
Currently it isAddress ----> Customer
Should not it beCustomer ----> Address
Usually if you have two
Java classes one for Customer and the other for Address, the Customer class has an instance variable of type Address. The Address class has information related to street, zip code and the like, simply it doesn't know about the Customer class. Moreover, Customer ----> Address is the approach used in the blueprints Adventure Builder Application.
2. Same thing for the association between CreditCard and Customer.
Component Diagrams:
1. What are IAccounting, IShipping, IPayment and the other two interfaces represent and used for?
Sequence Diagrams:
1. Should I use classes and objects in the real assignment or components as Cade and Roberts did in the case study?