rafael liu wrote:That's what I thought at first, but there's no way to have a Product without a CompletedDesign, there simply is no Use Case that would build a Product without creating a respective CompletedDesign. And even if it had, there is no Use Case that would pick this pre-built house.
CompletedDesign is for me an "interaction with the system", this way in the same interaction the Customer can build 2, 3, * houses. Anyway, I'm changing this domain model..
rafael liu wrote:Wow, that's weird, my reply appeared as an edit of yours..
I wrote:
CompletedDesign is for me an "interaction with the system", this way in the same interaction the Customer can build 2, 3, * houses. Anyway, I'm changing this domain model..
In your understanding the House itself would be in the Inventory System?
The company has recently invested in a state of the art stock inventory and management
system that controls all inventory and valid combinations of inventory in the Factory Homes
catalog. This system is accessible using a well-defined set of web services.
rafael liu wrote:
The company has recently invested in a state of the art stock inventory and management
system that controls all inventory and valid combinations of inventory in the Factory Homes
catalog. This system is accessible using a well-defined set of web services.
I was designing it as a subsystem that would store and retrive components for me. The Wall, Door, etc in my application would be just for binding the Web Service response into a POJO, it wouldn't be store in my data base. The House, Product, etc would be in my data base only with references to its components.
I don't see how it would work if this system was only for validation.. You would pass a set of components combination just to check validity?
Zheng Wangz wrote:And if we could change it to IS-A relationship in the class diagram. I think it will make sense.
He puts the "turd" in "saturday". Speaking of which, have you smelled this tiny ad?
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|