When designing an n-tiered (n-layered) application using custom entities (aka business entities, domain objects, business objects, entity objects) , should you create entities and DAL functions for your lookup tables? For example, you have a lookup table called status. It contains three values "not started", "in progress", and "completed". The lookup table is used to fill dropdownlists. How do you handle this with custom entities? Do you just create a status entity that only has two properties, StatusID and Status? I'm just wondering how people handle it because the n-tiered approach feels a little like overkill just to fill a dropdownlist of 3 values but I will do that if that's what's supposed to be done.
...
Go to the complete details ...