[244] in Tooltime
Scopus team meeting notes 9/11 - 1.0b5 review
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Thu Sep 12 11:13:19 1996
Date: Thu, 12 Sep 1996 11:14:23 +0100
To: tooltime@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)
Scopus Implementation Meeting September 11, 1996
Attending: Goguen, Rogone, Smyser, Sousa, Wade
MEETING OVERVIEW:
Meetings notes from the student 1.0b5 testing was not available at the
start of the meeting. The tooltime team made a best effort of assessment
by starting with comments from Jamie Morgan (sent to tooltime-bugs).
Comments and action items below.
REACTION (or wade's personal comments):
We would get better results and limit frustration if we modify our approach
to a large acceptance testing. A training session is necessary, even
though we attempted to write an application that was "self training". It
is obvious that we are not at that level in release 1.0. This should
addressed during the migration planning effort.
To be complete, we should evaluate other comments not available during this
meeting. For example, one comments is as follows "new record 0-0000 phone
number is misleading, since the database is set up for phone numbers
without dashes."
ACTION ITEMS:
It is estimated at least one full day of effort to make improvements. The
goal is to complete the items by end of day Friday 9/13. Test on Monday
and Tuesday next week (9/16-17) and make final changes. This would be
release 1.0b6.
Wade altered the database group to prepare for an export/import of the test
database to production sometime after 5:00 pm on Tuesday.
NOTE:
At this time, this is the LIST we are working from to make changes and base
an assessment of the next release. Items can be added to the list ONLY
during team meetings.
NEXT MEETINGS:
To assess status and resolve issues, the team will meet at 8:00 am Friday
9/13.
We should plan on a quick meeting on Monday and then the normal tooltime
meeting on Tuesday.
DETAIL OF ACTION ITEMS AND COMMENTS:
1. Log # and Status boxes to be too small.
Tooltime team comments: If this is related to height, there is no
change for release 1.0. Possible question for Scopus and evaluation
of their next release for changes.
2. The Secondary Information fields are a waste of screen space.
Added issue is the font size, greatly affects near-sighted people.
ACTION: Remove secondary information from the screen,
leaving the database untouched for revisit of this
function in release 2.0
Assigned: Lynne (1/2 hour effort)
ACTION: The main help screen will be rearranged (required with
the removal of the secondary info) to allow more white
space between fields, and a smaller window frame.
Assigned: Lynne - 3 hours.
ACTION: Larger font will be researched to determine solution.
Two options: 1. Test using the Scopus options settings
for fonts and screen real estate. 2. Evaluate machine
resolution, changing from 1024 to 800x600.
Assigned: Rob and Peter R. - deadline Thusday 9/12 for
research and next steps determination (Friday 9/13 meeting)
3. Can't do a lookup from data-entry mode.
Tooltime team comments: It's true, that's the design for now.
4. "op-update-rel: dbsqlexec failed" and "ORA-01401: inserted value too large
for column"
Tooltime team comments: Need to further identify which field is having
the problem.
Assigned: Wade to send mail to originator the the bug report.
5. Clicking in the "History Entries" box, then pressing [Tab] puts an
entry into the Summary box then *two error messages* appear.
Assigned: Lynne to research and report. Effort - 1/2 hour.
6. In the Housecalls section, clicking "Save" resulted in the error:
"op_get_field_update_info: key field mit_log_id may not be updated"
Assigned: Wade to send mail to originator for more information.
Estimated possible 1 hour to fix based on understanding of Tcl code.
7. Scopus repeated error messages often. That is, an
error dialog box would appear, I would dismiss it by clicking "okay", then
the exact same error box would pop up again. Clicking "okay" once more
dismissed it for good.
Assigned: Rob and Peter R. will investigate to determine sequence of
when this occurs. Report by end of day Thursday.
8. In the Mainframe Maintenance section: the MITVMA and MITVMC fields are
not totally visible. The last letter of each word is mostly cut off.
Assigned: Lynne Effort - 20 minutes
9. The % (wild card) symbols for blank fields are confusing and
unnecessary when doing a search.
Tooltime team comments: The % sign is used by scopus to determine
the field is used for searching. This may be a Scopus design
feature/limitation. Options were discussed, including a. training,
b. user types an asterick (another internal scopus feature) on each
field used for searching, c. user issues a clear primary.
Assigned: Lynne to evaluate mail from Terry Arnett on possible
options/solution. After information gathering, decision to be made
at Friday meeting.
10. Perhaps the Status field should default to Pending when creating a new
log.
Tooltime team comments: no change
11. "New" button should create an empty log. What good is 0-0000 in the
phone field? It just creates extra work for the consultant to clear this
dummy info. from the log.
Tooltime team comments: The intention is to overwrite these fields,
which are an indicator of a required value. There is some correlation
to a "quick" function, where storing this record requires something to
be filled in.
It's possible that this function was misused. If using the New button
to create a record, then deciding to issue a search, these fields would
need to be cleared out via the Clear primary button.
Options: a. change required fields, b. show default values as is,
c. clear the default values.
Decidided that there would be no change at this time and it would be
investigated as a training issue and evaluation of product use.
12. Department name is missing on data from warehouse (item added by wade).
Assigned: Wade to revise data feed from warehouse and reload data
Effort 45 minutes.
13. Locks may still be an issue (item added by wade)
There was a desciption during the feedback meeting regarding using
the View Hits button and causing an item to be locked. If there is
no workaround, this is identified as a training issue.
14. Mac model list is incomplete (item added by wade)
Assigned: Wade to evaluate reloading data, Effort: 30 - 45 minutes
15. Eudora to Scopus copy and paste (item/concern added by wade)
Assigned: Lynne will do a quick test to copy an eudora mail message
into Scopus and show that it works.
