Use Case Object Design and Naming

SomeGuy posted on Tuesday, January 22, 2008

Use case based object design means you are going to have multiple 'versions' of some objects. A 'Lite' version to just retrieve Id, Name, etc., no child objects, few if any joins in the SP, and 'Full' version for editing, etc.

What is the common practice for naming these objects? VendorLite; VendorLookup; VendorEdit; VendorForEditing? FullVendor? VendorWithChildren?

E

 

 

simon_may replied on Tuesday, January 22, 2008

I am using seperate namespaces for the objects implementing a use case