[139] in Tooltime
Scopus Implementation Meeting June 18, 1996
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Tue Jun 18 15:20:32 1996
Date: Tue, 18 Jun 1996 15:22:04 -0400
To: tooltime@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)
Scopus Implementation Meeting June 18, 1996
Attending: Charbonneau, Dupuis, Endriga, Lane, Lee,
Oh, Saylor, Sousa, Wade
Agenda
1. 1.0b2 Testing, Expectations and Process
2. High level Planning - Next Four to Six Weeks
3. Short Term Issues
4. Next Steps
1. 1.0b2 Testing, Expectations and Process
- Testing 1.0b2 is available at 9:00 am on Tuesday June 18
- Expectations and testing requirements were stated in the
previously released test plan (may be useful to revisit).
- High level expectations of testing:
- Last week we tested vital signs, this week we begin
evaluating the application for training needs, business
integration, exceptions (unplugging the network, test
record locking, ...), stress testing, etc.
- We are NOT testing a polished application, but how well it
performs as stated above.
- Given that there are Macintosh problems (updating housecall and
netinstall as child windows), testing will primarily be conducted
on Windows class machines. The Macintosh testing should be limited
to the main Help Screen. (The Macintosh problem is still an open
issue).
- Release notes are included at the end of this mail message and are
on the web http://web.mit.edu/tooltime/www/scopus_notebook.html
- Comments should be sent to tooltime-bugs@mit.edu. Lynne will
summarize into one document before the feedback meeting.
- Peter will distribute (and send a copy to tooltime@mit.edu) the
storybook he wrote. This will be used as one guideline to help
evaluate how the application performs against the core business.
- Peter will summarize the responses from the student stress test
(Tuesday June 18 5:00 pm) and present the findings to the group.
- There will be a feedback meeting (see below for details).
2. High level Planning - Next Four to Six Weeks
- Next six weeks:
week 1 - Test 1.0b2, feedback, prioritize tasks
week 2 - Release 1.0b3, feedback, determine deployment issues
and timetable to release, include training needs,
contingency planning, etc.
week n - Release 1.0b4 if needed, and more if needed
week n + 1 - Create list of outstanding tasks and prioritize,
assign resources and timeline.
This includes items such as incoming email handler,
outgoing email for escalation and notification,
web support, account setup simplification, automated
warehouse generation, design issues previously
tabled, generation of reports, updated documentation,
database timeout generation, release 2.0 tasks, etc.
week n + 2 Possible rollout target
week n + 3 - Conduct Post-Partum - conclude this phase, determine
next steps, understand learning's, celebrate.
NOTE: Future development needs to be tighter, e.g. items that
are to be worked on should be derived from a consensus
checklist.
3. Short Term Issues:
Talked about FileMaker issues. Peter worked on FileMaker migration.
He feels that based on the 184 test records, we can migrate the
10,000 records since February '96 to Scopus.
Some issues remain, it was difficult to map the department name into
a department number. He did not map a person into a MIT ID (which
would affect the hit count on records per-Scopus, should be an
issue).
4. Next Steps:
Next Meeting
Tuesday June 19, 1996
3:00 am
16-720 **
Agenda: Asses testing and prioritize tasks, determine needs around
training, deployment, release 1.0b3.
RELEASE NOTES
--------------------------------------------------------------------------
Scopus Help Desk Application
1.0b1
Base Application Release
June 11, 1996
--------------------------------------------------------------------------
Scopus Help Desk Application
Release Notes
1.0b2
June 17, 1996
- (Lynne) Changed the layout of the main Help Desk log screen to make the
vertical height slightly shorter.
- (Lynne) Removed the constraint to the pick list on the following fields:
Model, Operating System Version, Software Version
- (Lynne) Removed the MIT Address fields from the primary and secondary
contact information
- (Lynne) Updated the following pick lists to include, other, unknown and
N/A (hardware only) for lookup tables: Hardware, Operating System, Software
- (Lynne) Removed extraneous entries in the picks lists for:
Status, Method
- (Lynne) Added labels to the following fields:
Created on, Modified on, Closed on
- (Lynne) Changed labels on the following fields:
Created by, Modified by, Closed by
- (Terry) Added the column 'mit_pri_id' and 'mit_sec_id' to the 'mit_logs'
table. These correspond to the MIT ID numbers for the primary and secondary
information fields.
- (Terry) Added TCL logic on the Software entry field: If a user enters a
software title that is not in the lookup table, the 'Unsupported' flag will
be marked.
- (Terry) Added a new lookup table 'mit_lk_role' for the Roles entry field
- (Terry) Worked on the CLOSED TCL logic for the help desk screen
- If you close the main screen, and one of the child screens has a status
of OPEN, the save will abort, telling the user which of the child screens
had failed the test.
- If you close a child screen, the associated help desk log id is closed at
the same time.
- (Terry) The FIND button on the main screen will only select non-CLOSED
records in the database.
- (Terry) Worked on the CLOSE LOG button TCL logic for the help desk screen
- (Terry) Consultant can now enter lower case text in the primary and
secondary information fields to be used with the PROFILE FIND buttons. TCL
code will convert to uppercase before the SQL statement.
- (Terry) Added the '*' buttons, located to the right of each of the
PROFILE FIND buttons. When pressed, the associated primary or secondary
fields will be cleared.
- (Terry) Added the Category TCL logic: When a category of 'Netinstall' is
selected, the associated Netinstall button will become visible, while the
other buttons (Housecall and mainframe) will become dimmed. The same logic
holds true when selecting the 'Housecall' and 'Mainframe' buttons.
- (Terry, Lynne) Changed sort order for a find from the main log screen.
The records presented are now sorted by status in the order: urgent,
unseen, pending, waiting, taken, frozen. Closed and Cancel status will not
be found from this lookup.
- (Lynne, Terry) Call Category field cannot be changed if already saved as
netinstall, housecall or mainframe. (Code will be added next week to check
for existence of child record.)
- (Lynne) Added to the TCL for a save on netinstall, housecall and
mainframe to prevent the discard changes if close button is pressed
immediately after the save.
- (Terry) Added record row level record locking via programming. The
logs table is updated with a flag upon selecting a record.
- (Terry) For administrators, added a button (function) to unlock
locked records.
- (Terry) Added hits field to main help screen to identify the number
of outstanding records in the database for the primary customer that
are not closed.
- Mofified tab order on main help screen.
- Added a "log busting" button to display all available open logs
based on a weighting.
--------------------------------------------------------------------------
