desinging test sets for opscan

From: charlie strauss <cems_at_earthlink_dot_net>
Date: Fri Jul 27 2007 - 20:16:42 CDT

Hi, this is slightly off topic for OVC but I thought i'd ask here anyhow. Is
there any analysis of the best way to design stack of opscan paper ballots for Logic
and Accuracy testing. I have a progessive clerks office that wants to rethink things
and I want to help them.

What I'm thinking is of things like this. Rather than have equal numbers of
votes on the test pack for every candidate one has different numbers e.g. 2 ballots
for candidate A, 3 Ballots for candidate B, 4 ballots for candidate C, and one ballot
for none. This obviously gets at the problem of transpositional type errors in
the machine programming.

Is there other strategies one can use to persue other types of likely mechanical
or software errors?

One can use a non-minimal stack size but keeping it modestly small will help the
process go quickly. And addtionally one wants to avoid having too many (intentional)
tests to overvoted marks.

Thoughts or references welcome
_______________________________________________
OVC-discuss mailing list
OVC-discuss@listman.sonic.net
http://lists.sonic.net/mailman/listinfo/ovc-discuss
By sending email to the OVC-discuss list, you thereby agree to release the content of your posts to the Public Domain--with the exception of copyrighted material quoted according to fair use, including publicly archiving at http://gnosis.python-hosting.com/voting-project/
==================================================================
= The content of this message, with the exception of any external
= quotations under fair use, are released to the Public Domain
==================================================================
Received on Tue Jul 31 23:17:06 2007

This archive was generated by hypermail 2.1.8 : Tue Jul 31 2007 - 23:17:08 CDT