[226] in Tooltime
Scopus Implementation Meeting Sep 04, 1996
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Thu Sep 5 21:34:41 1996
Date: Thu, 5 Sep 1996 21:35:50 +0100
To: tooltime@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)
Scopus Implementation Meeting September 04, 1996
Attending: Goguen, Pakulat, Rogone, Smyser, Sousa, Wade
Agenda:
1. Roundtable
2. Training Document
3. Coordination
4. Next Meeting
-----
NOTE: I realize that while I attribute areas of discussion to an
individual, some items/words listed are my "fill in the gap"
style of writing and may not be attributed to the person.
1. Roundtable
Wade:
- Tooltime team updated (9/4) on Macintosh issues. Scopus is
projecting a three week time frame to fix the bugs. We expect
there will be some patch (most likely to the Macintosh binary).
- There was some discussion (Ragone/Pakulat) regarding possible
machine configuration options in the Help Desk area if we had both
the Macintosh and Windows platforms operational. This discussion
was tabled until we have more information on the viability of the
Macintosh client.
- Database for the production machine is progressing (slowly).
We expected to limit the differences from the test environment
and production by using many of the same components.
This design became altered when the disks we ordered required
Solaris 2.5 and not 2.4 (which we ordered). This resulted in
switching Oracle database versions from 7.1.4 to 7.1.5 since
7.1.4 does not run on Solaris 2.5. Scopus confirmed (9/4) that
there are no known issues with switching to 7.1.5. The database
group is trying to procure SNS for Oracle 7.1.5. This may not
be available on day 1 of production.
- Migration planning will need to consider redeployment of a new
tnsnames.ora file with the production machine settings. We will
also need to confirm accounts are complete.
- Some discussion on items post release 1.0. Expected that there will
be an extended "production/service" phase, which is not part of
release 2.0. This includes support of a password/changing program,
better account creation/deletion, documentation on system install and
Scopus machine specifics, automation of the warehouse feed, etc.
Release 2.0 will need a scope statement and prioritization, which may
include release 1.0 feedback (approx. six weeks post release 1.0).
Action Items:
- Reload new Filemaker data for help desk logs and netinstall
(with Peter Lee 9/5)
- Complete database changes needed for release 1.0b5
- Follow up with Facilities Management and Database Services on
production machine preparation, including install of the test
database and migration of the Scopus install software.
Brett (via Wade):
- Submitted response to Scopus on InformTEAM issues (8/29). Waiting
for their response.
Action items:
- Follow up on InformTEAM
- Possible help with Summary search (see below for description)
Lynne:
- Made some modifications (changed behavior of exit button, screen
ergonomics) due in release 1.0b5.
- Will complete 1.0b5 modifications by Monday 9/9
- Working on training document, first draft complete
- Decided not to use separate field for log history search on the
main screen due to problems forcing data into uppercase. Brett's
history search will be available.
- Discussed using Brett's history search model for a summary search,
which would be case insensitive. Wade to discuss with Brett. The
down side is a loss of QBE searching. Decided to assess this post
release 1.0.
Action Items:
- Complete release 1.0 - including review of tabs with Rob, incorporate
Brett's Summary change. Produce a new motd.
- Produce a second draft of the training document
- Help prepare for 1.0b5 testing with addition of new accounts
- Lynne will complete the Programmer's Guide with the latest 1.0b5
changes and send back to Esther. It should then be complete and
ready for the Web.
Ragone:
- Will begin exploring Brio Query as a report/query tool. The purpose
is to gain some experience on generation reports, understanding
limitations and gaining enough information to help plan a
strategy to use a third party report tool.
- Peter will start with the requirements document gathered by Peter Lee.
Action Item:
- Continue exploring Brio Query, report progress to team
Smyser:
Action Items:
- Helping out with training document.
2. Training Document:
- Discussion of training document. Agreed initial purpose is to release
a document by Tuesday 9/10 for student testing. This document is
expected to produce hints and describe any know issues in addition to
"bullet" description items in the following categories:
- Logging in/out of the application
- Creating a New Log
- Searching
- Annotating an exiting log
- Appendix (description of buttons)
- The goal of this document is to provide helpful information to use
the application as well as provide a baseline to for the students
to give feedback during the testing phase as to the usefulness of
the document and areas of improvement.
- The team (with Esther's help) will assess the document prior to
release 1.0 and determine it's final format and content.
- Post Release 1.0 will include a more formal document, including
functions related to the activities of a consultant beyond just using
the application.
- The tooltime team will review the draft (Lynne and Rob working on this,
will send out be end of day Friday) on Monday and submit comments.
- Final comments will be discussed during the Tuesday 9/10 tooltime
meeting.
3. Coordination:
- The team agreed to meet in 16-720 for three hours each Wednesday
for the next four weeks, 1:30 - 4:00.
- The purpose of the meeting is to:
- Promote efficiency (having people in the same room, working on
either the same or related tasks).
- Enhance coordination efforts
- Generate greater team dynamics
4. Next Meeting
- Tuesday September 10, 1996
10:00 am
16-720
