I'm working on my Factory Homes assignment and search for somebody who works/worked on it too. I confused by [House 1 -- * Wall] and [Wall 1 -- * Apperture] relations. My question is about GUI and system flexibility implied by this relations. I see two approaches:
1. Customer has rich, CAD-like interactive interface which allows to manipulate each wall/door/window separately. Pros: It meets Business Domain Model and flexibility requirements. Cons: It contradicts with use cases because of customer should simply "select and add" item to his design. Customer must specify exact wall position in this approach before system can validate design.
2. There are predefined sets ot walls/doors/windows and customer simply selects such set (i.e. planning). Pros: It's simple and meets use cases. Cons: This approach isn't flexible and slightly contradicts Business Domain Model because customer can't manage [House 1 -- * Wall] and [Wall 1 -- * Apperture] relations fully.
Could you please advice me which approach is most appropriate?
Second approach is better whereas the predifined sets are defined in the starte of the art inventory system.
About the domain model [House 1 -- * Wall] and [Wall 1 -- * Apperture] , its not managed by customer but the
application together with inventory system uses it as a rule while defining predefined sets and changes customer can make to the set.