Tentative 1996 Winter Quarter Project Schedule
Important Client Deadlines | ||
---|---|---|
Part to Turn in | Deadline | General Description |
Project Plan | January 12th, 1996 | o Team introduction o Project schedule o Explaination of activities o Brief project description |
Requirements Document | January 29th, 1996 | o List of functional activities o Storyboard |
Design Document | February 9th, 1996 | o Describe how the system is implemented |
Initial Prototype | February 23th, 1996 | o Cool looking Java calendar |
Final Project Notebook | March 3rd, 1996 | o Software ready to ship and sell |
Tentative 1996 Winter Quarter Project Schedule | ||||||||
---|---|---|---|---|---|---|---|---|
Activities | Jan 15 | Jan 22 | Jan 29 | Feb 5 | Feb 12 | Feb 19 | Feb 26 | Mar 4 |
Coding | xxxxx | |||||||
Component Test | xxxxx | |||||||
Planning | xxxxx | xxxxx | xxxxx | |||||
System Test | xxxxx | xxxxx | ||||||
Training | xxxxx |
Task | Fraction of the Time Given (8 Weeks) | Actual Time |
---|---|---|
Planning | 3/8 | 3 Week |
Coding | 1/8 | 1 Week |
Component Test | 1/8 | 1 Week |
System Test | 1/4 | 2 Week |
Training | 1/4 | 1 Week |
Training Breakdown | ||||
---|---|---|---|---|
Task | Responsible Agent | Required Man-Days | Deadline | Special Note |
Learning Java | Programmers | 20 | 1/22 | How to write applets |
Planning Breakdown | ||||
Task | Responsible Agent | Required Man-Days | Deadline | Special Note |
Requirement Gathering | Programmers | 8 | 1/24 | |
Create Goals | Manager | 4 | 1/26 | |
Requirements Document | Technical Writer | 6 | 1/27 | Due 1/29 |
Brainstorm | Architech Manager | 4 | 1/29 | |
Design Document | Technical Writer Architech | 26 | 2/6 | Due 2/9 |
Review of Design | Architech Programmer | 12 | 2/10 | |
Final Design | Technical Writer Architech | 6 | 2/12 | |
Coding Breakdown | ||||
Task | Responsible Agent | Required Man-Days | Deadline | Special Note |
Writing Modules | Programmers | 20 | 2/19 | Initial Prototype Due 2/23 |
Component Test Breakdown | ||||
Task | Responsible Agent | Required Man-Days | Deadline | Special Note |
Testing | Programmers | 4 | 2/19 | |
Debugging | Programmers | 6 | 2/21 | |
Retesting | Programmers | 4 | 2/24 | |
Revision | Programmers Architect | 6 | 2/26 | |
System Test Breakdown | ||||
Task | Responsible Agent | Required Man-Days | Deadline | Special Note |
Integrating | Programmers | 10 | 2/29 | |
Testing | Programmers | 2 | 3/1 | |
Debugging | Programmers | 12 | 3/4 | |
Retesting | Programmers | 8 | 3/6 | |
Revision | Programmers | 8 | 3/11 |
Yakko Wakko and Dot Profile (YWD Profile) project team is a subgroup of the Java as Desktop project. Our project is focused on building a Java calendar browser applet. The College of Computing currently uses two calendar programs: Now Up-to-Date and the X utility "plan". The Now Up-to-Date application runs on MacIntosh platform while the "plan" utility runs on Unix workstations. People with accounts in the College of Computing have the option to create a publicly readable calendar file. Our Java calendar applet must be able to read and display the information in the calendar file, allow updates to the calendar from Java, and be able to browse other people's calendar and schedule appointments.
There are several precursor systems that attempts to do the same tasks. This project team will study these other works to gain insight on the inner-working and pros and cons of the system. By studying the existing systems we will be able to create a new system that is an improvement from the existing ones. The precursor systems to be studied are: Netscape Calendar, DISCS, and previous Java Prototypes.
The Netscape Calendar was created by a College of Computing undergraduate. The application uses Hypertext Markup Language along with Perl to produce a brosable calendar on Netscape. DISCS is a continuing project as part of the Real-World Lab (CS 4310/1/2) that implements a calendar system for the Office of Information Technology (OIT). Several College of Computing graduates have done initial Java prototypes for an editable calendar.
Many of the previous systems that we are going to study are written in HTML. The limited functions in HTML places many constraints on what the system can provide. Building a calendar program with Java applets provides us with more functionality and options. With the more powerful Java applet, the new calendar will be a vast improvement from previous systems.
Top | Plan | Req Doc | Design Doc | Prototype | History | Revision |