Никак не претендуя на корифея
Best practices -> Naming conventions:
Цитата:
Name structure
When possible and logical, application object names should be constructed hierarchically from three basic components:
business area name+(business area description)+action performed (for classes) or type of contents (for tables)
where "business area name" often are referred to at "the module prefix".
Example:
CustInvoicePrintout,
PriceDiscAdmCopy,
PriceDiscAdmDelete,
PriceDiscAdmSearch,
PriceDiscAdmName,
PriceDiscAdmTrans
So build Application Object names hierarchically: Module prefix + {sub module description} + {action performed}.