Quantcast
Channel: CSLA .NET
Viewing all articles
Browse latest Browse all 764

OO design

$
0
0

Hello all,
I am quite new to the OO world, I have been working with .NET for about a year and most of the work I have done with it has been procedural in nature. I got the Expert Business Objects book and am trying to change my thinking to fit OO programming.


I have a rather general question with a mock application I'm trying to develop with CSLA.NET. I have come up with a mock use case based on the company I work for. In trying to layout the object design I've come across a problem and want to make sure I'm going down the right path.

My design has several root objects.
   Vendor, Customer, Driver, Plant, Contact

I also have a class called Address. Each one of the above objects exhibits a has-a relationship to the Address class. Further Vendor, Customer, Plant also have a has-a relationship to the Contact Class.
In the book Rocky talks about normalizing behavior, so my thought is that the way I have this setup is correct, however he also advises against overly complex relationships so this gives me pause. The mock application isn't going to be used for anything, but I would like to understand and make sure I am learning the design process correctly.
 
Anyone out there have a similar problem/solution? Am I heading down the right path? Any advice would be greatly appreciated.

Thanks,

Justin


Viewing all articles
Browse latest Browse all 764

Trending Articles