thanks for you reply and sorry for my english, well, when you make a entity, this entity have n points of views, what is the best : put all points of view in the same BO or make a light BO with aggregation to anothers custom classes?

an example:

I have a Article entity and this entity is used for n Departments, Marketing, suppliers, production, etc. i make a BO Called Article with all methods and properties for all departaments OR

a have a Article entity with aggregation to custom classes , every custom class is for a departament, i have oArticleMarketing, oArticlesupplier, oArticleProduction

well what is the best design?, exist another form for this design?

Best Regards

>Francisco,
>
>>Regards, i stay in doubt about the interfaces (UML) and what is his relevancy in OOP MM VFP development , when i can use the interfaces?
>>
>>i start a dev with UML and roundtrip, but i have a class like Article, and i add aggregation for oArticleMarketing object, where i put all methods and properties for this departament, and make mi BO Light, but it's good add anothers n class for every department (Marketing, Account, Financial, etc)?>>
>
>I don't really understand the question...could you reword it add a little more detail?
>
>Regards,