CPE309 Progress Reports
Week 9
Team Name: Ostrich Software
Manager: Tyler Charlesworth
Date Submitted: 6/2/2008
Team Accomplishments:
- Completed integrating code modules
- Made basis path testing assignments
- Updated Ant build to copy source .properties and .tpl files
- Created automated system tests
- Updated user manual
- Updated class diagram
- Updated javadocs
- Updated test matrix
Unfinished Tasks:
- Combining automated system tests
- Polish system tests
Schedule Revisions:
We are following the CPE309 general schedule. Stage 2 release scheduled for today, 6/2, details here. Our detailed calendar is available here.
Group Problems:
The amount of time that is being spent on this project is far more than was ever expected. Several items have been turned in late due to the large amount of effort required.
Late Status Reports:
Formal individual status reports are no longer being collected regularly. Verbal status reports were collected 6/1.
Week 8
Team Name: Ostrich Software
Manager: Tyler Charlesworth
Date Submitted: 5/26/2008
Team Accomplishments:
- Completed coding individual code modules
- Wrote unit tests
- Integrated 3 of 5 code modules
- Performed remaining 4 inspections
- Updated Ant build to update version number automatically
- Created procedure to follow for automating system tests
- Assigned automated system tests
Unfinished Tasks:
- Automating System Tests
- Integrating remaining features slated for stage 2
- Updating user manual
Schedule Revisions:
We are currently following the CPE309 general schedule. Stage 2 release scheduled for 6/3, details here. Our detailed calendar is available here.
Group Problems:
The amount of time that is being spent on this project is significantly more than was expected. The project manager loses points because of this.
Late Status Reports:
Formal individual status reports are no longer being collected regularly.
Week 7
Team Name: Ostrich Software
Manager: Tyler Charlesworth
Date Submitted: 5/19/2008
Team Accomplishments:
- Released Stage 1.1
- Added Release Notes for Stage 1.1
- Performed 1 of 5 Inspections
- Reverted conventions panels to remove hyperlinks from stage 1 in preparation for hyperlinks for stage 2
- Finished basic Ant build script
- Created XML script for Costello capable of starting BlueJ
- Removed extraneous files from our subversion repository
Unfinished Tasks:
- Automating System Tests
- Coding, Inspecting remaining features slated for stage 2
Schedule Revisions:
We are currently following the CPE309 general schedule. Stage 2 release scheduled for 6/3, details here. Our detailed calendar is available here.
Group Problems:
Only 1 and 1/2 code sections have been submitted for inspection. Our desire was to have all 5 done by today. Aaron and Michael are having technical problems with their code sections that we plan on addressing in a group meeting this evening.
Late Status Reports:
Formal individual status reports are no longer being collected regularly. Informal individual status updates were assigned and most everyone submitted a response in a timely manner. Still to be submitted: status update from Brian.
Week 6
Team Name: Ostrich Software
Manager: Tyler Charlesworth
Date Submitted: 5/12/2008
Team Accomplishments:
- Coding: Conventions name, description, and compliance version number now properly export and update without having to restart BlueJ
- Updated SRS to reflect multiple formatting options
- Set up subversion with somewhat more intuitive Branch and Trunk folders
- Updated Staged Delivery Plan for stage 2
- Analyzed and decided upon features for stage 2
Unfinished Tasks:
- Automating System Tests
- Coding all features slated for stage 2
Schedule Revisions:
We are currently following the CPE309 general schedule. Stage 2 release scheduled for 6/3, details here.
Group Problems:
We had some difficulty finding a satisfactory feature for Aaron to be responsible for. We have been having trouble working with BlueJ in Costello.
Late Status Reports:
Formal individual status reports are no longer being collected regularly. Informal individual status updates were assigned and everyone submitted a response in a timely manner.
Week 5
Team Name: Ostrich Software
Manager: Tyler Charlesworth
Date Submitted: 5/5/2008
Team Accomplishments:
- Released Stage 1
- Updated Javadocs
- Finished code inspections
- Integrated code
- Updated user manual
- Updated system tests
- Updated JUnit tests
- Updated changelog
- Updated SRS
Unfinished Tasks:
- Plan for Stage 2
- Determine features
- Determine timeline
Schedule Revisions:
We are currently following the CPE309 general schedule. Stage 2 release scheduled for 6/3, details here.
Group Problems:
We were unable to meet the stage 1 release deadline. We are going to be working with more focus towards stage 2 to prevent the deadline from sneaking up on us again.
Late Status Reports:
Formal individual status reports are no longer being collected regularly. Informal individual status updates were assigned and everyone submitted a response in a timely manner.
Week 4
Team Name: Ostrich Software
Manager: Tyler Charlesworth
Date Submitted: 4/28/2008
Team Accomplishments:
- Planned for release (schedule, delegating responsibilities)
- Finished individual code portions
- Integrated 50% of code
- Created an informal subversion comments policy
- Performed ad-hoc testing of Jalopy
- Added 50% of unit tests
- Updated the SRS for Stage 1
- Began regularly performing and recording daily build
Unfinished Tasks:
- Update user manual for Stage 1
- Finish system tests for Stage 1
- Finish unit tests for Stage 1
- Integrate 100% of code
Schedule Revisions:
We are currently following the CPE309 general schedule. Stage 1 release scheduled for 4/29, details here.
Group Problems:
There is a lot of stress and concern about meeting all of the requirements for the Stage 1 release on time.
Late Status Reports:
Formal individual status reports are no longer being collected regularly. Informal individual status updates were assigned and everyone submitted a response in a timely manner.
Week 3
Team Name: Ostrich Software
Manager: Tyler Charlesworth
Date Submitted: 4/21/2008
Team Accomplishments:
- Updated Jalopy to latest version, 1.5rc3
- Made analysis of Stage 1 Release features
- SRS change request to update to Stage 1 features was submitted
- Made test cases for Stage 0.1 features
- Daily build put in place
Unfinished Tasks:
- Remedy defects for Stage 1
- Update user manual for Stage 1
- Update SRS for Stage 1
- Test Jalopy features
Schedule Revisions:
We are currently following the CPE309 general schedule. Stage 1 release scheduled for 4/29, details here.
Group Problems:
No group interaction problems are apparent at this time. There is some concern about meeting all of the requirements for the Stage 1 release (updating all of the associated documents, etc.).
Late Status Reports:
Formal individual status reports are no longer being collected regularly. Informal individual status updates were requested with a minimal response. They may have to be assigned in the future.
Week 2
Team Name: Ostrich Software
Manager: Tyler Charlesworth
Date Submitted: 4/14/2008
Team Accomplishments:
- Resubmitted BlueJalopy Stage 0.1
- Decided on defects to be fixed for Stage 1 release
Unfinished Tasks:
- Remedy defects for Stage 1 release
- Update user manual for Stage 1
- Minimize stated system requirements in SRS
Schedule Revisions:
We are currently following the CPE309 general schedule. Stage 1 release scheduled for 4/29.
Group Problems:
No problems are apparent at this time.
Late Status Reports:
Formal individual status reports are no longer being collected regularly. Informal individual status updates may be requested by the project manager; they were not requested for this report.
Week 1
Team Name: Ostrich Software
Manager: Tyler Charlesworth
Date Submitted: 4/7/2008
Team Accomplishments:
- Completed BlueJalopy 0.1 for release
- Updated the wiki to reflect changes to the project
Unfinished Tasks:
- BlueJalopy Stage 0.1 was compiled with the wrong compatibility settings; it must be resubmitted for credit
- Create a project plan/schedule for the next 10 weeks
Schedule Revisions:
Our project schedule has not been developed yet.
Group Problems:
A testing plan needs to be enacted before the next release to deter problems like those that plagued this release.
Late Status Reports:
Formal individual status reports are no longer being collected regularly. Informal individual status updates may be requested by the project manager; they were not requested for this report.
CPE308 Progress Reports
Available here
