>>Hi,
>>
>>I kind of sort of understand the purpose and use of BIZ object. But I am a little confused on what is the better practice for BIZ object in the following case (simplified).
>>
>>Say you have a parts stock room system. I have a class that is used as BIZ object for validating entries in the parts stock room table. Another typical thing that has to be done in this system is posting receipt of some quantities for the parts. In the UI tier this is done in a batch mode: User has a grid-like form where he/she enters a bunch of parts and the QTY received for each part. This UI tier will then pass the information to the BIZ object that will update (via DA tier) the in-stock quantities. My question is, do I simply add a method of batch posting of receipt items to the Stock Room Parts BIZ class or is it better to have a separate class for using with batch processing?
>>
>
>Seems to me you're thinking about this backwards. A set of business objects should be the "engine" for your application, handling all the operations that need to be done. The UI then simply calls on those objects to do what it needs. That is, the UI design should not drive the design of business objects.
>
>

Thank you. Back to working on understanding on how to design business objects.