Design Help - An object modifies and saves another object

Question

I was having problems with a design problem, and thought that the community could help me point the way in the right direction. I am modeling an employee management system for my company and came up with a design question that puzzled me.

Here is the scenario:

I have an Employee class, the employee class has a list of Office objects (where the employee works and worked). I have a requirement to create the possibility of transferring an employee between offices. There is some additional overhead for the transfer request (approvals, reviews), but at the end of the approval, my transfer object should change the list of Office Employee Object Office.

I use C #, EF4 and POCO for my objects. I am not sure how to model the transmission object. It will persist for some time and cannot be completed in a few days (permissions must be completed before it is allowed to continue). The transfer subject must know the employee for change and a new office for the employee. I feel that this is a bad design to make Employee a child of Transfer and modify it there. I'm just wondering if anyone has any tips on how to model this requirement.

Answer 1

You can consider the transfer as a completely separate object - EmployeeTransfer.

, : 1. . 2. . 3. Transfer To Office. 4. .

, - . Transfer , , Employee and Transfer To , .

, .

Answer 2

, Transfer , . Windows Workflow Foundation... QuickStart.

Answer 3

Transfer, . , Transfer Employee Office, . Transfer, , Enum ( ) Transfer Employee Office . Transfer . Transfer and Employee ( Transfer and Office) "".