Visual Intercept Quick Reference

productsheader.gif (4756 bytes)

Visual Intercept 1.1.0.83 Quick Reference Card
Click here to download this QR Card in Word 7 format (self-extracting zip file, 43K).

Integration with Microsoft Visual SourceSafe

To enable direct integration of Visual Intercept with Microsoft Visual SourceSafe, you must specify the directory of the srcsafe.ini file in the Integration tab of the Preferences dialogue, beneath the Edit menu.

Use the Visual Intercept Wizard to import you Visual SourceSafe project tree structure into Visual Intercept.

Setting Filters

You can limit the incidents and projects initially Fetched from the Visual Intercept database upon launch by setting up Filters. Go to the Filters tab in the Preferences dialogue, beneath the Edit menu, and specify the projects you wish to be automatically fetched.

You can also greatly improve the performance of Visual Intercept by turning off the "Always fetch detail information" switch in the Defaults tab of the Preferences dialogue. This will mean detailed information on incidents, like Contacts and related Incidents, will only be fetched when you specifically ask for them. To optimize the speed of data retrieval, it is highly recommended that you change this setting as your Visual Intercept database gets large.

Essential Visual Intercept Commands

Command	Shortcut	Description

New	Ctrl+N	Create a new Visual Intercept document.
Delete	Ctrl+D	Remove a Visual Intercept document from the database.
Insert	Ctrl+I	Insert a Visual Intercept document into the shared database, for others to retrieve and modify.
Update	Ctrl+U	Send changes in an Intercept document to the shared database.
Refresh	Ctrl+R	Retrieve document information from the shared database, overwriting any changes that have not been Updated.
Print	Ctrl+P	Print a Visual Intercept document
Fetch	Browser toolbar	Retreive information from the common shared database to the individual user's computer.
Help		Provides context-sensitive help.

Incident Attributes

The four attributes - Status, Priority, Severity, and Category - summarize important characteristics of a particular incident. The Attribute values described below are the default values in Visual Intercept. You can edit these values in the Visual Intercept Administrator.

Parameter	Description
New	The Incident has just been reported and is not yet under investigation.
Open	The Incident is legitimate but is not currently being investigated.
Investigation	The Incident is under diagnosis to determine the specific problem.
Development	The problem has been diagnosed and the solution is proceeding.
Duplicate	There is an earlier occurrence of this Incident.
Not Reproducible	Unable to recreate the Incident.
Rejected	The Incident will not be investigated any further.
Suspended	Although the Incident has not yet been resolved, investigation has been halted temporarily.
Unit Test	The Incident solution is being tested within a limited environment.
System Test	The Incident solution is being tested within a system environment.
Q/A	The Incident is being tested for quality assurance.
Closed	The Incident has been resolved.
Reopen	The Incident has been reopened.
Custom	The Visual Intercept administrator can custom configure Status. Details are provided on page 158 in the Administration chapter of the User's Guide.

Parameter	Description
Urgent	The Incident needs to be dealt with immediately.
High	The Incident is not a crisis but should be looked at ASAP.
Medium	Work on Incident after urgent and high priorities.
Low	Can be worked on when time and resources allow.
Custom	The Visual Intercept administrator can custom configure Priority. Details are provided on page 158 in the Administration chapter of the User's Guide.

Parameter	Description
Annoying	The Incident is troublesome or disagreeable.
Crash	Causes the system to fail.
Confusion	The Incident is confusing to the user.
Unexpected	Results of an operation are not planned or expected.
Custom	The Visual Intercept administrator can custom configure Severity. Details are provided on page 158 in the Administration chapter of the User's Guide.

Parameter	Description
Automated Test	The Incident was found by an automated testing procedure.
Change Request	A change to an aspect of the project has been requested. Not a request for a new feature.
Code Error	The Incident is the result of a flaw in the code such as a typographical error.
Configuration	The Incident is related to hardware and software configuration issues.
Cosmetic	The Incident is related to display issues that are cosmetic.
Design Flaw	The Incident is related to a flaw in the system design.
Documentation	The manuals are either incorrect and/or do not describe the software adequately.
Education	The Incident is related to training and/or edification issues.
Integration	The Incident is related to integration issues within a larger environment.
Internal	The Incident is based on a proactive, what if, internal discussion.
New Feature	The Incident is a request for a new feature.
Requirement	The Incident is required for the project.
Source Inspection	The Incident was found during source code inspection.
Third Party	Someone outside the system reported the Incident.
Unknown	Unable to assign to a specific type.
Custom	The Visual Intercept administrator can custom configure Category. Details are provided on page 158 in the Administration chapter of the User's Guide.