






Team SPEW - Week 14 - Status Report
- Project-team name and number: Team SPEW (T3)
- Week number: 14 (week of April 10)
- Planned hours (week): 40 - Actual hours (week): 57
- 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
- Finish implementing the breaking and stepping feature for ODIN simulation; have this completely working and tested.
- Implement a setting for allowing any type of connection to be a request/result (not just 1000, 1001).
- Implement any GUI changes; to make the ODIN graphviewer look nice.
- Work on and finish our Iteration 3 Use Cases (Detailed).
- Testing and bug fixing, if necessary, for all components of our application and/or project.
- Write up good documentation for all components of our application and/or project.
- Focus on final presentation material.
- Complete Status Report 13 for Week 14; that is, complete the Status Report for that week that it is due.
- Begin to work on and finish our Final Vision Document.
- Begin to work on and finish our Final Conceptual Architecture.
- Begin to work on and finish our Final Detailed Design.
- Begin to work on and finish our Final Use Cases.
- Begin to work on and finish our Test Report.
- Begin to work on and finish our Final Presentation.
- Work on implementing the Executor Implementation feature.
- Work on implementing the Single Step Progression feature.
- Work on implementing the Pausing On Event feature.
- Work on implementing the Connection Abstraction feature.
- Begin to Generate Additional ODIN Test Cases.
- Start to write our User Manual for our ODIN application (and/or project).
- Correct ODIN Extensions.
- Begin our Usablilty Testing for our ODIN application (and/or project).
- Progress (or lack thereof) on meeting those objectives
- We have finished implementing the breaking and stepping feature for ODIN simulation; It is completely working and tested.
- We have implemented the setting for allowing any type of connection to be a request/result (not just 1000, 1001).
- We are still implementing GUI changes for our ODIN simulation; we will have these GUI changes implemented by the end of Iteration 3. These GUI changes are mainly for the purpose of having the ODIN graphviewer look nice.
- We have already worked on and finished our Iteration 3 Use Cases (Detailed).
- We have made good progress in testing and bug fixing the ODIN application; that is, testing and bug fixing for all components of our application and/or project.
- We are still in the process of writing up the documentation for all components of our application and/or project; we will have this done (and/or completed) by the end of Iteration 3.
- We are also in the process of working on our Final Presentation material.
- We completed Status Report 13 for Week 14; that is, we completed this Status Report.
- We have begun to work on our Final Vision Document; we will have this completed by this coming Monday.
- We have begun to work on our Final Conceptual Architecture; we will have this completed by this coming Monday.
- We have begun to work on our Final Detailed Design; we will have this completed by this coming Monday.
- We have begun to work on our Final Use Cases; we will have this completed by this coming Monday.
- We have begun to work on our Test Report; we will have this completed by this coming Friday (that is, next Friday).
- We have yet to begin working on our Final Presentation; we plan on working on it next week.
- We have implemented the Executor Implementation feature.
- We have implemented the Single Step Progression feature.
- We have implemented the Pausing On Event feature.
- We have implemented the Connection Abstraction feature.
- We have already begun to Generate Additional ODIN Test Cases. There is still some more ODIN Test Cases that need to be generated.
- We have not begun to write our User Manual for our ODIN application (and/or project). We plan on working on this in the coming week.
- We have corrected the ODIN Extensions.
- We have not begun our Usablilty Testing for our ODIN application (and/or project). We plan on working on this in the coming week.
- Problems that arose and how you intend to deal with them
- (Tangible / measurable) plans for next week
- Continue to enhance our implementation of the breaking and stepping feature for our ODIN simulation.
- Continue to enhance our implementation of the setting that allows any type of connection to be a request/result (not just 1000, 1001).
- Finish implementing our GUI changes for our ODIN application.
- Continue to perform testing and bug fixing, if necessary, for all components of our application and/or project.
- Finish writing our documentation for all components of our application and/or project.
- Complete our Final Presentation material.
- Prepare for our Final Presentation.
- Complete Status Report 14 for Week 15; that is, complete the Status Report for that week that it is due.
- Finish and turn in our Final Vision Document.
- Finish and turn in our Final Conceptual Architecture.
- Finish and turn in our Final Detailed Design.
- Finish and turn in our Final Use Cases.
- Finish and turn in our Test Report.
- Continue to enhance our implementation of the Executor Implementation feature.
- Continue to enhance our implementation of the Single Step Progression feature.
- Continue to enhance our implementation of the Pausing On Event feature.
- Continue to enhance our implementation of the Connection Abstraction feature.
- Generate remaining ODIN Test Cases.
- Finish writing our User Manual for our ODIN application (and/or project).
- Finish our Usablilty Testing for our ODIN application (and/or project).
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