[86] in ad-lib
Reporting Advance Bugs...
daemon@ATHENA.MIT.EDU (Grant Young )
Fri Mar 3 16:12:13 1995
To: ad-lib@MIT.EDU
Date: Fri, 3 Mar 95 16:08:52
From: gyoung@MIT.EDU (Grant Young )
Procedure for Reporting Bugs, Suggestions, Comments, and
Questions for the Advance System
1. The Geac Advance system is significantly more flexible and
malleable than the Geac 8000. In order to make sure the
migration to the new system is as effective as it can be we
encourage everyone to submit reports of apparent problems or any
questions or suggestions they may have through this procedure.
Even duplicate reports of problems may contain unique clues that
will help us solve the problem.
We expect to receive reports that can be solved with a little
explanation or training as well real problems with the system
that need to be addressed. The reporting procedure is meant to
be educational for users of the system as well identifying
problems that need resolution before Advance replaces the Geac
8000.
2. All Official Reports should be sent using the report form on
paper or via fax to the Systems Office, to the attention of Grant
Young. (E-mail or verbal reports will not be considered official
or formal and may or may not receive a response but will not be
entered as official reports or reported to Geac.)
Copies of the report form should be generally available, either
through a supply from the departments and implementation teams or
through the Staff Web for Training. The Systems Office will also
make copies available for xeroxing. Please make your own supply
so that we will not be spending our time distributing forms.
You can print a copy of the form from Athena:
athena%attach gyoung
athena%lpr -Phayden /mit/gyoung/Public/bugform.txt
(Replace the hayden with the printername of your choice.)
3. When making out reports, SCREEN PRINTS and/or RECORD NUMBERS
that help identify the particular problems and the procedure you
used before the problem occurred are extremely valuable. Attach
them to your report. Please attempt to recreate the problem
before reporting it. The more information you can provide the
easier it will be for us to verify the problem and identify the
answer.
4. When received by the Systems Office an initial assessment will
be made of the report's severity and whether it duplicates a
previous report or adds more information to a previous report.
If the report is new a problem number will be issued for the
report. In all cases an acknowledgement will be e-mailed to the
originator of the report with the problem's number (either the
new one or the original report's number.) The acknowledgement
may direct the originator's attention to a frequently asked
questions list or the bug report list for further information.
5. Once a report has been issued the report will be listed in the
bug report list which will be accessible both from the Staff Web
for Training and as a file in /mit/gyoung/Public subdirectory on
Athena with its current status and the expected action to solve
it.
6. Reports that need Geac's attention will be e-mailed to our
Project Manager. After his evaluation appropriate resources
within Geac will be consulted.
7. Problem resolutions may fall into several categories:
a. System setup problems may be solved right away upon
discovery and adjustment.
b. Incomplete data conversions may be fixable with Geac's
help right away.
c. Some data conversions and table setups may need to be
specified for the 2nd and final data migration (GMA) and
won't be visible until then.
d. Some bugs and problems may require more or less temporary
work-arounds or work flow adjustments. Other solutions may
be judged critical for going live with the new system.
e. Some enhancements are already scheduled by Geac for
future releases of Advance. MIT is also a co-development
partner for the new client/server version of Advance. Some
changes may be possible during this development process.
f. Some data cleanup is possible after the conversion for
data problems on the 8000.
g. Some bugs never die or get fixed until the system is
replaced.
8. Implementation teams will set their own priorities for bugs in
their area. The Barton Operations Group (BOG) will review and
set overall priorities.
