Abstract

workshop -

 

  82                  Computer Based Testing, the Ball State Experience

Yasemin Tunc, Ball State University

Dan Fortriede, Ball State University

 

During the summer of 1999, Ball State University renovated space to construct a 24 station computer-based testing room for a pilot study.  The idea for the testing lab came from faculty who teach large classes.  This pilot study, which started with four faculty in the fall semester, expanded to 14 faculty in the spring.  Based upon feedback from faculty and students, this project has become a great success.  CBT will be open to all faculty, starting fall '00.

 

In this presentation, we will focus on the following issues:

 

* The policies and procedures that govern the testing lab: Separate sets of guidelines were developed for faculty and students.  Both sets will be shared as well as any amendments that became necessary as usage increased.

* Lab set up and staffing issues.  We will share how the workstations were set up (technical details) in an attempt to curtail cheating.  We will also touch on student lab assistant roles and the supervision of such a high profile facility.

* The assessment tool used at Ball State: inQsit is a web-based testing and surveying tool developed at Ball State University which allows an instructor to develop, administer, and evaluate tests and surveys. The proctor functionality was enhanced to accommodate centralized proctoring services, which were handled by the lab assistants. The lab assistants would verify the instructor's requirements and student identification cards then issue authorization for the student to access the test module. (See the web site at www.bsu.edu/inqsit for more information about the inQsit product.)

* The home grown reservation and reporting program: This web-based tool allows students to reserve a station for their tests and produces utilization reports for management purposes.

 

Intended audience: Lab managers, any one involved in academic computing issues, or departmental computing coordinators would be a target audience for this presentation. In addition computing center directors or academic computing directors might be interested in how this project built a very postive bridge between our Computing Services and the academic departments (for once we made them happy).

Abstract List