This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
In factory homes assignment the first 2 use cases are bit confusing they use words component and product interchangeably. Do they mean same thing ? If yes then is it safe to assume that all products (not the entity Product) are of type component.
I'm working on same assignment now
For me, PRODUCT is assembled house. COMPONENT is just one piece you can add to your house design.
I don't really know why we need PRODUCT and HOUSE domain objects with 1-to-1 relation. The only thing
which comes in mind is that we could use PRODUCT to store some house design summary, to be able get
fast view on house design WITHOUT loading entire component structure.