|
Size: 3085
Comment:
|
← Revision 18 as of 2010-03-17 13:09:13 ⇥
Size: 3626
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| Assigned:: | Assigned:: ABR + JRG |
| Line 21: | Line 21: |
| Tasks adressed:: ["TaskX/1"] | Tasks adressed:: [[TaskA.5]] |
| Line 27: | Line 27: |
| Time estimated:: not done |
Time estimated:: 6md |
| Line 33: | Line 32: |
| Time used:: 0md | Time used:: 0.5md (ABR) |
| Line 39: | Line 38: |
| Priority:: ? | Priority:: 9 |
| Line 45: | Line 44: |
| Status:: Not started | Status:: In progress |
| Line 51: | Line 50: |
| Iteration:: 11 | Iteration:: 12 |
| Line 69: | Line 68: |
| We need a bit storage for our test bed. This involves making an implementation of bitstorage working on local disk, but presenting the interface we use on the real bit storage, wrapping it in a webservice, and documenting it. | We need a bit storage for our test bed. This involves making an implementation of bitstorage working on ''local disk'', and providing the interface we use on ''the production bit storage''. For the production system we will use a webservice as interface to the bitstorage. The wsdl/java interface for this webservice must be decided. A testbed implementation of this interface must be made, which will store the files on the local disk. The relevant documentation of the webservice must ofcourse be made available. |
| Line 71: | Line 73: |
| See http://wiki.statsbiblioteket.dk/domswiki/SummaryAPIs and http://wiki.statsbiblioteket.dk/domswiki/Bitstorage_API, for the prototype interfaces. These should be used as the basis, but must probably be changed for the testbed system. |
Action Testbed Bit Storage
- Assigned
- ABR + JRG
- Prev assigned
- Tasks adressed
- Time estimated
- 6md
- Time used
- 0.5md (ABR)
- Priority
- 9
- Status
- In progress
- Iteration
- 12
- Notes
We need a bit storage for our test bed. This involves making an implementation of bitstorage working on local disk, and providing the interface we use on the production bit storage. For the production system we will use a webservice as interface to the bitstorage. The wsdl/java interface for this webservice must be decided. A testbed implementation of this interface must be made, which will store the files on the local disk. The relevant documentation of the webservice must ofcourse be made available.
See http://wiki.statsbiblioteket.dk/domswiki/SummaryAPIs and http://wiki.statsbiblioteket.dk/domswiki/Bitstorage_API, for the prototype interfaces. These should be used as the basis, but must probably be changed for the testbed system.
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.