[128] in Tooltime
Scopus Implementation Meeting June 11, 1996
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Tue Jun 11 14:25:04 1996
Date: Tue, 11 Jun 1996 14:26:56 -0400
To: tooltime@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)
Scopus Implementation Meeting June 11, 1996
Attending: Dupuis, Endriga, Lane, Lee,
Oh, Pakulat, Sousa, Wade, Willis
Agenda
1. Testing Plan Review
2. Next steps
1. Testing Plan Review
- The team is responsible to obtain the software, install and
login prior to testing. Please ask for help as needed.
*** Building 16 lab room is also available for testing ***
- There may be some issues with the Mac testing. In addition to
the Mac client having a slow startup, it does not scroll
properly. This presents a problem on screens less than 17".
This client has gone through the least amount of testing to date.
- Team members are responsible to test the application on Wednesday,
June 12. Mail should be sent out at end of day on Tuesday or on
Wednesday morning with a confirmation.
- It is expected that testing may not take more than an hour.
The team should test the Main Help screen, Housecalls and
NetInstalls.
- The team will follow the test plan submitted earlier. Please
review the test plan for ground rules. See discuss transaction
113 from May 22, 1996. Also see the checklist of items to be
used during testing, discuss transaction 120 from June 3, 1996.
- The high level ground rules include:
- Evaluate for vital signs (or show stoppers). For example,
error messages, GPF's, functions written in the functional
specification not working.
- Send comments via the template described in the test plan
to tooltime-bugs@mit.edu. For example, include date and time
of problem encountered, user who conducted the test,
function and/or screen being used, what was entered
(clicked or attempted), what happened, what should
have happened, what type of machine was used.
- Items that are not "show stoppers", can be collected in
the tooltime-bugs mailing list. The team may identify
these non show-stoppers with the word "comment" in the
subject header.
- Things not show-stoppers, but, comments welcome include
screen ergonomics and real-estate changes, etc.
- Business rules (escalation) and notification have not been
developed. Reports and automated time triggers (e.g.
changing a record after a "thaw" date) have not been
developed.
2. Next Steps:
Next Meeting
June 13, 1996
9:00 am
11-1124A
Agenda:
- Meeting to asses comments sent to tooltime-bugs. The team will
prioritize the changes for development.
The development turnover time is slated to end the following day
(Friday, June 14) with a 1.0b2 release available the following Monday.
At the end of this meeting, the team will decide if we are on
shedule for a 1.0b2 release based on the feedback.
