/ VoteCal Statewide Voter Registration System Project
Use Case: UC05.09.01 / Determine Organization that was issued an Affidavit

Use Case: UC05.09.01 / Determine Organization that was issued an Affidavit

Attribute / Details
System Requirements: / S.28.2 VoteCal must provide a method for an authorized SOS or county user to input a specific affidavit number and determine the person or organization to which the affidavit was issued.
Description: / The purpose of this use case is to allow a user to determine the person and/or organization to which the an affidavit was issued for redistribution.
Actors: / SOS User, County User
Trigger: / User initiates the use case whenever there is a need to determine who was issued a particular affidavit, e.g., during an investigation into possible fraudulent registration activity.
System: / VoteCal Application
Preconditions: /
  • All global preconditions apply.

Post conditions: /
  • All global post conditions apply.

Normal Flow: /
  1. User accesses the Organizations Management area of the application.
  2. User selects the “Look up organization by affidavit number” command.
  3. System presents the UI05.xxx Look up Affidavit Issuance Record screen.
  4. User enters the “Affidavit Number”.
  5. User selects the “Find Issued Organization” command to initiate the affidavit search.
  6. System queries for all the Affidavit Issuance Records with affidavit number ranges that contains the entered Affidavit Number.
  7. If any records were found, system presents each the returned Affidavit Issuance Record in a list with the following columnsinformation:
  • Organization Name
  • Issue Date
  • Range of Affidavits Issued and Quantity
  • Contact Name
  • “View Organization Details” command – user selects this to see details about the organization and contact
  1. [BMc1][cik2]User selects “View Details” on the Organization in the search results list they want to get details for.
  2. System presents the UI05.xxx Organization Details screen displaying detailed information about the organization. These include:
  • Organization Name
  • Address, City, State, Zip Code
  • Phone Number
  • Comments
  • Contact Name
  • Organization Status
  • Issue Date
  • Range of Affidavits Issued and Quantity
  1. If user needs to look up another affidavit, go back to Step 2.

Alternative Flows: / 6a No records with ranges containing the entered Affidavit Number were found
6a.1 System presents message stating that there is no record in the system of the specified affidavit being issued to an individual or organization.
6a.2 Go back to Step 2.
7a No details exist for the organization selected
7a.1 System presents message stating that there are no details about the organization in the system.
Exceptions: / N/A
Includes: / N/A
Frequency of Use: / TBD. Expected to occur more frequently during the registration period leading up to an election, and shortly after.
Annual counts of VRC Statement of Distribution forms received by SOS statistics: [BMc3]
2006 = 419;
2007 = 339;
2008 = 776;
2009 = 204;
Average of the past 4 years = 439
Business Rules: /
  • Affidavit numbers (the numeric portion of the Voter Registration Affidavit ID) are uniquely and sequentially numbered within each county code and alpha series language code.N/A

Assumptions: / Voter Registration Affidavits are uniquely and sequentially numbered.N/A[BMc4]
Notes and Issues: / N/A

Revision History

Date / Document
Version / Document Revision
Description / Revision Author
11/20/2009 / 0.1 / Initial Draft / Victor Vergara
12/10/2009 / 0.2 / Document Revisions / Victor Vergara
01/12/2010 / 1.0 / Release to Client / Victor Vergara
02/01/2010 / 1.1 / Incorporate Client Feedback / Victor Vergara
02/08/2010 / 1.2 / Submit to client for review. / Maureen Lyon
02/11/2010 / 1.3 / Incorporate Client Feedback / Victor Vergara
03/16/2010 / 1.4 / Incorporate Client Feedback from Discovery Sessions / Kimanh Nguyen
03/18/2010 / 1.5 / QA and Release to Client for for Review / Don Westfall
04/05/2010 / 1.6 / 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/1904/05/2010
Version: 1.65 / Page 1

[BMc1]Based on the business rules and flow in UC 05.08.01 it does not seem possible for there to be more than one range found. If this is the case, why are we presenting the results in a ‘list’ that will have only one record and asking the user to select the appropriate record to view details? Why not just display the details directly? Am I missing something?

KN: Accepted. There should only be one result, based on the functionality of 05.26.02.

[cik2]1I agree – there should only be one issuance record if searching for a specific affidavit number.

KN: Accepted.

[BMc3]See note for same data in UC05.08.01

KN: Accepted.

[BMc4]See note for same assumption in UC05.08.01

KN: Confirmed with program staff and moved to Business Rules.