Voting System Presentation - PowerPoint PPT Presentation

1 / 16
About This Presentation
Title:

Voting System Presentation

Description:

1) A candidate has logged in and would like to upload a photo into the system. ... (and filed) as well as a digital database. The database is backed up in all ... – PowerPoint PPT presentation

Number of Views:41
Avg rating:3.0/5.0
Slides: 17
Provided by: csU65
Category:

less

Transcript and Presenter's Notes

Title: Voting System Presentation


1
Voting System Presentation
  • Beddes, Nathan
  • Hanlon, Sean
  • Wendt, Jeremy

2
User Interface the brain
User Interface
  • Essentially a front for a database
  • Patterns separate UI from DB
  • DB is distributed SQL with all necessary checks
    and redundancy (i.e. it was outsourced)

Site Map
owns
Option4
Option1
Option3
Option2
Etc.
Etc.
Etc.
Etc.
Site Map contains all possible links/paths, etc.
on the https//USVoters.org website However, as
will be seen soon only certain portions are
viewable to different users
3
Navigating System
Central Clock
Human
2
0
1
User Type (voter, admin, researcher)
User Interface
3
4
5
Rules
Notes This step assumed from now on
0) Human makes request of UI, UI prepares new
webpage to show. 1) UI checks if User Type is
allowed operations described on next level of
site map. 2) Some commands require query of
Central Clock time (i.e. voting only allowed Nov.
2) 3) Rules consulted by User Type 4) Boolean
response sent to UI 5) If operation approved and
requires further data, UI gets info and presents
to human
4
Logging in to the system
Security
Human
2
3
1
User Interface
User Factory
DB Proxy
4
Correct User Type
Notes User Factory creates singletons for
researcher, lowerAdmin, fullAdmin, flyweight for
candidate and voter If DBProxy returns userType
fullAdmin, User Factory checks the IP Address
with Security to assure human is at a safe
terminal
1) UI sends ID and password to User Factory 2)
User Factory checks password match with
Security 3) Upon successful password recognition,
User Factory gets the User Type and relevant
data from DB Proxy 4) User Factory creates the
correct User Type for human and returns it to UI
5
Register New Voter (Step 1)
Geographic data filler
Human
2
4
3
1
User Interface
DB Proxy
Registration
Notes The overall registration process is not a
real time system. It requires three steps
1) UI sends personal/legal data of human to
registration 2) Location data is obtained for
human (to be explained later) 3) Registration
adds data to its Unverified Voter List 4) The
corrected list is sent to DB Proxy
6
Geographic Data (aside)
2
State 1
District 1
District 2
District 3
1
.
State i-1
District 1
District 2
District 3
District 1
District 2
District 3
State i
State i1
District 1
District 2
District 3
.
State n
District 1
District 2
District 3
Notes While the which state decision is
essentially a no-op, the districts use a chain
of responsibility pattern to decide location of
voter
0) Remember that the user has supplied their
legal address and other info in previous step 1)
States use address to find correct state for
person 2) Districts for each state decide if
address is within their bounds 3) Updated
information sent back to Registration
7
Register New Voter (Step 2)
Printing and mailing signature form
full admin
3
4
2
1
User Interface
DB Proxy
Registration
Notes Backward-forward dashes for all steps
here describe properly executed signal
sent back to caller.
1) Full admin tells the UI that data is complete,
sufficient and accurate for human in Unverified
Voter List 2) UI calls appropriate function in
Registration 3) Registration prints a signature
form (mailed to human) 4) Registration moves
human to Partially Registered List and
communicates this to DB
8
Register New Voter (Step 3)
Flat Bed Scanner
human
Mr. Postman
Unpaid Intern
2
3
4
Registration
5
1
DB Proxy
1) Mr. Postman delivers signature form to
human 2) Human returns signed signature form to
Mr. Postman 3) Mr. Postman delivers signed form
to Unpaid Intern 4) Intern scans document/ sends
image to Registration 5) Registration moves human
to Voter list in DB
9
Upload Candidate Info
Candidate
Central Clock
3
1
4a
4c
4b
DB Proxy
User Interface
Decorator
Rules
2
  • 1) A candidate has logged in and would like to
    upload a photo into the system.
  • 2) The UI consults the Rules to see what window
    of time uploads are allowed in.
  • 3) The UI then consults the Central Clock to see
    if the current time is in that window.
  • 4) If allowed, the candidate can then upload
    media.
  • a) The media is stored in a decorator object
  • b) The decorator is sent to the DB proxy
  • c) The DB proxy wraps the data appropriately for
    the Database and enters it into the DB.

10
Voting
Central Clock
Joe/Jane Voter
1
4
State i
3
DB Proxy
District j
User Interface
Decorator (candidate info)
2
Rules
0) Voter has logged in and requests the
opportunity to vote 1) Exact time obtained 2)
Rules are consulted if time is within voting
window 3.1) Ballot created from State/District
objects 3.2) Candidate information displayed on
request 4.1) DB retrieves data for (3) where
necessary 4.2) Final ballot sent to DB from UI
(through State and District)
11
Updating Rules
Administrator
2
Security
1
User Interface
3
Central Clock
4
Rules
  • An administrator logs in.
  • The UI checks with Security to verify that the
    administrator is at a secure terminal.
  • The UI checks the Rules and the Central Clock to
    verify that no elections are running.
  • If there are no elections, the UI allows the
    administrator to change the Rules.

12
Provisional Ballots
Judge
2,3
1
DB Proxy
User Interface
  • 1) Two judges log in separately to resolve
    provisional ballots (not
  • necessarily same time).
  • 2) The UI gets a ballot that has been marked as
    questionable from
  • the Database, through the DB proxy.
  • 3) Each judge views ballots and validates or
    invalidates them. They
  • go back into the Database after being marked.
  • 4) Later both judges decisions are compared. If
    they match the
  • votes count/dont count, otherwise they get put
    aside for a committee
  • to look at closer.

13
Voting Results
Administrator
Central Clock
2
1
3
3
DB Proxy
User Interface
Rules
2
  • 1) An Administrator logs into the system to check
    voting results.
  • 2) The UI checks the Rules and Central Clock to
    determine if the race
  • is ongoing or finished.
  • 3) The UI then gets voting totals from the
    Database and reports the result as a
  • running result or a final result.

14
Experts View Data
Expert
2
1
3
DB Proxy
User Interface
  • 1) Expert logs on
  • 2) Allowable data retrieved from DB
  • 3) Expert writes paper (not a portion of our
    system)

15
Paper Receipts
I Voted sticker mailed (when appropriate)
Printer farm
DB Proxy
  • An invisible portion of our system (thus far) is
    that the DB Proxy creates two
  • copies of relevant data (such as votes). There
    is both a hard copy created
  • (and filed) as well as a digital database. The
    database is backed up in all
  • relevant ways also.

16
Patterns Used
Write a Comment
User Comments (0)
About PowerShow.com