tags:

views:

74

answers:

1

Hi

Im building a windows app in c# and I have the following design question :

I have the following object structure : Parent -> Child Collection - > Child - > Grandchild collection -> Grandchild.

The use case requires that I use my Parent object in stages. Eg. Make a new instance of parent. Populate parent and save. At a later stage I would fetch parent and populate the children and save. At a final stage I would then fetch the parent again and populate the grandchildren for the specific child objects and save.

Is this a bad object model? If so, how will it be possible to split this huge object model into smaller models ?

Thanks

+1  A: 

I think this question can only be answered if we know the domain of the problem. A design is (mostly) right or wrong depending on how it fits the situation.

Andrew Bullock