Team Mu Architecture - Update 1

8/13/2019 Team Mu Architecture - Update 1

1/23

Turn off mark up when writing, cutting, and pasting initial document.

You guys should come to see me.

DATE?

The Electronic Voting System

Architecture Document

Team Mu

Paul Casilloichael !nyder

""#$%#$&"'


2/23

The Electronic (oting !ystem

Tom )orkman

Mentors

ehmet alcok

Doug !mith

Team u $ # $' ""#$%#$&"'


3/23


Revision List

Revision Number Date Description

D*A+T&." ""#&% -riginal Draft

&.$ "$#&% *e/ised Diagrams, E0ecuti/e !ummary

Team u ' # $' ""#$%#$&"'


4/23


Approvals Page

Team:

oncur: 111111111111111111111111111111111111111111

Michael Sny!er

oncur: 111111111111111111111111111111111111111111

Tom "or#man

oncur: 111111111111111111111111111111111111111111

Paul asillo

Mentor:

oncur: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

Mehmet Malco#

oncur: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

Doug Smith

%nstructor:

Approval: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

&ary "al#er

Team u 2 # $' ""#$%#$&"'


5/23


Table o' ontents

".& E0ecuti/e !ummary.........................................................................Page 3

$.& 4ntroduction and 5ackground...........................................................Page %

'.& Document -67ecti/es.......................................................................Page 8

2.& 4ntended Audience...........................................................................Page 3.& Architecture -/er/iew and !cope...................................................Page

3." +unctional 5lock !tructure........................................................Page

3.$ Tier !tructure.........................................................................Page "&3.' !oftware odule !tructure....................................................Page "$

3.2 9ardware !tructure..............................................................Page """2

3.3 :etwork !tructure................................................................Page """23.% Data !tructure.......................................................................Page "$"2

3.8 ;ser 4nterface !tructure and Con/entions...........................Page "$"3

3. Technology.........................................................................Page "2 "8

3. Phases...................................................................................Page "2"

3."& Preconditions and 4nputs....................................................Page "3"%.& !takeholders...............................................................................Page "3"

Table o' (igures

".& +unctional 5lock Diagram.............................................................Page

$.& Tier !tructure Diagram .................................................................Page ""

$'.& !oftware odule Diagram.......................................................Page "&"''2.& ;ser 4nterface Architecture Diagram.......................................Page "'"%

Team u 3 # $' ""#$%#$&"'


6/23


)*+ E,ecutive Summary

There is a federal mandate that 6y the $&& presidential election all 3& states must use

some form of electronic ta6ulation. The integrity of our country


7/23


-*+ %ntro!uction an! .ac#groun!

-*) Statement o' Problem

The current /oting system relies hea/ily on the userens. ercuri @ Camp, $&&2

Another issue which needs to 6e addressed is the positioning of names on the 6allot. Past

elections ha/e shown that the name on the first position in a contested primary 6allot hasan percentage point ad/antage. :ew /oting machines lack a fully secure /ote

ta6ulating and auditing system to ensure that there can 6e no tampering with the

electronic /otes. Current leading e=/oting suppliers work on the principle of securitythrough o6scurity. This pro/ides no way to /erify that software functions as the suppliers

claim. Bitcat, $&&2 Electronic /oting machines potentially make /oting fraud /erysimple. An election sa6oteur needs only to introduce a minor change in the master copyof the /oting software to 6e effecti/e. Difranco, Petro, !hear, (ladimiro/

-*- State o' Technology/ %n!ustry/ or Research

After the $&&& Presidential /oting ta6ulation issues, a ma7ority of our states 6egan the

transition to electronic /oting machines. 4n haste, the companies that 6egan producingthese machines were more concerned with marketing a finished product = with little

regard to the uality of the product. 4n hindsight, there are a num6er of flaws which

need to 6e addressed.

There is a federal mandate that 6y the $&& presidential election all 3& states must use

some form of electronic ta6ulation. The integrity of our countrying the /ote confusing, as it reuires the push of a 6utton e0ternal to the

screen. This is counterintuiti/e to a system that uses the touchscreentouch=screenas the

only means of input. Also, many users are only present to /ote for one particular districtor area, and statistically they choose the first candidate they see on the screen for the rest

Team u 8 # $' ""#$%#$&"'


8/23


of the districts. This skews the results 6y gi/ing a candidate at the top of the list an

ad/antage o/er the candidates 6elow him or her. The /oting ta6ulation system reuires a

physical memory card to 6e remo/ed from the system transported /ia a human and talliedat an e0ternal location. This method of data retrie/al opens the door for many errors.

)ith the card in the possession of a person, it is su67ect to damage, tampering, or e/en

misplacement.

-*1 2ypothesis

-ur team will de/elop a new, more understanda6le /oting en/ironment. The new system

will 6etter suit the needs of the /oters as well as the administrators in/ol/ed in the

election process. The team will de/elop a simple user interface designed to make the/oting e0perience faster and less stressful. )e will employ a data6ase accessi6le /ia the

internet which will assure /oters of the system


9/23


5*+ Architecture 3vervie6 an! Scope

The scope of this document includes

+unctional 5lock !tructure Tier !tructure

!oftware odule !tructure

9ardware !tructure

:etwork !tructure

Data !tructure

;ser 4nterface !tructure and Con/entions

Technology

Phases

Preconditions and 4nputs

5*) (unctional .loc# Structure

+igure ".& displays the 6asic structure of the system.

Team u # $' ""#$%#$&"'


10/23


Team u "& # $' ""#$%#$&"'

+igure ".& +unctional 5lock Diagram

This diagram misses its mark. !ee

me for help.


11/23


The administrator will initiali>e the system for use. The user will input their information

through the ;4. -nce the session ends, the data is logged to the PCe the system again for the ne0t /oter, or close the machine.

Team u "" # $' ""#$%#$&"'


12/23


The we6 interface will display information retrie/ed from the data6ase. 4t will only

display a user


13/23


The ;4 tier will in/ol/e the standard user interface, /isually impaired user interface,

and the administrati/e interface. raphics can 6e created with Ado6e Photoshop C! andthe whole interface can 6e displayed using Ga/a Applet or G!P.

The processing tier will in/ol/e all the Ga/a code that dri/es data retrie/al, o67ectmanagement, and session handling.

The data tier will in/ol/e ta6le creation, PF#!HF for 6atch processing, and uniueseuencing.

Team u "' # $' ""#$%#$&"'

+igure "$.& +unctional 5lockTier!tructure Diagram


14/23


The we6 tier will in/ol/e the we6 interface. Ga/a will 6e used for session management

and security. Any graphics can 6e created with Ado6e Photoshop C! and the whole

interface can 6e displayed using G!P.

5*0 So't6are Mo!ule Structure

The following modules will 6e implemented

!tandard ;4

(isually impaired ;4

Administrati/e ;4

5allot randomi>er

!ession handler

)e6 interface

+igure $'.& summari>es these modules and their relation.

Team u "2 # $' ""#$%#$&"'


15/23


The three ;4


16/23


6eing cast. A session handler will 6e adapted for the we6 interface as well, to gi/e

e0pirations to dormant logins and collect usage information.

The we6 interface will ha/e its own G!P to display the information. 4n the 6ackground,

data6ase mapping classes will collect the specific information.

5*1 2ar!6are Structure

The hardware in/ol/ed will include

eneric PC


17/23


The user /ote ta6le will contain each usered /iew will gather all the current /otes together per

candidate, per district using PF#!HF. This will dri/e the we6 interface


18/23


Team u " # $' ""#$%#$&"'

Standard GUIInstructions appear*andidates appearS$stem +aits for

selection

#isuall$ ImpairedGUI

Instructions are read*andidates are readS$stem +aits for

selection

+igure '2.& ;ser 4nterface Architecture

Diagram

Is usersatisfied

+ithdecision,

Is usersatisfied

+ithdecision,

Standard GUI-e&t instructions

appear-e&t candidates

appearS$stem +aits for

selection

#isuall$ ImpairedGUI

-e&t instructions areread

-e&t candidates are

readS$stem +aits forselection

Does user+ant to.uit,

"re allelectionschosen,

/es

/es

"dministratie GUI"dministrator initialies or

restarts session

"re allelectionschosen,

-o

/es

/es

S$stem%og ote!nd session

Is usersatisfied +ithall decisions,

Is usersatisfied +ithall decisions,

/es

/es

-o -o

-o-o

/es

-o


19/23


The standard user interface will display the candidates for a particular district or election.

The user will select their choice 6y pressing the appropriate name. A confirmation screenwill appear that allows the user to change their choice or continue. -nce they continue,

the ne0t set of candidates will appear and the process repeats. -nce all election choices

ha/e 6een e0hausted, a final confirmation screen will appear, displaying all the useration and hints

Team u " # $' ""#$%#$&"'


20/23


PF#!HF functionality

!ecurity

5*; Phases

5*;*) %nitiation

The initiation phase will in/ol/e planning and designing the software modules. )e will

design each user interface and design the schema for the data6ase as well.

5*;*- %mplementation

+irst, we will implement the user interfaces. )ithin the interface, we can implement the

random 6allot positioning system. )e can also integrate access for the /isually impaired

as it will ha/e to 6e tied closely to all of the dependent ;4 properties.

!econd, we will create the random num6er generator for /oter assignment and implement

the real=time data6ase. These will 6e closely tied together as the uniue /oter key willha/e to 6e the primary key to our dri/ing ta6le.

Third, we will implement the secure ta6ulation system and implement the supportwe6site for /oter /erification. This will tie 6ack to the data6ase and users will 6e a6le to

securely retrie/e their and only their /otes from the ta6les.

5*;*0 Delivery

-nce the system has 6een implemented, it will 6e installed on two PC


21/23


The stakeholders on this pro7ect include

Paul Casillo

ichael !nyder

Tom )orkman

ary )alker

ehmet alcok

Doug !mith

Penn !tate ;ni/ersity

Team u $" # $' ""#$%#$&"'


22/23


&lossary o' Terms

The following are a list of terms used throughout this document

;4 = raphical ;ser 4nterface

-racle = A 6rand name of data6ase that employs its own procedural

language

PF#!HF = -racle


23/23


.ibliography

Difranco, Petro, !hear, (ladimiro/ $&&2, -cto6er !mall (oting Elections Can !wing

Elections. Communications of the AC, 28, 2'=23

Gason Bitcat $&&2, -cto6er !ource A/aila6ility and E=(otingCommunications of the AC, 28, %3=%8

ercuri and Camp $&&2, -cto6er The Code of The ElectionsCommunications of the AC, 28, 3'=38

$&&2 4EEE !ymposium on"$ ay $&&2. $&&2, Gune &" !ecurity and Pri/acy, $&&2.Proceedings, $8= 2&
http://ieeexplore.ieee.org/xpl/RecentCon.jsp?punumber=9120http://ieeexplore.ieee.org/xpl/RecentCon.jsp?punumber=9120

Team Mu Architecture - Update 1

Documents

Transcript of Team Mu Architecture - Update 1