[315] in Tooltime
Scopus Implementation Meeting Nov 05, 1996
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Fri Nov 8 09:11:31 1996
Date: Fri, 8 Nov 1996 09:13:20 +0100
To: tooltime@MIT.EDU
From: Steven Wade Neiterman <wade@MIT.EDU>
Scopus Implementation Meeting November 05, 1996
Attending: Goguen, Lee, Ragone, Sousa, Wade, Yanow
Main Objectives:
1. Macintosh Stability Update
2. Bug list and Tracking
3. Next Steps
4. Roundtable/Action Items Update
-----
The majority of the meeting was a review of the action items from the
previous meeting on October 22nd. The major items for review were the
Macintosh stability update and bug tracking update.
1. Macintosh Stability Update:
Peter Ragone handed out (also in tooltime-bugs) information on
Macintosh stability testing.
Three items have been identified to report to Scopus, none of which
are identified as showstoppers for deployment. The three items are:
- Dismiss button (appears only on SQL modify result window) causes
a crash. The window can be closed without using this button,
in addition, this function is not a primary function.
- There are result set overlapping windows (does not appear on other
platforms) when invoking the My Pending Logs function.
- Clipboard on the Macintosh does not work as it does on other
platforms, for now it is disabled for the Macintosh.
Problems encountered during the Acceptance testing in Building 16 on
PowerPC 6100 and 8500 Macintosh systems could not be reproduced when
testing in Building 11 or in E40. Lynne completed the acceptance test
scenario in Building 11 without any problems.
Wade also believes there may be a problem when leaving Scopus running
for long periods of time. In building 16, leaving Scopus running
overnight causes the Macintosh to freeze the next morning. This
needs further testing as it could be related to a specific Mac.
Telecommunications has had some Mac related problems, specifically
problems starting Scopus after a crash, where SQL*Net may have been
damaged. This needs further investigation. At this point, an
application crash may occur when using the Duplicate function, which
is broken on all platforms and is being evaluated.
It has been reported that the History Entries works differently on
the Macintosh. Lynne will check on possible resolution via checking
the tab sequence.
It was decided that our position is that there are no showstoppers
and the three bugs will be reported to Scopus after the conclusion
of Friday November 8, 1996. At this time, further testing with
Larry Egan and Lynne will have been accomplished and any problems
noted.
2. Bug list and Tracking:
- Rob created a Filemaker database. This took about an hour and is
now ready for data entry. Filemaker 3.0 is required for access.
- Original goal was to have a list available for November 5th. This
has been pushed back two weeks, until November 19th.
3. Next Steps:
- Next meeting agenda will include at least the following:
- feedback on bug list gathering
- technology transfer update
- Macintosh stability testing
- schedule refinement
- criteria for rollout
- status on release 1.0 application changes
- roundtable on all action items
4. Roundtable/Status/Action Items
-----
Wade:
ACCOMPLISHMENTS:
- Completed acceptance test report and submitted to Bill Hogue
- Progress made on release 2.0 timeline, vision and scope - about
15% complete
- Mail sent to database services with questions (see action items
below), also left voice mail - waiting for meeting time.
- Communicated with Scopus Customer Care Rep (Dennis Dallin) on
issues regarding obtaining software (ScopusWorks, WebTeam 2.0,
Irix client), new documentation (InformTEAM and Scopedia), and
Scopus release 5.0 and how it changes training needs. Waiting
for reply.
- Communicated with Mike Yin at Scopus on Macintosh Scopus client
and SQL*Net 2.1 issues. Waiting for reply.
- Test database disk replaced and database was restored
- Mail to be sent to tooltime for info on generation mailing list
archiving mail from scopus-users@scopus.com.
- Followed up on generating requisition for maintenance contract
for help-them machine and checked on maintenance contract for
production machine.
- Completed install of Windows NT 4.0 in lab room, ready to run
ScopusWorks when it arrives
ACTION ITEMS:
- Refine SLA with Facilities Management on production machine and
coordinate loading of Scopus software on the production machine.
- Confer with database services to install SNS on test machine after
production release. After initial testing on test, migrate SNS to
production machine.
- Automate warehouse feed
- Collate post release 1.0 "todo" list to ensure stability
- Work with database group on account transfer from test to prod.
- Waiting for arrival of ScopusWorks
- Need better counts of final Filemaker data for production import
- Follow up on Scopus bugs,
21009 - InformTEAM, Terry called this in to Melissa.
23591 - Macintosh SNS issues
- Wade to work on vision statement and direction for next 12 months,
including potential customers (e.g. Local Experts use as a backend
communication and searching). Need plan, pilot?, requirements.
- Need to resolve problem with adding accounts to production - getting
database constraint error
- Further investigate performance as stated above
- Investigate resources needed to produce release 2.0
- Check timeline for payment of next maintenance contract?
- Write architecture document
- Obtain latest documentation on InformTEAM and SupportTEAMplus
(a.k.a. Scopedia) 510 597 5612 Joel@scopus
- Work on rollout schedule
- Continue on test and machine cleanup and install documentation
- Index mit_lock_user on production (was done on test)
- Check on next release of Scopus, version 5.0
- Install SNS on database
- Look at Filemaker import improvements with Brett
FOR REFERENCE:
- Some of the migration concerns include:
- Force password changes on existing accounts for production
- Availability of reporting (printing or via Brio Query) as needed
by netinstall and others.
- Need better numbers of Filemaker data for migration, including
UNIX/VMS.
- Need to determine date for Filemaker change to 'read-only' mode
- Determine everyone who needs to be notified of the switch date
- Availability of some Help Desk staff to be available when data
is migrated from test to production to confirm the readiness of
the system.
- Training completed, Help Desk full time staff available for QA
- Limit "test" database account and usage to developers and testers
- Process issues: adding/deactivation of accounts, checking R1.0
usage of warehouse lookup, pick list (software) updates, etc.
-----
Rosen (via Wade) No change from previous meeting notes:
- Submitted response to Scopus on InformTEAM issues (8/29). Brett
sent a clarification of the Scopus response, but Scopus closed the
log.
- Possible future items may include looking at improved searching
and email/oracle publishing
ACTION ITEMS::
- Follow up on InformTEAM. Terry Arnett pointed out that we had
outdated documentation, Wade to follow up. Terry submitted a
call to Scopus, Wade and/or Brett to follow up on issue number.
-----
Sousa:
- Minor changes needed for release 1.0b8, these include:
- Fix Duplicate Button
- Fix double discard messages on children
- Mask touched and comment appropriate code
(it was decided at the meeting to remove the touched code from
Release 1.0 and to revisit the usage of this in further
releases. The original purpose of this field is to
determine if a log is not being resolved because it's
too difficult, yet it's looked at often.)
- Working with Tom on technology transfer issues, spent 5 hours
- Working with Peter R. on Macintosh stability testing
- Sent updated programmer's guide document to Esther
ACTION ITEMS:
- Complete 1.0b8 items as listed above
- Continue working with Tom on technology transfer
- Help construct mail to Scopus on Macintosh issues and work with
Larry Egan on testing.
- Lynne will complete the Programmer's Guide with the latest 1.0b7
changes and send back to Esther. It should then be complete and
ready for the Web.
-----
Ragone:
- Macintosh stability testing completed, notes recorded above
- Evaluate Brio Query against list of items for report generation.
Need to determine if we stay with Brio Query and what
documentation requirements are needed (e.g. field lookups).
Goal is to demo Brio Query to team.
ACTION ITEMS:
- Continue exploring Brio Query, report progress to team
- Help with QA on training document and 1.0b8 testing
-----
Smyser:
- Currently working on bug list gathering and Filemaker form for
storage and reporting.
- Completed software list update. Need to send wade updates to
Filemaker. Also, need to check other fields, e.g. hardware
ACTION ITEMS:
- Complete bug/task list gathering from tooltime-bugs meeting
- Helping out with training document, including feedback
- Continue with QA on the 1.0b8 changes
-----
Yanow:
- Interested in updating training guide, need feedback
ACTION ITEMS:
- Will talk to Rob on updates (Lynne will also review document)
(Do we still need information on a FAQ and TOC on web? - wade)
- Check with Lynne on completion of the programmers guide and
incorporation in the project notebook.
- Agreed to download Scopus from the web and test it in E19
-----
Rosato:
- Tom has been reading Tcl and reviewing the design environment
with Lynne
- Tom is upgrading his Intel machine, will move to a 32bit OS
- Tom will attempt to make a change to the main logs screen using
a "play" area on the test database. The change will consist of
filling in the logged in consultant username in the taken
field if the status is changed to "taken".
ACTION ITEMS:
- Continue learning to use the design tools and make the change
listed above
- Report an issues on technology transfer and measure progress
against technology transfer plan.
-----
Lee:
- Update on data probe: Cumbersome to use, preferred option is
to write sql statement in the Modify string of a result set.
Downside, need to know sql. Possible use of external query
tool as option.
- Decided to keep data probe available for release 1.0
ACTION ITEMS:
- Work on bug/task list (wade needs copy of FM 3.0 to view data),
estimated to be one full day for two people (Peter and Rob)
- Help with gathering better Filemaker load counts, will send
numbers for review at next tooltime team meeting
- Supply Filemaker data for production load, possible advance test.
