Object Design - Collection of IDs

Diz posted on Tuesday, April 24, 2007

Hi,

I'm working on a little code review tracking application as a proof of concept for something larger. 

Here's an abbreviated use case:
-----------------------------------------------------------------------------------------
Developer logs in, system displays Developer Inbox, which contains:
- Code submitted (path or description)
- Other stuff describing that code submission.

Developer can add/edit/delete items in this list. 

Developer chooses Add.  System displays a detail form containing all of the code attributes, as well as a multi-selectable list (or set of check boxes) of code types.   Code Types reflect general buckets used to  determine who ends up reviewing this code.   Examples: .net, Java, Oracle - PL SQL, etc.

Developer selects the appropriate code types (one or many), and clicks OK.
-----------------------------------------------------------------------------------------
I'm good with the inbox, pick one out of an NVL and go to detail form which uses a root BusinessBase called ProjectCode.   All possible Code Types are exposed through CodeTypesNVL. 

The part I'm not sure about is what ProjectCode should contain for its selected Code Types.  It seems like I should just use a collection of IDs from the CodeTypesNVL?  I need to maintain the list of IDs, so do I want a BusinessListBase with an BusinessBase that contains just one property - ID?    That seems like overkill. 

Any advice would be appreciated.  Thanks!