Weekly Report on Project Status

Project Schedule

ACTIVITIES	hours per week									TOTAL
Meetings	7	10	8	10	5	7	7	12	7	73
Requirements	5	2	15	2	6					30
Documentation	5	7	18	10	13	5	15			73
Training	40	15	18	5	7					85
Preliminary Design / Prototyping	5	17	3	3	5					33
Detailed Design		5			10	5				20
Coding		15	2	10	30	15				72
Pre-Integration Testing		.5			8	10				18.5
Integration						5	30			35
Post-Integration Testing						25	30	35	10	100
Modification / Enhancements							10	15	5	30
MILESTONES	Project Teams	Project Plan		Requirements Document		Design Document		Final Demo	Project Notebook
	Apr. 3	Apr. 8		Apr. 22		May 6		May 20-22	May 29
DATE	April					May
	1 - 7	8 - 14	15 - 21	22 - 28	29 - 5	6 - 12	13 - 19	20 - 26	27 - 2
TOTALS	62	71.5	61	40	84	67	62	57	22	564.5

This week our team invested enough time to make up for our low-productive fifth week, which enabled us to return to our original schedule

• Design Document - Completed
• Coding(Financial Manager)
  • Basic Classes - Coding is complete
  • UI - Coding of the UI is mostly complete, and results compare adequately to storyboarded design
• Coding(Report Manager)
  • Basic Classes - Coding is complete
  • UI - Coding of Report Manager UI is mostly complete
• Coding (File I/O) - We've decided to implement a proxy server and communicate via sockets

none to report

• Next week we will begin Integration and Integration Testing of basic accounts, transactions and the report manager
• Next week we will finalize File I/O protocol and finish coding File I/O server
• In two weeks we will finish integration with the File I/O and begin full Integration Testing