15.11.2012 Views

icegov2012 proceedings

icegov2012 proceedings

icegov2012 proceedings

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

equirements. A direct communication between the programming<br />

and the test team was established and ICT was used for<br />

transparency and reproducibility, e.g. platforms like Bugzilla were<br />

used for bug tracking. For the testing this approach brought the<br />

project team in the comfortable situation where they concentrated<br />

all test resources on workflow tests for the administration<br />

software. The project did not concentrate on single functionality<br />

but looked at complete processes as workflows which were<br />

walked through in the same way as election commissions<br />

administrate their election. To identify bugs even before the<br />

workflow tests and therefore increase efficiency of the<br />

development process document tests were performed and every<br />

developer had to test her or his software parts. Executed test case<br />

results are divided into business process, usability after WAI and<br />

security test cases. All results of a test execution at a certain date<br />

are displayed by the amount of found or not found bugs (number<br />

of defects or none defects) and their attribute (business process,<br />

usability and security). The idea was to create a simple table<br />

where execution date, number of found defects or executable<br />

business process test cases are documented. According to the test<br />

strategy it was not always necessary to test a new release with all<br />

business process test cases. With every new release the test team<br />

analysed new functionality or changes and discussed which test<br />

cases are relevant.<br />

Evaluation of the project´s test strategy can be described as the<br />

following. Document tests have been implemented for assuring<br />

that the requirements have been translated into good system<br />

specification. Developers executed developer’s tests to check<br />

functionality, specialists performed workflow tests to verify all<br />

processes and the operation team tested the technical<br />

infrastructure.<br />

4. ELECTION<br />

230.479 students were eligible to vote at the 21 Austrian<br />

universities where the federation of students’ elections 2009 took<br />

place. A total 375 races had to be decided, consisting of 21<br />

university body elections and 354 study body elections. 2,411<br />

candidates campaigned for 1,633 mandates. The electronic voting<br />

ended technically successful on Friday, May 22nd 2009, at 6:00 h<br />

pm. Until then 2,161 students participated in the elections. [4]<br />

The project´s test approach turned out to be very efficient and<br />

effective, however, only focusing on the technical level. Due to a<br />

process error based misleading communication one ballot sheet<br />

included an incorrect name of a political party. Furthermore<br />

certain electronic ballot sheets did not include the short names of<br />

political parties at all. The problem was an outsourcing of tasks<br />

from the election commission to a technical operation team<br />

combined with special designed e-voting processes between all<br />

parties. After re-analysing the results from the electronic election<br />

a certain risk level must have caused the critical situation. The<br />

process and communication error was not discovered as there was<br />

a separation into technical and workflow testing, where the<br />

operation team tested their processes and simulated the activities<br />

of the election commission but they could not test integration into<br />

the election system. On the other side there was training for the<br />

election commission where they tested their activities and actions<br />

(workflows) but the operation of the e-voting system was only<br />

501<br />

simulated. There was a lack of communication in the workflows<br />

between the operation team and the election commission.<br />

As a result of these issues on December 13 2011 the Austrian<br />

Supreme Court decided that e-voting at the student union election<br />

did not fulfil all requirements of the law. They concluded that<br />

election commissions must be able to verify the correctness of the<br />

main steps of the voting phase and vote counting without the help<br />

of any expert. This includes not only the detection of possible<br />

manipulations but also the errorless realization. The decision<br />

focuses on the use of an e-voting system but for sure also effects<br />

the use of any electronic system for elections like administration<br />

software.<br />

5. CONCLUSION<br />

The paper has shown that the challenge of quality assurance of egovernment<br />

such as ICT supported elections lies not only in<br />

fulfilling various standards or technical correctness of software,<br />

but also in process management and IT-strategies at all<br />

stakeholders. When establishing new technologies also workflows<br />

change’s which have to be considered, evaluated and tested. The<br />

case study has shown the need of process oriented approaches<br />

when redesigning election administration by ICT support.<br />

Furthermore this demands an overall IT strategy where quality<br />

management is one part of it. Nevertheless, also due to the<br />

decision of the Austrian Supreme Court, the election commission<br />

should never lose control of process execution and process<br />

control. Furthermore the authors believe that to gain trust the<br />

challenge is to implement a QM process for the election system<br />

where everyone – especially election commission and eligible<br />

voters – has online access to the documented test cases and get the<br />

possibility to test the software by their own. Transparency in the<br />

QM process might lead to accuracy, correctness and to more trust.<br />

We would call this a QM-trust-box.<br />

6. REFERENCES<br />

[1] Federal Computing Centre, BRZ, e-government IT-strategy,<br />

http://www.brz.gv.at/Portal.Node/brz/public/content/unterne<br />

hmen/struktur/unternehmensbereiche/10052.html#E-<br />

Government, Feb. 2012.<br />

[2] Austrian Government (no date): Hochschülerinnen- und<br />

Hochschülerschaftsgesetz 1998 (HSG 1998) [Federation of<br />

Students law]. http://www.bmwf.gv.at/startseite/<br />

hochschulen/universitaeten/gesetze/studienrecht/hsg_1998/<br />

[3] Austrian Government (no date): Hochschülerinnen- und<br />

Hochschülerschaftswahlordnung 2005 (HSWO 2005)<br />

[Election Regulations]. http://www.bmwf.gv.at/startseite/<br />

hochschulen/universitaeten/gesetze/studienrecht/hswo_2005<br />

[4] Andreas Ehringfeld, Larissa Naber, Thomas Grechenig,<br />

Robert Krimmer, Markus Traxl, Gerald Fischer: Analysis of<br />

Recommendation Rec(2004)11 Based on the Experiences of<br />

Specific Attacks Against the First Legally Binding<br />

Implementation of E-Voting in Austria. Electronic Voting<br />

2010, EVOTE 2010, 4th International Conference, July 21st<br />

- 24th, 2010, Austria

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!