[100] in Tooltime
Scopus Implementation Meeting Notes 5/14/96
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Tue May 14 22:45:48 1996
Date: Tue, 14 May 96 22:51:26 EST
From: wade@MIT.EDU (Steven Wade Neiterman)
To: tooltime@MIT.EDU
Cc: pakulat@MIT.EDU, jwl@MIT.EDU, endriga@MIT.EDU, tarnett@MIT.EDU
Scopus Implementation Meeting May 14, 1996
Attending: Charbonneau, Dupuis, Fermann, Larrabee, Lee
Pakulat, Sousa, Wade
Agenda
1. Roundtable
2. Handout and discussion of functional specification
3. Planning, next steps and action items
1. Roundtable
- Ray working on SQL*Net and Scopus client differences
(Wade late night thoughts: Ray said he was missing
another dll, was it core7win.dll? I am interested to
know if we not only solve the Scopus install issues,
but can we install Scopus on a machine already
previously configured with SQL*Net without hindering
existing products. If this statement does not make
sense, don't worry - I can explain later my
experiences with PowerBuilder conflicts).
- Peter to work today on extended data dictionary. Also
is assigned rough sketch of a storybook to complement
the functional specification and could be used in
testing. Talked about alternatives to writing
paragraphs, including annotated process diagram or
scenario/solution models are also appropriate.
- Chad working on scope statement for business
implementation document deliverable. Noted that some
restrictions/constraints learned last week should get
posted in the document.
- Other team comments: It was noted that last week's
screen design sessions were frustrating. Talked about
a number of reasons why this may have been so.
- Wade noted that Scopus will certify SQL*Net 2.1 for
the Macintosh in the June/July timeframe. We risk
using Scopus for a month without transaction
encryption on the Macintosh client. The team agreed
that this was acceptable. Wade offered Scopus the
availability of MIT to beta test the new client.
- The team discussed models to distribute the Windows
and Macintosh binary without needing to have access to
the one CD supplied by Scopus - thus allowing a
consultant/tester/demo person access to the software
on demand. CSS fileshare and AFS tooltime locker were
options presented. FTP was an option, but it was
noted that net-dist.mit.edu would not be good as non
authorized people would attempt to download and run
the software.
- Wade - Need to locate SQL*Net for Solaris. ASD wants the CD
back and we could use it to install a version needed to
test Scopus Solaris client. Also, confirmed with Scopus that
Oracle 7.1.4 is what we want to load on the production
machine.
2. Functional Specification:
- First draft (40 pages) was handed out, including final
cut at screen design.
- Team homework:
1. Review functional specification for inaccuracies
2. Identify missing functions that need to be
designed and integrated into the release schedule.
- Some discussion on generating a page of reports that
the team would like to see as part of a release.
Other areas that may need to be addressed include
notification, escalation rules.
3. Planning, next steps and action items
- Next meeting:
- Wedensday May 15 11:30 - 1:00 pm 16-720
Purpose: Review page by page - comments on the functional
specification, generate one copy of comments.
- Other Meetings:
- Thursday May 16 9:00 - 10:00 am 11-124A -
Purpose: Review consolidated and enhanced
functional specification, determine if it is
complete.
- Friday May 17 9:30 - 10:15 16-720
Purpose: Review Scopus tools with Terry,
specifically DesignTEAM, possible Tcl examples. Be
prepared to "play" with these tools next week.
- Tuesday May 21 10:00 - 11:00 11-124A
Agenda: More planning, including thoughts on a
test plan. Initial thoughts - tooltime team
testing week of June 10. Help Desk testing starting
week of June 17.
- Calendar Review:
- Handout of calendar for next six weeks.
Also available on the Web
"http://web.mit.edu/tooltime/www/scopus_notebook.html
