I have a question about Mark Cade/Simon Roberts' Golf Equipment Store (GES) case study, specifically about the Browse Catalog use case.
First interaction between the Customer and the System
1. Customer selects browse catalog 2. System presents the main page the catalog that has a list of categories and a list manufacturers
The way this interaction gets modeled in the class diagram isn't very clear. It only shows SearchProcessor(StatelessSessionBean) has a dependency(searches) on class ProductCategories.
Given the decision for the class diagram to compress manufacturer as Product's attribute, how does a list of categories and a list manufacturers get designed into class diagram just with class ProductCategories (not ProductCategory) ??
Actually, again, in the Business Domain Model, it has ProductCategory class, not ProductCategories class.
I am actually thinking we could model a list categories and a list of manufacturers with following approach
we will have a ProductCategory class, so from Inventory subsystem, you will get a list of ProductCategory classes, each ProductCategory class you will have a list of Product class objects. A list of Manufacturers can be derived from list of Products from a list ProductCategory classes. A list of categories will come from the list of ProductCategory objects. That will be derived from "Category" attribute of Product objects.
Even though Mark Cade/Simon Roberts class diagram doesn't include members and methods in it, it wouldn't hurt to show some details in it, right ? I know if I was the developer for the project, I would find it helpful to have some level of details in the designed architecture.
Anyone who read the book want to comment on my questions ?