|
Size: 3015
Comment:
|
Size: 3518
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 21: | Line 21: |
| Tasks adressed:: ["TaskX/1"] | Tasks adressed:: ["TaskA.3"]. |
| Line 27: | Line 27: |
| Time estimated:: not done | Time estimated:: 4md (lacks review) |
| Line 61: | Line 61: |
| Collect the results from the other testbed actions. Bundle these projects in a installable package, running on the local machine, reminicient of the domstestsetup.sh. The purpose of such a script is the be able to, quickly, setup an running empty DOMS system, to test against. All the data relating to one instance of DOMS must be stored in a single welldefined location, for easier coexistence with other DOMS'es. Most of the other testbed actions produce webservices. This action should provide a tomcat for all of them to run in. Having just one tomcat instance per DOMS testbed will help developers running parallel systems. Thorough documentation about the interrelations between the components should be written or compiled from the actions, and a proper INSTALL document must be created. |
|
| Line 63: | Line 72: |
| ## Detailed description of wanted output from the work to be carried out. ## E.g. Implement a utility class for writing data to a disk. The data must be base64 encoded before being written. Wrap up the Testbed webservices and Fedora so they can easily be installed in a tomcat. Write thorough documentation. |
Action Testbed Delivery
- Assigned
- ABR + JRG
- Prev assigned
- Tasks adressed
- ["TaskA.3"].
- Time estimated
- 4md (lacks review)
- Time used
- 0md
- Priority
- 1
- Status
- Not started
- Iteration
- 11
- Notes
- Depends on all the other Testbed actions
Collect the results from the other testbed actions. Bundle these projects in a installable package, running on the local machine, reminicient of the domstestsetup.sh.
The purpose of such a script is the be able to, quickly, setup an running empty DOMS system, to test against. All the data relating to one instance of DOMS must be stored in a single welldefined location, for easier coexistence with other DOMS'es.
Most of the other testbed actions produce webservices. This action should provide a tomcat for all of them to run in. Having just one tomcat instance per DOMS testbed will help developers running parallel systems.
Thorough documentation about the interrelations between the components should be written or compiled from the actions, and a proper INSTALL document must be created.
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.