Scooby2beDue Project Plan
|
Spring Quarter 1996 Document Author: Project Sponsors: GregoryAbowd |
Jon A. Preston (Manager) |
|
|
Spring Quarter 1996 Document Author: Project Sponsors: GregoryAbowd |
Jon A. Preston (Manager) |
The Scooby2beDue To-Do List will support far more than the most basic to-do list functionality of adding and removing reminders of things that the user may need to accomplish. It will also allow users to include the date that each item is due, and set a priority for each one. The list may then be sorted and diplayed based on priority (the default), due date or creation date. The applet will also support the concept of "groups", where list items may be separated into logical subsets or groups and then displayed sorted based on group. List items may be edited at any time to correct typos or to reflect changes in circumstances.
The data for the Scooby2beDue To-Do List will be stored in each user's home directory on the College of Computing filesystem in a file named ".todolist". Because the applet uses telnet to log into the WWW server based on the user ID and password given by the user, each user needs to have telnet access to the WWW server.
This project is one of the mini-projects being developed as part of the CyberDesk project.
| Dates | -4/1- | -4/8- | -4/15- | -4/22- | -4/29- | -5/6- | -5/13- | -5/20- | -5/27- | -TOTALS- |
| Meetings | 0 | 10 | 5 | 5 | 10 | 5 | 5 | 10 | 5 | 55 |
| Documentation | 2 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 5 | 77 |
| Design | 0 | 2 | 15 | 8 | 3 | 0 | 0 | 0 | 0 | 28 |
| Training | 28 | 30 | 15 | 0 | 0 | 0 | 0 | 0 | 0 | 73 |
| Coding | 0 | 15 | 10 | 35 | 35 | 20 | 10 | 0 | 0 | 125 |
| Debugging | 0 | 0 | 0 | 0 | 5 | 15 | 20 | 0 | 0 | 40 |
| Integration | 0 | 0 | 0 | 0 | 0 | 5 | 5 | 10 | 0 | 20 |
| System Testing | 0 | 0 | 0 | 0 | 0 | 0 | 12 | 12 | 6 | 30 |
| MILESTONES | Project Teams | Project Plan | Requirements Document | Design Document | Final Demo | Final Notebook | ||||
| TOTALS | 30 | 67 | 55 | 58 | 63 | 55 | 62 | 42 | 16 | 448 |
We will be having three types of group meetings:
1. Organizational - coordinated by the manager for the members to get updated on each
other's status
2. Status - coordinated by the manager and the sponsor to keep the sponsor
up to date on our progress
3. Demo prep - coordinated by the manager to get the group prepared for live
demonstrations of our project
Roles:
Architect (11 hrs.), Programmers (22 hrs.), Manager (11 hrs.), Writer (11 hrs.)
We will have be creating four documents which will be converted to HTML based on templates
provided by Professor Abowd
:
1. Project Plan
2. Requirments Document
3. Design Document
4. Final Notebook
These four are described in detail under the deliverables section.
Roles:
Architect (9 hrs.), Programmers (18), Manager (20 hrs.), Writer (30 hrs.)
The architect will be doing most of the design while coordinating with the manager and the programmers. The majority of the designing will take place during the fourth week. There will be little or no designing after the sixth week.
Roles:
Architect (18 hrs.), Programmers (8 hrs.), Manager (2 hrs.), Writer (0 hrs.)
We will be developing the prototype using the Java programming language. All members of the team will be engaged in this activity. The programmer and architect will spend the most time gathering tutorial materials and going through exercises to build up their experience. We will then have a group training session on Java for the benefit of the remaining project team members. The manager and the technical writer will also spend a few hours familiarizing theselves with HTML (I borrowed most of this description from the template because it was pretty much in line with our project)
Roles:
Architect (20 hrs.), Programmers (40 hrs.), Manager (5 hrs.), Writer (8 hrs.)
During weeks 3 through 8, we will be coding our program. The programmers will do most of the coding but the architect will also help out and serve as liason between them and the rest of the team to keep documentation up to speed with actual progress.
Roles:
Architect (45 hrs.), Programmers (80 hrs.), Manager (0 hrs.), Writer (0 hrs.)
Debugging will be an ongoing process, but the official stage will be a cooperative effort between all the members to find and solve problems with the program. The manager and writer will help perform system test while the architect and the programmers will perform system and unit test and cooperatively find solutions to the problems that are found.
Roles:
Architect (10 hrs.), Programmers (20 hrs.), Manager (5 hrs.), Writer (5 hrs.)
Integration and interface testing of seperately-written code. Does not include final system test.
Roles:
Architect (10 hrs.), Programmers (10 hrs.), Manager (0 hrs.), Writer (0 hrs.)
This is the post-integration stage during which we will perform system level tests and modifications. This will be the last stage unless we have extra time to make any final functional or asthetic improvements.
Roles:
Architect (10 hrs.), Programmers (10 hrs.), Manager (5 hrs.), Writer (5 hrs.)
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:
(This paragraph was taken from Team 10's Project plan)
The Project Plan which is this document provides descriptions of and a schedule for the different activities and deliverables that our group must complete this quarter.
The Requirments 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 will be used (and potentially presented to the class) to demonstrate how the system will look and be used. (taken from the Project Milestone Page)
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. (taken from the Project Milestone Page)
The Final Notebook will be our group's main web page will contain links to all relevant documents and information concering our project. In addition it will contain links to all the versions of these documents.