Help with use case model...

reagan123 posted on Monday, December 07, 2009

Hello everyone!

Quick question.  Lets say I have two objects,  a "Car" object and a "Person" object.  I need to allow the user to associate people and cars in order to be able to track who is responsible for a car and their role.

Would I add a personnel child collection to my Car class or would this scenario have its own class?  Any feedback or better suggestions greatly appreciated.

CarA   --> John Doe/Mechanic
           --> Chris Adams/Technician
           --> Jane Doe/Owner

CarB  --> Tom Smith/Mechanic

triplea replied on Monday, December 07, 2009

I assume what you want to achieve is to have a list of cars for which you want to edit the associated personel. I have done this both ways, have a "use case" root object which has a collection of (in your example) cars, each having a child employee list. Other way is to just have a BLB list of cars which on save would start your db transaction and serve as your root object.

Otherwise if you edit 1 car at a time it should not be different than the PTracker example of Project/Resources.

reagan123 replied on Monday, December 07, 2009

Thanks you for the reply.  I appreciate it. 

I always like to try to get some insight from different people in order to see the different ways of solving the same issue.

I'll also re-look at the PTracker library again.