an internet voting system manager

An Internet Voting System Manager

Yonghua LiKansas State University

October 19, 2001

MSE Project - Phase I

Give my thanks to:

Dr. Maria Zamfir-Bleyberg Dr. William Hsu

Dr. David Gustafson

Presentation Overview

Project Overview Project Requirements Object ModelCost EstimationProject Plan Review

Project Overview

• Problems with current paper process? Integrity & Fairness

Validating ballot Pregnant ballot

Positioning candidate name in ballot

Project Overview (Cont’d)

• Issues in Designing Internet Voting System (IVS)

Authentication of voters Privacy Equity Security

Current Researches on IVS• Approaches to meeting the security,

secrecy, scalability, and convenience requirements of elections;

• Development of methods to reduce the risk of insider fraud;

• Development of reliable poll site and kiosk Internet voting systems that are not vulnerable to any single point of failure and cannot lose votes;

Current Researches on IVS (cont’d)• Development of new procedures for

continuous testing and certification of election systems;

• Protocols for preventing vote selling and reducing coercion;

• Electronic authentication for kiosk and remote voting system;

Current Researches on IVS (cont’d)• Human factors design for electronic

voting; • Effects of Internet voting on participation

in elections; • Implications of Internet voting for

political campaigns; • Experimentation, modeling, and

simulation of election systems.

Goals• To design a manager for an internet voting

system where voters can cast ballots through internet;

• To experiment, model, and simulate some approaches on internet election voting system;

Components• Emphasis on two components

IVS manager (IVSM) (sever side) Voter (client side)

• Integration with other components, e.g., database

IVSM Sketch

Query Processing

DatabaseConnection

Manager

Query Processing Server

ClientIVSM

Object Model of IVSM Component

AdministratorIVS Manage

Cache Manager

Ballot

Server

Query ProcessingConnection Manager

Connection

Object Model of Client Component

Client

Connection Ballot

Basic Functions of IVSM

• Administrator login setup• login id – administrator’s ID;• password – administrator’s password;

• Database setup• Candidate list database;• Voter database;

• Voting period setup• Start time;• Stop time;

Basic Functions of IVSM (Cont’d)

• Server initializing;• Ballot counting – doing statistics on the

voting ballots.

User Diagram of IVSM Component

login

IVSM

set up id & passwd

setup database

Setup voting period

initialize pool

run server

administrator

show voting result

Basic Functions of the Server

• Idling – waiting for visit;• Querying – getting ballots for the requested

election title from the database;• Caching – storing data and making them

available to querying;• Uploading – sending required blank ballots

to client.

User Diagram of Server

idle

query

cache

IVSM

upload

server

Basic Functions of Client

• Login• providing voter ID and password;• downloading a blank ballot;

• Voting – casting the ballot.

User Diagram of Client

client voter

login

vote

Cost Estimation – Function PointTable 6. Total Function Points for All the Types

Function Points Total Simple Average Complex Function Points

Value Amount Value Amount Value Amount Inputs 3 3 4 1 6 1 19 Outputs 4 2 5 1 7 2 27 Files 10 2 15 1 35 Inquiries 7 2 4 Interfaces 10 2 20 Total 115

Cost Estimation - COCOMO

Table 8. Summarize Formulas for Different programs

Programmer Development Time TDEV Productivity (Month)

Application Programs PM = 2.4*(KDSI) 1.05 TDEV = 2.5* (PM) 0.38 Utility Programs PM = 3.0*(KDSI) 1.12 TDEV = 2.5*(PM) 0.35 System Programs PM = 3.6*(KDSI) 1.20 TDEV = 2.5*(PM) 0.32

KDSI = 5.1 KLOC

PM = 2.4*(KDSI) 1.05 = 13 person-month

TDEV = 2.5 * (PM) 0.38 = 6.5 month

Project Plan• Phase 1: Requirements

August 16, 01 - October 15, 01Overview, Cost Estimation, Project Plan, SRS

• Phase 2: DesignOctober 16, 01 – November 14, 01Formal Requirements, SQA, Test Plan, Design, Formal

Technical Inspection• Phase 3: Implementation

November 15, 01 - December 14, 01Coding, Testing, Testing/Reliability Evaluation, Users

Manual, Project Evaluation

Gantt Chart

ID Task Name Duration1 Literatue review 15 days

2 Overview 13 days

3 Cost estimation 5 days

4 Project plan 5 days

5 Requirement specificaton 19 days

6 Phase I presentation 0 days

7 Design 6 days

8 Formal specification 13 days

9 SQA plan 5 days

10 Test plan 6 days

11 Formal inspection 8 days

12 Phase II presentaton 0 days

13 Source code 12 days

14 Testing & reliability evaluation 11 days

15 User manual 4 days

16 Project evaluation 4 days

17 Project documentation 16 days

18 Phase III presentation 0 days

10/15

11/14

12/14

W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12 W13 W14 W15 W16 W17 W18 W19 W20 W21 W223rd Quarter 4th Quarter

Summary

• Project Overview• Project Requirements• Object Model• Cost Estimation• Project Plan• URL:

http://www.cis.ksu.edu/~yli3568/mse/mse.html

?