Hello everyone
I have a question that maybe seems to be silly, but I'm trying to figure out the best solution for some time and need some help.
I am making a small web application for clothing company (it's my first independent project). It is supposed to handle info about how the products are designed (lengths, fabric, buttons and so on).
There is a need to define the sizes for every product as well as the attributes the product has, and then specify the values for each combination(ex: sleeve length for size S: 40 cm, and so on...).
So the attribute - like sleeve length - depends on the size and I'm not sure how to arrange the classes in order to correctly explain the relation: product-size-attribute.
1. should the product aggregate the size and size should aggregate attribute?
2. or maybe product should aggregate both size and attribute and then maybe I'll need one more object which will depend both on size and attribute?
Am I somewhere close to the good solution? :/
Please help
I have a question that maybe seems to be silly, but I'm trying to figure out the best solution for some time and need some help.
I am making a small web application for clothing company (it's my first independent project). It is supposed to handle info about how the products are designed (lengths, fabric, buttons and so on).
There is a need to define the sizes for every product as well as the attributes the product has, and then specify the values for each combination(ex: sleeve length for size S: 40 cm, and so on...).
So the attribute - like sleeve length - depends on the size and I'm not sure how to arrange the classes in order to correctly explain the relation: product-size-attribute.
1. should the product aggregate the size and size should aggregate attribute?
2. or maybe product should aggregate both size and attribute and then maybe I'll need one more object which will depend both on size and attribute?
Am I somewhere close to the good solution? :/
Please help