[281] in Tooltime
Scopus Status Report 10/04/96
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Mon Oct 7 13:54:49 1996
Date: Mon, 7 Oct 1996 13:55:42 +0100
To: tooltime@MIT.EDU
From: Steven Wade Neiterman <wade@MIT.EDU>
Scopus Implementation
Date: October 04,1996
Working On Milestone:
- Transition to rollout continues
- Assessment of release 1.0b7, training, and acceptance testing
are the major migration items on the rollout schedule.
Accomplishments:
- Refined production machine setup (9/23), ensure proper access/roles
and machine software/configuration and test machine cleanup (9/25)
- Completed first draft rollout schedule (9/24)
- Performed testing against production machine (9/25)
- Completed 1.0b6 (9/27), including some data issues (9/24)
- Began work on 1.0b7, Scopus consultant on site for 1.5 days (10/1)
- Tested release 1.0b6 (10/2)
- Completed version 5 training document (10/4)
Goals:
- Refine technology transfer schedule with Service Process resource
- Complete application changes needed for 1.0b7 and final 1.0 candidate
- Complete database changes needed for 1.0b7
- Continue with production and test machine management -
cleanup, data export/import, automated warehouse feed, etc.
- Complete training and acceptance testing for 10/15 delivery
- Review and adjust schedule as necessary according to rollout date
- Continue with problem resolution, Macintosh client, InformTEAM,
obtain latest documentation/software
Issues:
- Waiting for resolution on two items: Log id 23142 is related to
Macintosh log text losing new lines when displayed on Windows,
and Log id 23164 is related to changing the File -> Exit function to
execute our code to unlock an existing record.
Notes:
- The responsibility of the tooltime team is to obtain acceptance
testing of the new application and ensure a stable production
environment. The responsibility of the Help Desk staff is to
determine an appropriate rollout date. At times, the criteria to
reach both objectives tends to be subjective as definitions for
release "show stoppers", impact and acceptance become difficult to
define.
- 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.
