






Team SPEW - Week 12 - Status Report
- Project-team name and number: Team SPEW (T3)
- Week number: 12 (week of March 27)
- Planned hours (week): 80 - Actual hours (week): 92 (Note: Hour totals includes week of Spring Break as well.)
- Did you meet with your advisor last week? If not, why not?:
- No, we did not meet with our advisor last week because we got everything we needed from him at the previous meeting (the week before last).
- Planned objectives for the week
- Continue work on the implementation of a rewind button that allows for the user to reverse the ODIN simulation.
- Continue to work on the implementation of the ability to change threshold for link activity heuristic in viewer.
- Modify the preprocessor as needed; according to what other changes are made to ODIN.
- Continue working with ODIN and GUI.
- Complete the Status Report for that week.
- Begin to prepare our Iteration 2 Demo.
- Implement circle size bytes sent + received in graphviewer.
- Implement filter links by threshold in graphviewer.
- Implement type in ip address and have it centered in graphviewer.
- Implement reset button - or buckets in graphviewer.
- Possibly look into reverse playback - low priority for the graphviewer.
- Update our class diagrams (to use the right kinds of arrows) and lightly document our late-breaking changes (no multiple layouts, we have no use for the prepro precomputing yet).
- Work on how to determine the way to treat the hostcatcher.
- Update ODIN to get search queries/results in the flexible way discussed by our customer (Dr. Cooper); by adding virtual methods to the Message superclass.
- Update ODIN to output search IDs.
- Generate an ONA file where nodes are activated and deactivated in the middle of the p2p network activity. Right now we've only been using files where all the nodes come online at the beginning and stay around till the end.
- Progress (or lack thereof) on meeting those objectives
- We continued working on the implementation of a rewind button (that would allow for the user to reverse the ODIN simulation). There is still a good amount of work to be done to get this functionality working in the ODIN simulation; we plan on having this done by the end of the term.
- We continued to work on the implementation of the ability to change threshold for link activity heuristic in viewer.
- We modified the preprocessor as needed; according to the changes we have made to ODIN thus far.
- We continued working with ODIN and GUI. We are satisfied with the GUI we have provided for ODIN and will halt further work on this aspect of the project; we may add additional functionality in the future.
- We have completed this week's Status Report; the one you are reading now, this one.
- We have already begun to prepare our Iteration 2 Demo, and we will have it completed before Wednesday of next week; the day of our Iteration 2 Demo.
- We implemented the circle size bytes sent + received functionality for our graphviewer.
- We also have implemented the filter links by threshold functionality for our graphviewer.
- We implemented the type in ip address and have it centered functionality for our graphviewer.
- We implemented the reset button - or buckets for our graphviewer.
- We have looked into the possibility of a reverse playback for the ODIN simulation, but this is still a low priority for the graphviewer.
- We have updated our class diagrams (to use the right kinds of arrows) and lightly document our late-breaking changes (no multiple layouts, we have no use for the prepro precomputing yet).
- We also have worked on how to determine the way to treat the hostcatcher for our ODIN project.
- We updated ODIN to get search queries/results in the flexible way discussed by our customer (Dr. Cooper); by adding virtual methods to the Message superclass.
- We updated ODIN to output search IDs.
- We have generated an ONA file where nodes are activated and deactivated in the middle of the p2p network activity. Right now we've only been using files where all the nodes come online at the beginning and stay around till the end.
- Problems that arose and how you intend to deal with them
- (Tangible / measurable) plans for next week
- Work on our Iteration 3 blacklog.
- Prepare different ways to user test our product.
- Get ready (that is, prepare) for our Iteration 2 Demo for next week; which will ocurr on Wednesday of next week.
- Implement any new features our customer (Dr. Cooper) requests of us.
- Complete Status Report 12 for Week 13; that is, for that week that it is due.
- Continue work on the implementation of a rewind button that allows for the user to reverse the ODIN simulation.
- Continue to work on the implementation of the ability to change threshold for link activity heuristic in viewer.
- Modify the preprocessor as needed; according to what other changes are made to ODIN.
Return to the home page of Team SPEW
Link to this Page
- SPEW Status Reports last edited on 26 April 2006 at 5:02 pm by c-24-99-45-114.hsd1.ga.comcast.net