Final Status Report

Project Schedule Comparison

ACTIVITIES	hours per week									Planned Total	Actual Total
Meetings	7	10	8	10	5	5	7	12	7	68	71
Requirements	5	2	15	2	6					25	30
Documentation	5	7	18	10	13	5	15	10	15	73	98
Training	40	15	18	5	7	9				50	94
Preliminary Design / Prototyping	5	17	3	3	5	6				25	39
Detailed Design		5			10	6				25	21
Coding		15	2	10	30	15	20			70	92
Pre-Integration Testing		.5			8	8				25	16.5
Integration						1	10	20		35	31
Post-Integration Testing							10	10	5	100	25
Modification / Enhancements						2				30	2
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
Planned Totals	62	62	62	70	62	67	62	57	22	526
Actual Totals	62	71.5	64	40	84	57	62	52	27		519.5

• Requirements
  • Clearly defined requirements in our Requirements Document.
    Comments: "Excellent Job!" (Dr. Abowd, Requirement Doc Grade)
• Design
  • Clearly defined, straight-forward design detailed in our Design Document.
    
• Coding
  • Enhanced User Interface completed
  • Transaction Manager completed
  • Account Manager completed for checking account
  • Report Manager completed with Balance and Budget reports
  • File I/O Client and Server completed for non-UNIX platform
• Integration
  • Transaction Manager successfully integrated with Financial Manager
  • Account Manager successfully integrated with Financial Manager
  • Report Manager successfully integrated with Financial Manager
• Testing
  • Minimal pre-integration testing completed

• Underestimation of Training
  In our Project Plan our group underestimated the amount of time required to adequately learn the JAVA programming language. This planning error resulted in insufficient time for complete integration and product testing.
• Only one type of Account was implemented
  Our group decided that instead of implementing additional account types, that we would demonstrate additional capabilities of the Instant Finance program by implementing the Report Manager. Therefore, the Savings Account and Credit Card Accounts were not implemented.
• File I/O integration
  Our File I/O Server will only work on operating systems which do not have User-level file restrictions. This problem was the result of using a vehicle platform for coding that was not close enough to the actual target platform, and not allowing enough time to adequately test the program on the target machine due to planned training miscalculations.
• List of Known Bugs

• Future Work on Instant Finance
  Here is what we offer the next group to work with Instant Finance
  • An excellent Requirements Document
  • A good, straight-forward Design Document
  • Straight-forward code that can be easily modified and/or reused. However, we would recommend replaceing the File I/O portion of our project with a Telnet host and client similar to that used by the Scooby2beDue Project.
  • Some ideas for future development