Use Case: UC10.07.01 / Verify Voter Identity Online
Use Case: UC10.07.01 / Verify Voter Identity Online
Attribute / Details /System Requirements: / S29.1 VoteCal must provide a public website for voters to verify the status of their voter registration and other election related information without compromising private information.
S29.2 For privacy purposes, the VoteCal public website must require an individual accessing the website to provide sufficient personal identification data to prevent others from accessing that voter's data and must not provide or confirm any private information.
Description: / The purpose of this use case is to allow a voter (Public User) to provide sufficient information to identify themselves before they can access any their semi-anonymous voter registration information and other election related information on the VoteCal Public Website.
Actors: / Public User
Trigger: / This use case is always initiated from other use cases. Voter initiates the use case whenever they need to access their semi-anonymous voter information from the VoteCal public website.
The parent use cases include:
UC10.01.01 Verify Voter Registration Online
System: / VoteCal Public Website
Preconditions: / N/A
Post conditions: / § Identity information from the Voter record is retrieved, and the user is effectively logged in for that session. Subsequent access to the VoteCal Public Website will use the Voter’s identity information, until the session ends.
Normal Flow: / 1. System redirects from a VoteCal Public Website page.
2. System presents the UI10.001 Verify Voter Identity: Step 1.
2.1. System presents a verification screen using a solution that prevents automated attacks by bots, such as generates CAPTCHA image and characters.
3. User enters information to verify their identity (* required):
§ Street Number*
§ ZIP code*
§ Date of Birth*
§ First Name*
§ Characters shown in the CAPTCHA image*
4. User selects “Submit”.
5. System verifies that the entered characters match the CAPTCHA characters and that all required information has been provided by the user.
6. System queries for Voter records that matches the information provided by the user.
7. Return to invoking use case with relevant data.
Alternative Flows: / 6a1 System did not find a Voter record for the specified criteria
6a1.1 System presents error message that no voter was found for the entered information.
6a1.2 If the number of attempts has not exceeded the threshold (e.g. 5 attempts), system presents error message. Go back to Step 3.
6a1.23 If the number of attempts has exceeded the threshold, system presents an appropriate error message, indicating that the user has exhausted their limits of tries.
6a1.34 The use case ends in failure, with the user unable to proceed with accessing voter information on the system. The user should be redirected to county contact information.
6a2 System found multiple Voter records for the specified criteria
6a2.1 System prompts user for additional information (Last Name) to uniquely distinguish them from the other returned voters.
6a2.2 System re-queries for matching Voter records, with the additional information provided by the user.
6a2.3 If a unique voter record was found, go to Step 6.
6a2.4 If the query returned no voter records or multiple voter records:
6a2.4.1 If the number of attempts has not exceeded the threshold (e.g. 5 attempts), system presents error message. Go back to Step 3.
6a2.4.2 If the number of attempts has exceeded the threshold, system presents an appropriate error message, indicating that the user has exhausted their limits of tries.
6a2.4.3 The use case ends in failure, with the user unable to proceed with accessing voter information on the system. The user should be redirected to county contact information.
6a3 System found a single Voter record matching a confidential voter
6a3.1 System presents error message that the user may not use online functionality.
6a3.2 The use case ends in failure, with the user unable to proceed with accessing voter information on the system. The user should be redirected to county contact information.
Exceptions: / N/AE1. If the user did not enter all required fields, the system will display an error message.
Includes: / N/A
Frequency of Use: / TBD. Expected to be considerably more frequent prior to an election.
Business Rules: / § The CAPTCHA entry must match the generated characters in order to proceed.
§ If user is unable to verify their identity, system must prevent displaying semi-anonymous voter information to the user on the VoteCal Public Website.
Assumptions: / N/A
Notes and Issues: / N/A
Revision History
Date / DocumentVersion / Document Revision
Description / Revision Author /
11/20/2009 / 0.1 / Initial Draft / Victor Vergara
12/10/2009 / 0.2 / Document Revisions / Victor Vergara
01/20/2010 / 0.3 / Document Revisions / Scott Hilkert
01/20/2010 / 1.0 / Minor edits and release to client. / Maureen Lyon
02/05/2010 / 1.1 / Incorporate Client Feedback / Victor Vergara
02/05/2010 / 1.2 / Submit to client for review / Maureen Lyon
02/11/2010 / 1.3 / Incorporate Client Feedback / Victor Vergara
02/11/2010 / 1.4 / Document Revisions / Victor Vergara
02/12/2010 / 1.5 / Accept Changes / Chad Hoffman
03/01/2010 / 1.6 / Incorporate feedback from Discovery Sessions / Victor Vergara
03/04/2010 / 1.7 / Minor edits and submit to client for review / Maureen Lyon
3/4/2010 / 1.8 / Incorporate Client Feedback / Chad Hoffman
03/05/2010 / 1.9 / Minor edits and submit to client for review. / Maureen Lyon
03/17/2010 / 1.10 / Incorporate Client Feedback from QA Checklist / Kimanh Nguyen
03/22/2010 / 1.11 / QA and Release to Client for Review / Don Westfall
04/01/2010 / 1.12 / Update with client feedback / Kimanh Nguyen
mm/dd/yyyy / 2.0 / Submit to Client for Review (Deliverable 2.3 Draft) / {Name}
mm/dd/yyyy / 2.1 / Incorporate Client Feedback / {Name}
mm/dd/yyyy / 2.2 / Submit to Client for Approval (Deliverable 2.3 Final) / {Name}
03/2204/10/2010
Version: 1.121 / Page 3