in a recent project, i have a scenario set up like this:

• Namespace Business_Objects:
• BaseBOs
• CustomersBO
• ContractsBO
• ContactsBO
• ClientsBO..
• Customer Maintanance
• CustomersBO (subclasssed from BaseBOs CustomersBO)
• ClientsBO (subclassed from BaseBOs ClientsBO)
• ..
• Contracts Maintanance
• CustomersBO (subclassed from BaseBOs CustomersBO)
• ContractsBO (subclassed from BaseBOs ContractsBo)
• ..
• .. and so on

i was wondering if anyone got some naming convention advice for the subclassed bo's to reduce confusion.

Something like CustMaintCustomersBO and CustMaintClientsBO ... ContrMaintCustomersBO..
but then i have a namespace like customerpropertiesgroups and one customerproperties. So i cannot name them like custprop..something because it could be confused with either one.

not sure. i have around 15 BO's in total, and not all of them are subclassed in each namespace, but still its quite alot of bo's going around.

How do you name your bo's in such cases ?

Thanks

When we do this, we place them in a different namespace.  This is something that we do for every report.  So in our medical application, we probably have the PatientsBO inherited some 40+ times for each report that uses it.  So the inherited BO is still named PatientsBO, but it will reside in a different namespace.  This reduces confusion as we know that when it is all said and done, this is going to at the very least, have all of the original PatientsBO properties.  This may not work for you, but this has been a good system for us.