[145] in Tooltime
Scopus Status Report 6/21/96
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Thu Jun 27 19:32:24 1996
Date: Thu, 27 Jun 1996 19:34:42 -0400
To: tooltime@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)
(this is from last week, in a few more hours,
there should be one for this week!)
Scopus Implementation
Date: June 21,1996
Working On Milestone:
- Beta phase continues with multiple releases, testing, and assessment
of work required to complete this phase.
- Release 1.0b3 testing to begin week of July 1.
- Initial beta phase completion goal (June 30) has slipped.
Now projected to be mid July for completion of a stable client of
base/core functionality.
Accomplishments:
- Released 1.0b2 for testing (6/18)
- Completed 1.0b2 feedback and assessment meeting - documented 50 items
- Began work on 1.0b3 tasks based on critical or "easy fix" items
- On-going tasks: writing system architecture document, writing
overview document, data model imported into Silverrun, started work on
win32 installer, 184 records from FileMaker were imported into Scopus
as test, ordering production machine.
Goals:
- Complete 1.0b3 release
- Complete full FileMaker/Scopus import of non-closed records
- Complete requisition for production machine
- Continue with on-going tasks (see above)
Issues:
- Outstanding Macintosh problems, waiting for Scopus reply
Notes:
- The Scopus consultant has left.
- Release 1.0b2 identified a number of critical items. From this point
forward, the only items to be worked on for the application need to
be driven from the task list. Discussion from testing sessions or the
team meetings will serve as the basis to add and prioritize items to the
list.
- A number of design issues have been tabled for a future release. These
items have been documented in either team meeting notes or the release
feedback meeting notes. In July, we need to revisit these issues.
One issue that may need an early assessment is the presentation of
"supported" products and the process to update this information, store,
and present a consistent view for both the Help Desk and the Community.
Some work has been done is this area, but the process is still
incomplete.
