Spring Quarter 1996 Project Sponsor: Gregory Abowd |
Brian Leslie (Manager) |
The recent advent of the Java programming language has the potential to revolutionize the way computing is done in the future, allowing the Web browser to replace the traditional GUI desktop and software to be written for cross-platform use, interfacing with the Web as a distributed file system. The Future Computing Environments (FCE) group here at Georgia Tech, as part of the CyberDesk project, is promoting the development of a set of personal productivity tools using the Java programming paradigm, to help encourage a break from the GUI desktop.
This project will build a financial manager that will make use of the possibilities of Java. As such, it will be platform independent, able to run from any machine capable of running the Java virtual machine. Also, it will allow remote access to account information from any web browser.
The financial manager will provide for the tracking of several different types of bank accounts, including checking, savings, and credit card accounts. A front-end Java applet will control the access to a user's accounts. Once logged in, the user will be able to select accounts to view, generate reports and graphs, or perform account maintenance (creating or deleting accounts, etc.). The opening of a specific account will spawn another Java applet to handle interaction within that account. Once within a specific account, a user will be able to add, delete, or edit transactions, generate reports and graphs, and perform other various tasks.
The project team is divided into four major "roles", which are divided among and shared by the five members. Here are descriptions of the four roles:
ACTIVITIES | hours per week | TOTAL | ||||||||
Meetings | 7 | 7 | 7 | 7 | 7 | 7 | 7 | 12 | 7 | 68 |
Requirements | 5 | 20 | 25 | |||||||
Documentation | 5 | 25 | 18 | 5 | 5 | 15 | 73 | |||
Training | 40 | 10 | 50 | |||||||
Preliminary Design / Prototyping |
5 | 20 | 25 | |||||||
Detailed Design | 5 | 15 | 5 | 25 | ||||||
Coding | 15 | 30 | 25 | 70 | ||||||
Pre-Integration Testing |
10 | 15 | 25 | |||||||
Integration | 5 | 30 | 35 | |||||||
Post-Integration Testing |
5 | 25 | 30 | 30 | 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 | 62 | 62 | 70 | 62 | 67 | 62 | 57 | 22 | 526 |
Modifications to this original project schedule will be placed on the Project Schedule page.
There are four formal documents required for this project. Detailed descriptions of the requirements for each of these documents can be found on the Project Milestones page. The deliverables are:
Due: 3 April 1996
The Project Plan (this document) is a brief introduction to the project team members and a preliminary schedule and breakdown of the project's activities.
Due: 22 April 1996
The Requirements Document is an "extended document that details all functional requirements of the delivered prototype. A section of this document also indicates nonfunctional requirements that will be used to test the system for acceptability and a storyboard that will be used to demonstrate how the system will look and be used."
Due: 6 May 1996
The Design Document is a "detailed description of how the system will be built, including, for example, any object-oriented analysis and design to show the system structure."
Due: 29 May 1996
The Final Project Notebook is a "final collection of all of the above information in a well-organized Web page." It will include all revisions of all of the documents and provide access to the system's source code.