Upload
alaina-small
View
222
Download
1
Tags:
Embed Size (px)
Citation preview
Beckie Curtis, Michigan DOT
Virtis/Opis Issue Process
Virtis/Opis Issue Process
• Current Bug Status• Support Center• Issue Definitions• Issue Action Plan• Technical Support Site
Current Bug Status
Support Center
• The V/O Technical Support Site has multiple links
• Issues with the program should be reported on the support center
• http://aashto.engrprograms.com/virtis/
• Login/password is virtis2/opis2
Support Center
Support Center
• When an issue is reported, it will be set to “UNKNOWN”
• The contractor will review the issue and classify
Issue Definitions
• Urgent Bug • A program issue that
prevents users from performing critical business functions
• The Task Force and Tag will confirm the status of the bug as “Urgent”
Issue Definitions
• Critical Bug • A program issue that provides
incorrect final results without giving a warning to the user
Issue Definitions
• High Priority Bug • A program issue that provides
incorrect final results or prevents portions of the program from functioning but the user is alerted to the error
Issue Definitions
• Low Priority Bug • A program issue that causes
minor inconvenience to business process but there is a known work around available
Issue Definitions
• Maintenance Item • A program issue that is not
handled appropriately (as determined by the Task Force and TAG) or does not follow the AASHTO code for a program function that was intended to be included in the program
• This item was not included in the original work plan, but should be resolved
Issue Definitions
• Support Item • A program issue that is
resolved by providing information to the user
Issue Definitions
• Enhancement Item • A program issue that would
require changing the capabilities of the program in order to add additional program function or to improve usability but is not part of the current expected capabilities
Issue Action Plan
• Urgent Bug • All users will be notified
through email when the bug is found
• An emergency fix will be designed
• All licensees will be notified through email that the patch is available
Issue Action Plan
• Critical Bug • All users will be notified
through email when the bug is found
• The fix will be included in the next release
Issue Action Plan
• High and Low Priority Bugs • The original submitter will be
notified that the issue was classified as a high or low priority bug
• He/she will be notified as to the release of the fix and be invited to serve on the TAG for testing the fix
Issue Action Plan
• Maintenance Item • The original submitter will be
notified of the classification• He/she will be notified as to
the release it will be included and be invited to serve on the TAG for testing
Issue Action Plan
• Support Item • The original submitter will be
notified of the classification and provided the information
Issue Action Plan
• Enhancement Item • The original submitter will be
notified of the classification • Once a price range is
identified (small, medium, large) the original submitter will be notified
Technical Support Site
Technical Support Site• Critical Bug Tab
• Urgent & Critical Bugs
• Technical Notes and workarounds
• Kept for one additional version after the fix is implemented
Technical Support Site
• Other improvements under consideration/in progress• General Bugs sorted by the
categories the TAG sorts enhancements
• Education Tab includes responses to common support requests
• Archive Tab to include bug fixes more than 1 version old
Questions?