|
Size: 3467
Comment: ActionExportWebserviceContinued closed
|
Size: 3372
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| Line 4: | Line 3: |
| Line 8: | Line 4: |
| Line 10: | Line 5: |
| Line 13: | Line 6: |
| Line 15: | Line 7: |
| Line 19: | Line 8: |
| Line 21: | Line 9: |
| Line 25: | Line 10: |
| Line 27: | Line 11: |
| Line 31: | Line 12: |
| Line 33: | Line 13: |
| Line 37: | Line 14: |
| Line 39: | Line 15: |
| Line 43: | Line 16: |
Status:: Finished. Description Not Reviewed. |
Status:: Finished. Description not reviewed. |
| Line 48: | Line 18: |
| Line 50: | Line 19: |
| Line 54: | Line 20: |
Notes:: |
Notes:: |
| Line 60: | Line 22: |
| Line 66: | Line 27: |
| The Life Cycle of an Action: | |
| Line 67: | Line 29: |
The Life Cycle of an Action: |
|
| Line 77: | Line 36: |
| Line 80: | Line 38: |
| Line 83: | Line 39: |
| Line 85: | Line 40: |
| Line 87: | Line 41: |
Action Export webservice continued
- Assigned
- BAM+?
- Prev assigned
- Tasks adressed
- ["TaskX/1"]
- Time estimated
- 1/4 md
- Time used
- 0md
- Priority
- 5
- Status
- Finished. Description not reviewed.
- Iteration
- 16
- Notes
This action is a follow-up to check that we have a working export mock-up. The mock-up is a quadriga export from objects with quadriga file content model in the spolebaand example. A quick test tells me that we have such a mock-up functionality. There is however the question of export return value. Should the export functionality write and return the file (and throw an exception if the file could not be written) or should some status message be returned?
It has been agreed that the service returns the 'export-file', and this action can be closed. -- ["bam"] DateTime(2008-12-11T08:49:12Z)
Checklist For Working On An Action
The Life Cycle of an Action:
Assign people for action definition: Done at start of iteration status meeting. Fill out Assigned
Define the action: Describe information about what is to be done and how. Fill out Tasks Addressed and Time Estimated.
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 Assigned and Prev assigned if new persons are assigned.
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:
- Update the state of the action to "In Progress" when you start working on it.
- Check if the tasks addressed by this action have their status set to "In Progress". If that is not the case, then change the state of them.
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. Hint: Continually updating the "Time used" field will make it easier for you.
- Update the "Progress History" and documentation pages of each task addressed by this action when appropriate. This depends on the situation, but in general, the task pages should hold all important related information about the work done, experiences gathered, identified requirements and so on.