|
Size: 3099
Comment:
|
← Revision 13 as of 2010-03-17 13:09:10 ⇥
Size: 3719
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| Assigned:: KFC | Assigned:: KFC + JRG |
| Line 21: | Line 21: |
| Tasks adressed:: ["TaskX/1"] | Tasks adressed:: [[TaskA.5]], [[TaskE.1]] |
| Line 27: | Line 27: |
| Time estimated:: not done | Time estimated:: 3md |
| Line 33: | Line 33: |
| Time used:: 0md | Time used:: 3md |
| Line 39: | Line 39: |
| Priority:: ? | Priority:: 7 |
| Line 45: | Line 45: |
| Status:: Not started | Status:: In progress |
| Line 51: | Line 51: |
| Iteration:: 11 |
Iteration:: 12 |
| Line 57: | Line 56: |
| Notes:: | Notes:: Code style and review needed |
| Line 76: | Line 75: |
| The Summa WSDL is here | |
| Line 77: | Line 77: |
| ## (that is from Stable, but 1.0 shouldn't change much) ## http://kredit:8480/summaws/services/SummaSearch?wsdl |
|
| Line 78: | Line 80: |
| '''Update:''' Received updated simpler [[attachment:searchWS.xml]] 2008-09-08 | |
| Line 79: | Line 82: |
| ## The result of a search can be seen in attachment:searchDesc.xml '''Update:''' Updated result [[attachment:searchResult.xml]] 2008-09-08 Implementing a simple bridge between the two should be doable in reasonably short time. Steps needed is programmatic briding and exposing as webservice with Summa WSDL. I estimate 1 md for each, and 1 md for review. |
Action Testbed Search
- Assigned
- KFC + JRG
- Prev assigned
- Time estimated
- 3md
- Time used
- 3md
- Priority
- 7
- Status
- In progress
- Iteration
- 12
- Notes
- Code style and review needed
We need a testbed search module.
The final search module will be Summa, but since that is not ready, we will need to look at single object search systems.
We have the Summa WSDL, so the idea is to try to wrap simple search in that API.
The Summa WSDL is here
Update: Received updated simpler searchWS.xml 2008-09-08
Update: Updated result searchResult.xml 2008-09-08
Implementing a simple bridge between the two should be doable in reasonably short time. Steps needed is programmatic briding and exposing as webservice with Summa WSDL. I estimate 1 md for each, and 1 md for review.
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.