U. S. ELECTION ASSISTANCE COMMISSION 

VOTING SYSTEM TESTING AND CERTIFICATION PROGRAM

1225 New York Avenue, NW, Suite 1100 

Washington, DC. 20005 

April 7, 2009 

Carolyn Coggins 

iBeta Quality Assurance 

3131 S Vaughn Way, Suite 650 

Aurora, CO 80014 

RE: Approval of ES&S Unity 3.2 Test Plan 

Dear Ms. Coggins, 

This letter is to inform you that version 2.0 of the test plan submitted by iBeta Quality Assurance 

for the testing of ES&S Unity 3.2 voting system has been reviewed and approved. Per section 

4.4.4.3 of the EAC’s Testing and Certification Program Manual (“Program Manual”) a test plan 

is approved based on the information submitted. Test plan approval indicates the following: 

• Approval simply signifies that the tests proposed, if performed properly, appear to be 

sufficient to fully test the system. A final determination of the sufficiency of the testing is 

a global evaluation based on the test plan, test cases, and test report reviews, as well as 

the EAC’s Quality Monitoring Process outlined in ch. 8 of the Program Manual. 

• Approval allows the test laboratory to begin test case development, testing, and test 

report submittal. 

• A test plan is approved based on information submitted. It is not known if relevant 

information was omitted that would affect the testing campaign. 

• The test plan is a living document and is expected to change and be updated during 

various phases of the testing life cycle. A final version that reflects all of the testing 

completed (TDP, S/W, Hardware, Software etc) should be submitted to the EAC at the 

completion of testing. If this final “as run” test plan does not reflect all the testing 

required, the EAC reserves the right to request further updates to the test plan and 

possibly additional testing. 

I also want to take this opportunity to remind you of the EAC’s requirements following approval 

of a test plan. Section 4.5 of the Program Manual requires VSTLs to report any changes to a 

voting system or an approved test plan directly to the EAC. Under this section, Manufacturers are 

required to enable VSTLs to report all test failures or anomalies directly to the EAC. In addition, 

for further guidance on this matter, please refer to Section 4.5.1 for information regarding the 

reporting requirements for changes to a system or test plan during testing, and Section 4.5.2 for 

information regarding the reporting requirements for anomalies or failures found during testing. 
Section 4.6 of the Program Manual lays out the various requirements for the submission and 

approval of a test report. Please be aware that all test reports will be posted on the EAC’s website 

in accordance with Federal law. Chapter 10 of the Program Manual outlines the responsibilities of 

the EAC, the VSTL, and the Manufacturer regarding the dissemination of this information. 

Finally, after final approval of the test report and the issuance of an Initial Decision of 

Certification by the Decision Authority (the EAC Executive Director) consistent with Section 4.6 

of the Program Manual there are additional steps that must be taken before final certification will 

be granted. These steps are outlined in Chapters 5 & 6 of the Program Manual and include items 

such as the execution of a trusted build, specific system identification tools being provided by the 

manufacturer to the EAC, and documentation that all other pre-certification requirements have 

been met. I strongly encourage you and the manufacturer to re-read these chapters in order to 

make the final steps of the process as efficient as possible. 

If you should have any questions regarding the approval of the test plan referenced above, or the 

rest of the EAC’s certification process please contact me. 

Brian J. Hancock 

Director, Testing and Certification 

cc: Election Systems and Software