Clicker system fails in its basic function

The greatest concern that has emerged is that the clicker system is too complex to be technically supported on campus.

Alex Doherty

Wednesday, February 27th, 2008


The adage, “If you play with fire, you're gonna get burned” seems to have recently struck the CPS Clicker system at Budig Hall. Last week, lecturer Nancy Holcroft was forced to assign 100 percent grades to every student taking a test in her Biology 100 class after the clicker system being used to administer the test failed to record the answers students were sending in. In this case it appears a problem arose with the lecturer's computer, though neither the company nor the University has identified a specific cause, eight school days after the incident.

Susan M. Zvacek, director of Instructional Development & Support, said that the clicker system is usually very reliable and her department had never before run into a problem such as last Monday’s. Although the system is mainly used for small quizzes, attendance or class interaction, IDS does not recommend using the system for “high-stakes testing situations.” It appears technology will continue to be integrated even more tightly into the class experience, but this raises a question: Is this integration necessarily positive or reliable?

eInstruction president Steve Kaye visited the campus Tuesday, meeting with professors and IT staff and finally assembling a company task force to investigate the problem. He assured that the University would be updated within 24 to 48 hours, though he offered no specific details as to the cause of the problem.

The greatest concern that has emerged is that the clicker system is too complex to be technically supported on campus, forcing the University to rely on a third-party company. It is positive that the company has taken steps to resolve these problems and communicated with University officials.

These good intentions still have not moved the University any closer to resolving the issue, and if professors are going to rely on this system to administer tests or other high-stakes usages, more high-level technical support needs to be available on campus.

Technology like the CPS clicker system provides some obvious benefits over traditional class interaction and test making methods, especially in large classes. It facilitates direct anonymous response to questions a professor might want to ask, and allows this information to be displayed instantly.

But convenience aside, the real question appears to be whether these platforms are ready for a test-taking environment, where time and grades are critical. Judging by the information available in researching the clicker system, it is not — at least in it’s current form.

Scantron surely has it’s share of issues as well, but the real issue is that as technology allows more advanced functions, it becomes more complex and therefore less reliable. Malfunctions with student or teacher hardware could cause a delay, forcing a reschedule or even a loss of all information, as happened last week.

Kaye said his company does thorough quality assurance testing on all its products and that a combination of unforeseen circumstances had converged to cause this problem. There are hundreds of different types of computers in use today, thousands of peripherals, countless configuration options and two major operating systems with five or more versions in use and all of this could cause problems. Basically, the clicker system has to be more complex in order to do what it does best and this is where unreliability comes from.

Currently then, the clicker system is thus inappropriate for testing situations. This is not to say that one day in the future this will not be possible. It will simply require more robust measures to address the complexity of the technology. According to Zaveck and Kaye, new training measures and software changes will be integrated to improve reliability.

The clicker system relies on complex technologies to offer what it does, meaning that in order for someone to fix it he or she will need a technical understanding of the system. Kaye said that eInstruction provides a comprehensive training program, but it mainly consists of how to setup a class’s roster or connect the equipment. As this circumstance has indicated, the clicker system is far more complex than this. When being used for testing, it is important it have a very high reliability rate. The system is complex and no one is available on campus that can provide high-level support.

If it’s the University’s goal to use the clickers for such important tasks, on-campus support and increased robustness in the clicker software would be required.

Alex Doherty for the Editorial Board

Discussion

All comments are moderated by Kansan.com staff. For our full user policy, click here.

28 February 2008
at 2:32 p.m.
Suggest removal
>> Last week, lecturer Nancy Holcroft was forced to assign 100 percent grades... Who made the decision to let the students have 100's on an exam? I'm no teacher, but I would've rather dropped the exam from the end-of-semester grade. >> problem arose with the lecturer's computer I've never had an instructor use the clickers for an exam. There are so many things that can go wrong outside of the clicker medium. The operating system, user error... technical glitches. A combination of events could have triggered numerous problems. >> The greatest concern that has emerged is that the clicker system is too complex to be technically supported on campus, forcing the University to rely on a third-party company. This is erroneous and preposterous. Are you suggesting that the university should hire 5-6 developers and then hire a support group and then hire sales and other staff just to implement it's own Clicker System? The university has a LOT of applications on computers campus-wide that are 3rd-party supported. How about an operating system? Should the university develop it's own operating system so we don't have to contact Microsoft when Windows XP system restore wipes out data? Maybe we can call it Windows KU or RockChalk XP. Interesting article. It reads to be somewhere between the lines of informative and argumentative without ever clearly reaching any accidental or logical conclusion.

29 February 2008
at 1:17 p.m.
Suggest removal
> > The greatest concern that has emerged is that the clicker system is too complex to be technically supported on campus, forcing the University to rely on a third-party company. >>> This is erroneous and preposterous. Are you suggesting that the university should hire 5-6 developers and then hire a support group and then hire sales and other staff just to implement it's own Clicker System? >>The university has a LOT of applications on computers campus-wide that are 3rd-party supported. Yes, in fact I'm reccomending exactly that. If you want to use clickers, the editorial board has come to the conclusion that the support offered from eInstruction is not sufficent for a piece of technology being used in testing situations. Does KU rely on Windows XP to administer tests? If so, yes we should have someone on hand who is an absolute expert with it. Unsurprisingly, there is an entire IT department full of people who are certified experts available at all hours of the day. This level of support is not available for clickers, therefore rendering them inappropriate for testing situations. As for your suggestion that KU have it's own operating system, sounds great to me. It would be fully a distro of Linux, call it whatever you want. Open source solutions would allow us full acess to the code and allow technicians to do the absolute highest level maintenance/debugging/support. >>without ever clearly reaching any accidental or logical conclusion. The conclusion is that we shouldn't be using third party hardware/software that we don't have access too and cannot support well enough to administer something as vital as tests. Any other questions? -Alex Doherty

3 March 2008
at 11:36 a.m.
Suggest removal
>>the editorial board has come to the conclusion that the support offered from eInstruction is not sufficent for a piece of technology being used in testing situations. In your article you state something along the lines of that IDS does not recommend using clickers in high-stakes testing situations. If you research further into this and visit the IDS website, you will find that IDS does not recommend using clickers for testing situations - reiterating your findings. Clickers did not fail in its "basic function". It's basic function is not for test-taking. So fine, lets say clickers failed in its basic function... which is recording data. Why did it fail? Out of the thousands of times this feature has been used on this campus, why did it fail this time and not any other time? You do not list any statistics or give other examples of situations where it has failed and reasons why. You only state that it is not recommended for testing and then you state that a 3rd party group is needed on campus for technical support. Fine. Lets say that we hired a 3rd party tech group on campus for clicker support. Would this situation still have happened? Yes. I am willing to bet it was the user's indirect fault for the clicker system failure. You're assuming that the complete fault was on the clicker system and it's lack of 3rd party assistance without even knowing WHY the problem happened in the first place. What if the problem was with the operating system or the user and not the clicker system? Would you still recommend hiring a clicker support group (even when KU does not recommend for testing) ? >>The conclusion is that we shouldn't be using third party hardware/software that we don't have access too and cannot support well enough to administer something as vital as tests. This is something that is already known... How is that a conclusion when -KU itself- does not recommend it for testing ? The instructor was well aware of the risks and in a moment of chaos, she "verbally" promised her students 100's on the exam.

Share your 2¢

Requires free registration.

Username:
Password: (Forgotten your password?)

Comment: