B
Brad Pears
I am working on a vb.net 2005 project and I have an OO design question...
I have a form on which data on the form is made up from three related tables
in a 1->M->M situation. ie... Table 1 and Table 2 are in a 1-M relationship
and Table 2 and Table 3 are also in a one to many relationship (using a
different relationship key then table 1->table2)
I am unsure how I should develop the business classes, whether I should have
just one business class which includes collection properties to house the
two 1-M relationships or whether I should create three business classes (one
for each table) with the high level class containing one collection property
for it's 1-M relationship with the 2nd class and in the second class, also
include a collection property to house the 1-M relationship it is in with
the 3rd class...
What would be a good business class design for this type of scenario? I am
very new to OO design and just trying to get my feet wet!!
Thanks, Brad
I have a form on which data on the form is made up from three related tables
in a 1->M->M situation. ie... Table 1 and Table 2 are in a 1-M relationship
and Table 2 and Table 3 are also in a one to many relationship (using a
different relationship key then table 1->table2)
I am unsure how I should develop the business classes, whether I should have
just one business class which includes collection properties to house the
two 1-M relationships or whether I should create three business classes (one
for each table) with the high level class containing one collection property
for it's 1-M relationship with the 2nd class and in the second class, also
include a collection property to house the 1-M relationship it is in with
the 3rd class...
What would be a good business class design for this type of scenario? I am
very new to OO design and just trying to get my feet wet!!
Thanks, Brad