⇤ ← Revision 1 as of 2008-10-27 10:23:49
Size: 2989
Comment:
|
Size: 3874
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 74: | Line 74: |
== Notes == We agreed to the following formulation: '''When deleting an object, you must delete all the objects in this objects view, but only if no object in the view is referenced from outside the view, except from an list of approved objects. Then purge the relations referencing objects in the view from all objects in the approved list'' Given: Object d (to be deleted). Objectlist approved (the approved objects) The formal algorithm to do this is: 1. Find the view 'v' of object d. 1. Find the list of objects 'e' that reference an object from 'v' 1. Remove from the list 'e' all objects in approved, and all object in 'v' 1. If 'e' is not empty, the delete fails, and the user is notified about the contents of 'e' 1. If 'e' is empty, mark all objects in 'v' as deleted 1. For all objects in approved, delete any relation they have to an object in 'v' |
Action How To Delete Objects
- Assigned
- ABR+TSH+BAM
- Prev assigned
- Tasks adressed
- ["TaskX/1"]
- Time estimated
- not done
- Time used
- 0md
- Priority
- 1
- Status
- Not described
- Iteration
- 14
- Notes
Notes
We agreed to the following formulation: When deleting an object, you must delete all the objects in this objects view, but only if no object in the view is referenced from outside the view, except from an list of approved objects. Then purge the relations referencing objects in the view from all objects in the approved list Given: Object d (to be deleted). Objectlist approved (the approved objects) The formal algorithm to do this is:
The Life Cycle of an Action: Define the action: Describe information about what is to be done and how. Fill out Review the definition: Get another project group member to review the action definition, and update it. Assign people for action implementation: Done by project manager, usually the same persons who wrote the definition. Fill out Implement the action: See details below Review the action: Get another project group member to review what is implemented (code and documentation), and update it. Finish the action: Change the status to "Finished" and update the "time used" field on the action page. Please make sure that you address the below issues, when working on an action: Keep track of how much time that has been spent working on the action. If it addresses more than one task, then make a note on the action page about how much of the elapsed time that has been spent on the individual tasks. Checklist For Working On An Action
Assign people for action definition: Done at start of iteration status meeting. Fill out Assigned
Hint: Continually updating the "Time used" field will make it easier for you.