This might sound like an excessively broad-level question, but here goes...

Our development team is having some differences of opinion regarding setting up business objects in the middle tier of a Winforms app that will use Web Services. We have a large amount of VFP business logic that we're looking to port to C# in the middle layer.

The differences in views really boil down to the # of levels of abstraction in setting up business 'classes'. We have one developer who actually wants to 'mirror' every winform and control with corresponding logic in the middle tier.

My preference is to identify all pieces of business functionality/requirements, and set up methods and properties accordingly. (For instance, if saving a financial transaction involves 7 steps, then set up 7 methods in the middle layer). I do have a general concern about setting up so many levels of abstraction that excessive overhead is introduced.

Any thoughts? I can go into more detail if need be...I'm just looking for some general philosophies.

Thanks,
Kevin