Project Deliverables and Schedule

Goal: Design and implement a prototype, review prototype to create final design.

It should be noted that this project must be completed during the summer session of 1998. It should also be noted that the programmer must learn the JHV and HDF in this period. Therefore, it cannot expect to implement all the requirements described in the requirements document.

The first priority will be providing a spreadsheet that has most of the features of the current spreadsheet, none of the bugs, and a much better interface. Complex new features, such as modification of data may be too difficult to complete in this short time period.

The main activities are listed below, with specific deliverables, which will be scheduled as milestones.

1. Investigate ideas
1. Deliverable: requirements document and project plan
2. Design initial prototype
1. Deliverable: Detailed project plan, specifying what features will be supported
3. Implement prototype
1. Deliverable: working prototypes for review and discussion (see #5 below)
4. Document prototype as develops
1. Deliverable: clear documentation of user features and internal interfaces
2. Deliverable: documentation of unresolved implementation issues, external dependencies, and ideas for future work
5. Regular reviews of the prototype
1. Deliverable: Weekly review with Bob and/or Peter
2. Deliverable: Periodic review of major features with Mike and/or others, timing TBD

Goal: Revise prototype, create final code, integrate into source base, complete documentation and test for release.

At the beginning of Phase 2, we will determine the features to be included in the release, and work out a more detailed schedule for integration and release.

The strategy is to freeze development of the new spreadsheet on 1 August, and conduct a detailed status review. This review will determine what will be included in the September release.

1. Final design review
1. Deliverable: specific plan for release of the spreadsheet
2. Revise the design as needed, possibly removing or disabling incomplete features which will be omitted from the official release
1. Deliverable: code revisions which meet all critical issues required for the release
2. Deliverable: complete design document for the code that will be released, including the programming interfaces, especially the data access interface
3. Complete the code
1. Deliverable: revised code ready to be integrated into CVS tree
4. Integrate into common source base
1. Deliverable: new spreadsheet checked in and working with the common source tree
5. Revised JHV User's Guide, reflecting the new spreadsheet features
1. Deliverable: revised UG ready to publish
6. Test Plan for spreadsheet features
1. Deliverable: description of how to test spreadsheet, sample data files as needed