1. Classification Fields

The number and content of all classification items are under your control. The system allows each company to create their own unique classification sets. The ones shown in this document are merely examples of some sets used by SurveyTester clients.

There are three levels to a classification set.

  1. Classification Field Set
  2. Classification Fields
  3. Classification Field Values

Classification Field Set – The upper level settings that are based on the type of item being tested (survey versus website). In the above example, the classification Simple (used by project testers and external clients) and Complicated (used by the programmers to track every single item at a detailed level) contain very different classification fields.

 

Classification Fields – The numerous ways to organize the issues.

 

Classification Field Values – The actual values that will appear on the Issues form. In the above example, the possible values for Status are displayed (open, re-test, fixed…).

 

 

Order – specifying an order ranking for the classification items to group them by likelihood to be used or category of issue.

 

Color- specifying a color for the classification items to group them by importance (red, yellow, green) or category/topic.

 

The following screen shots show Field Values for several Classification Fields.

The Classification Fields can be displayed in a variety of formats.

Items can be filtered by user type (i.e. internal versus external).

 

For example, you may find it more appropriate to only show the Billable check box to internal testers and reviewers.

 

The number and type of classification fields are at your discretion. The following are some examples of commonly used classification sets.

 

1.1 Status

 

Status codes inform the users of the current status of an issue. These are typically created at the time of installation and are based on company standards, but new ones can be created as needed for specific projects or types of projects.

Status codes are very easy to add and modify.

 

To edit/change an existing status code, simply double-click it. You will then be able to change the text. Any changes made will apply to all projects that have that classification set specified on the Projects form.

 

 

1.2 Issue Type

 

Issue type codes are used to categorize the type of issue or problem found. The ones in this example are specific to surveys. Issue types allow you to review the frequency with which a specific type of problem occurs. You can then use the information to pinpoint issues in the scripting process.

Some sites prefer to classify their issue types in great detail; others prefer to limit issue types to three to five major categories. The choice is up to each site, but the more types you pre-define, the easier it is to later determine where problems occur in your survey process.

 

 

Internal codes can be screened from client testers. 

Creating separate codes for client-requested changes might allow you to seek additional payments for changes made to projects after the client had already signed off on them.

 

One client found that, on average, 28% of changes made to surveys in the test phase initiated by clients who saw the screen and then decided it did not look like they expected. One solution to the problem is to create a template library of sample screens with different grid layouts, logo placements, fonts, etc., which the client can select before coding begins. All subsequent changes are then billable.

 

 

Here are some additional samples of Classification Sets.

 Sample Issue Types:

     Change: Logic – Change to questionnaire to logic

            Example: Change skip at Q2 for “No” response to go to Q5 instead of Q6.

     Change: Screen Design – Change to questionnaire question screen design

            Example: Request Q4 list be displayed in 2 columns.

     Change: Text – Change to questionnaire to text

            Example: Q20 typo in question text.

     Correction: Logic – Logic programmed incorrectly based on questionnaire logic

            Examples:  Q13 should be multipunch.

                “None of these” should be exclusive.

               Skip Q29 if Q28 = “No one regularly uses my pool.”

     Correction: Screen Design – Question displayed on screen incorrectly

            Example: Add space between question text and respondent instruction.

     Correction: Text – Text displayed on screen incorrectly

            Example: 3rd response, “Vinyl Pool”, should be plural.

Very Detailed

1.3 Priority

 

Priority codes inform the programmers of the priority of an issue. These are typically created at the time of installation and are based on company standards, but new ones can be created as needed for specific projects or types of projects.