[305] in Tooltime
Scopus Status Report 10/25/96
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Tue Oct 29 09:59:48 1996
Date: Tue, 29 Oct 1996 22:01:22 +0100
To: tooltime@MIT.EDU
From: Steven Wade Neiterman <wade@MIT.EDU>
Scopus Implementation
Date: October 25,1996
Working On Milestone:
- Release 1.0 acceptance completed, transition to rollout continues.
- Major concerns are stability and timing of the rollout
Accomplishments:
- Completed database changes needed for 1.0b7, incl. Filemaker reload (10/6)
- Completed plan for technology transfer (10/7) and started to implement
- Completed Export/Import from test to production - 10/08, 10/10, 10/13
- Completed first test for 1.0b7 and evaluation of Data Probe (10/9)
- Installed New Macintosh client (10/10), resolved new line problem
- Refined installer programs for Macintosh and Windows (10/10)
- Completed account creation for new student accounts (10/11),
DCS (10/11) and Transmissions (10/18)
- Completed Scopus benchmarking (10/12) with 4,249 mit_logs records
- Completed initial pass to cleanup lookup tables, e.g. software (10/15)
- Completed acceptance test plan (10/15)
- Completed student introduction to Scopus and training (10/15)
- Completed staff and student acceptance testing (10/16)
- Completed release 1.0b7 (10/18)
- Presented Transmissions with a demo/training (10/23)
- Conducted demo of Scopus for IS personnel in E40, E19 (10/23)
Goals:
- Continue technology transfer implementation
- Continue building tasks, issues and problem resolution items for R2.0
- Complete Macintosh testing for stability and issue resolution
- Continue with production and test machine management -
cleanup, data export/import, automated warehouse feed, etc.
- Assess acceptance testing results
- Refine criteria for rollout and migration
- Review and adjust schedule as necessary according to rollout date
- Continue with problem resolution, Macintosh client, InformTEAM,
obtain latest documentation/software
Longer Term Goal:
- Gather enough information to build a scope statement and work breakdown
for release 2.0.
Issues:
- Decided that UNIX/VMS (e.g. VRC Helpline) data and consultants will be
included in release 1.0. Need further work on testing data migration
and usage.
- Long term maintenance of the test database machine (help-them.mit.edu)
needs further discussion and resolution within the various groups in
the service process.
- Rollout issues not only include timing and impact with the Help Desk,
but risk (application and machine stability) and usage (ability to
generate reports and/or print information) needs to be evaluated.
Notes:
- Losing some momentum, need to reach closure on release 1.0 and create a
new schedule of activities and plan for rollout.
- A large number of post release 1.0 tasks exist. This includes stability
(install SNS, refine production machine management, etc.). This list
needs to be identified and prioritized within a reasonable time.
