[334] in Tooltime
Scopus Implementation Meeting Nov 19, 1996
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Sun Dec 1 20:00:17 1996
Date: Sun, 1 Dec 1996 20:00:58 -0500
To: tooltime@MIT.EDU
From: Steven Wade Neiterman <wade@MIT.EDU>
Scopus Implementation Meeting November 19, 1996
(plus updates from week ending November 26, 1996)
Attending: Lee, Ragone, Rosato, Smyser, Sousa, Wade, Yanow
Main Objectives:
1. Roundtable/Action Items Update
2. Begin list of activities to be conducted during next three months
Next Meeting: December 3rd, 10:00 16-720
Agenda: Continue calendar of activities through January
Roundtable/Action Items update
-----
Meeting highlights:
1. Roundtable/Status/Action Items
-----
Wade:
ACCOMPLISHMENTS:
- Confirmed with Scopus that order has been placed (11/26)
with manufacturing for an IRIX client. MIT should expect to
receive early week 12/2.
- Confirmed with Scopus that order has been placed (11/27)
with manufacturing for ScopusWorks (development tool for NT,
to complement existing tool on Unix). MIT should expect to
receive early week 12/2.
- Procured latest version of Scopedia (Scopus documentation) on
CD (11/25) in addition to being informed that updated on-line
information via the Web is now available (11/19)
- Completed C program to resolve Filemaker log/history proper
placement of line feed character during load into Oracle.
(11/25)
- Met (11/19) with David Ho on an introduction to Scopus. David
will be joining the Scopus implementation team.
- Continued conversations with Scopus on number of issues (see
Progress section for more information). This included:
* Update on Scopus version 5.2. Macintosh client is cross-
compiled, thus uses same source code and should have a
better consistency with clients on other platforms.
* Altered to change in Sales Rep. for MIT, new person is Joe Walsh
IN PROGRESS:
- Complete database code for placement of Exit function in
release 1.0b8. 50% complete.
- Waiting to receive IRIX client and ScopusWorks
- Pursued possible demo of Quality Team with CCR Dennis Dallin, who
is based in North Carolina.
- Checking into WebTEAM release 2.0 (currently beta, looking for
release timeline), Verity search engine (for possible use with
solution sets due in release 5.2 - Summer).
- Pursuing issues with Scopus Macintosh working with SQL*Net 2.1.
Bug ID 13329. Scopus informed this is a high priority.
Discussions on 11/13, 11/19, 11/26, 11/27
- Should investigate purchase of Customer Care Maintenance, seems to
be low cost and worth the cost/benefit.
- Met (11/21) with member of database group on SNS installation,
waiting for resolution
ISSUES:
- Will need new Macintosh client for to work with SQL*Net 2.1 and
thus SNS (encryption). However, SNS (from Oracle) does not work
on 68000 platforms.
- Team roles and responsibilities need to be reviewed to allow for
more effective working.
ACTION ITEMS:
- Resolve why only user DBO can update lookup tables
- Complete Exit menu coding under File pull down menu
- Continue follow-up of In Progress items
- Send mail to Scopus on Macintosh issues
- Meet with database group on final database record size
- 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
- 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.
- Conduct export/import from test to production to resolve some
problems with adding users to production and evaluate release
1.0b8 and Filemaker load as it would look on cut-over.
- Further investigate performance as related to stress testing
- Investigate resources needed to produce release 2.0
- Write architecture document, update project notebook
- Work on rollout schedule
- Continue on test and machine cleanup and install documentation
- Index mit_lock_user on production (was done on test)
- Install SNS for Unix, needed for warehouse feed
COMMENTS: Most pressing issues for the team are:
1. Complete listing of activities to be conducted over next 3 months
2. Create WBS for tasks, including start and end dates, EFT
3. Publish schedule to complete rollout of release 1.0, with well
defined tasks and explicit estimates/dates
4. Continue technology transfer
5. Begin work on pre-planning activities for release 2.0
-----
Sousa:
- Continued minor changes needed for release 1.0b8, these include:
- Coding for Unix print button on the child windows
- Adding Function menu
- Minor bug fixes, e.g. View Hits is now always active
- Fixed double discard messages on children windows
- Facilitate ergonomic changes as needed, Exit menu, button changes,
researching further input on accelerator keys
- Determined that ergonomic issues prevent pulls down menu's from
showing on Unix, seems that placement of buttons overlaps the
menu's.
- Meeting decisions:
- Remove accelerator key for Edit menu since this conflicts
- Worked with Wade on account cleanup (11/18), migration from test
database to production is outstanding item.
- Programmer's Guide
- Continue documenting the tables and column names in relation
to the field names on the screens, documenting the lookup tables
and updating process, adding the tcl group numbers for easier
access, documenting how to log on and where to find the pieces to
do the work, i.e. tcl is under administration menu within design
team etc., what are permissions and how to grant and revoke them
within Scopus and oracle, etc.
- Macintosh stability testing with Larry Egan should be completed.
- Met with David Ho 11/22 on Scopus development introduction
ACTION ITEMS:
- Complete 1.0b8 items as listed above
- Continue working with Tom and David on technology transfer
- Help construct mail to Scopus on Macintosh issues, including
clipboard, dismiss button problems, overlapping result sets.
- Work with Tom and David on content for Programmer's Guild before
sending to Esther for formatting/style/readability. Wade -
need timeline on next draft and completion schedule.
-----
Ragone:
- Met (11/15) with Mary Weisse and Wade to review report generation.
Completed report showing log entries per department and giving
counts.
- Peter stated that he feels Brio Query can handle initial
reports needed by Help Desk. Further learning and exploration
is needed.
- Issues: Need to purchase copy of Brio Query for Help Desk
ACTION ITEMS:
- Continue exploring Brio Query, report progress to team
- Present demo of Brio Query to selected Help Desk staff
- Help with QA on training document and 1.0b8 testing
- Some investigation into Rever. required, regarding Mac
SQL*Net and Scopus distribution.
-----
Smyser:
- Currently working on bug list gathering and Filemaker form for
storage and reporting. Bug list currently has 60 items, not
all items appear to be open (e.g. some have been fixed) or
require a response. Rob will continue cleanup.
Working on making the data input presentable (e.g. readable).
Need to review entries first for completeness (some items input
have been resolved and need to be noted as such) before a team
priority setting can be accomplished.
- Rob completed (11/17) "diffs" on Filemaker software data
input and matching values found in Scopus. Peter Lee will
review list and make changes on the Filemaker side before
importing to Oracle. Rob will evaluate how to make changes
to the Software list within Oracle.
- Rob completed testing (11/18) of release 1.0b8. The team
reviewed his comments. One action item on accelerator keys
was noted for Sousa to investigate. Discussion on print
button appearing on result set on Unix, but not on other
platforms.
- Tested Scopus on NT (11/20)
ACTION ITEMS:
- Complete bug/task list gathering from tooltime-bugs meeting
- Helping out with training document, including feedback
- Make changes to software list within Scopus/Oracle.
- Continue with QA on the 1.0b8 changes, as needed
-----
Yanow:
- Esther will review Training Guide and add a template of
host platforms (e.g. Mac versus Windows differences -
including sorting). Waiting for holiday to be over and Rob to be
available.
- After Tom/Lynne review Programmer's Guide, Esther will help
facilitate final version.
- (Not discussed, other documents may include an installation
document - including system requirements, support plans).
ACTION ITEMS:
- Will talk to Rob on Training document updates. (Lynne has
also stated an interest in reviewing 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.
- Esther will send in comments on testing feedback.
-----
Rosato:
- Short term goals for week Dec. 2nd:
- Complete Programmer's Guide outline as part of effort to
determine appropriate contents
- Lynne/David/Tom to meet and conduct examples
- Programming assignment:
- 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". The other change
involves resetting the status when problems on child close occur.
- Tom is currently spending 1 (at times 2) days per week on Scopus.
Would like to move this to 2.5 days per week.
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.
- Write outline for programmer's guide and help move it towards
completion.
-----
Lee:
- Agreed to provide Filemaker data in two installments. First
installment is due on December 3rd. Second installment is
due just before cut-over. Purpose of first installment is to
test conversion routines and data load into Oracle. It is
hoped that cleaning up some "dirty" data now, will make it
easier when it is done just before the cut-over.
ACTION ITEMS:
- Work on bug/task list estimated with Rob
- Supply Filemaker data for production load, initial delivery
due on December 3rd.
2. Began list of activities to be conducted during next three months
The team began a list of activities to be completed over the next
three months. The next steps are to complete the list, generate
further detail as needed, assess the list for priority, resource
allocation and timeline. Finally, generate a WBS.
- Some of the migration concerns include:
Release 1.0 process
- Force password changes on existing accounts for production
- Process issues: adding/deactivation of accounts, checking R1.0
usage of warehouse lookup, pick list (software) updates, etc.
Post release 1.0
- Conduct postpartum
- Begin list of stability and operational issues for both the
test (upgrade operating system, database) and production
(monitor activity, disk usage, connections)
- Formally, obtain feedback from users
Development tool training
- Complete in-house training
- Complete programmer's document
Release 1.0 cut-over
- Finalize date for final 1.0 candidate, including testing
- Move (import/export) Oracle database from test to production
- Begin using 1.0 as statement of record
Reporting tools
- Availability of reporting (printing or via Brio Query) as needed
by netinstall, DCS and others. - have prepared reports
- Procure limited number of tools/Brio Query
- Conduct training
Database production issues
- Need better numbers of Filemaker data for migration, including
UNIX/VMS.
- Availability of some Help Desk staff to be available when data
is migrated from test to production to confirm the readiness of
the system.
- Database services informed of final load numbers
- Database services and Facilities Management notified of prod. date
- SNS loaded in test and production machine
Filemaker process issues
- Need to determine date for Filemaker change to 'read-only' mode
- Clean and prepare data, Dec. 3rd, next test
- Conduct final cut of Filemaker data (include Unix/VMS?)
- Import into Oracle and test
Notification
- Determine everyone who needs to be notified of the switch date
- Prepare notification (mail?, ???)
- Perform notification (date?)
Training
- Complete training document
- Help Desk full time staff available for QA
- Who will train and how will people be asked for training?
Service transition
- Review contingency planning - short and long term outage
- Complete service document
Release 2.0
- Produce bug/task list based on release 1.0 feedback
- Produce IT enhancements list
- Produce new customer list (e.g. local experts)
- produce options and cost estimates for release 2.0
- Complete work breakdown for release 2.0
- Complete charter, vision, team members, resource assignments,
review roles and responsibilities, obtain commitment
Development
- RCS all release 1.0 code
- Review team working environment, e.g. source control, etc.
- Install and learn ScopusWorks
