/ VoteCal Statewide Voter Registration System Project
Use Case: UC05.32.01 / Configure CountyPreferences

Use Case: UC05.32.01 / Configure CountyPreferences[IV&V1][IV&V2]

Attribute / Details
System Requirements: / S10.7 For high-confidence matches that exceed the established threshold for automatic application of the match, VoteCal must provide the capability for SOS administrators or authorized county users to configure so that the system, for that county, either:
  • Automatically applies such registration changes and sends electronic notice of the change to the county; or
  • Applies such a change, but when the change would cause an existing voter registration to be cancelled, does not actually cancel a voter’s registration until the change has been accepted by that voter’s county.[BMc3]

Description: / The purpose of this use case is for a userto configure county-specific preferences or settings for the VoteCal Application.
Actors: / County User, SOS User[BMc4]
Trigger: / There is need to add or modify an existing system-wide preference for the VoteCal application.
System: / VoteCal Application
Preconditions: /
  • All global preconditions apply.

Post conditions: /
  • The CountySettings table will be updated with the user’s modifications.
  • All global post conditions apply.

Normal Flow: /
  1. User accesses the Administration sectionof the system and selects “Configure CountySettings”.
  2. System presents UI05.xxx Configure County Settings.
  3. If an SOS User is logged on, then the user has to select which County to configure settings for. If a CountyUser is logged on, the system automatically determines which County to update based on the user’s county.
  4. The screen contains controls that allow the user to configure county-specific settings. Each setting will have the following fields:
  • Parameter Name – An identifier for the setting.
  • Parameter Description – A brief description of what the setting is used for.
  • Parameter Value – The value assigned to the setting.
Examples of county settings are:
  • APPLY_HIGH_CONFIDENCE_MATCH: Whether high confidence matches that exceed an established threshold should be applied automatically
  • APPLY_AUTOMATIC_VOTER_CANCELLATION: Whether an existing voter registration is actually cancelled without first being accepted by the voter’s county
  1. [BMc5]User configures the desired settings. User has the option of adding new settings[BMc6], or modifying existing ones.
  2. User saves changes.
  3. System validates that no business rules are violated and applies the changes.

Alternate Flows: / N/A
Exceptions: / N/A
Includes: / N/A
Business Rules: /
  • A CountyUser can only configure preferences for their county.

Frequency of Use: / TBD.
Assumptions: / N/A
Notes and Issues: / Additional examples of configurable items:
  • Death/Felon/Duplicate Work Items – county preference for EMS vs. VoteCal
  • Mailings – whether SOS will perform on behalf of county

Revision History

Date / Document
Version / Document Revision
Description / Revision Author
04/01/2010 / 0.1 / Initial Draft / Victor Vergara
04/01/2010 / 1.0 / QA and release to client. / Don Westfall
mm/dd/yyyy / 1.1 / Incorporate Client Feedback from QA Checklist / {Name}
mm/dd/yyyy / 1.2 / Submit to Client for Review / {Name}
mm/dd/yyyy / 2.1 / Incorporate Client Feedback / {Name}
mm/dd/yyyy / 3.0 / Submit to Client for Approval / {Name}
04/01/2010
Version: 1.0 / Page 1

[IV&V1]Paula: No comments on this use case.

[IV&V2]Art: No comments either.

[BMc3]There are a lot of other requirements and UCs that infer County-by-county settings. Can we note that as well.

[BMc4]The expectation is that we would actually control these setting, but configure them based on countypreference.

[BMc5]Perhaps these are bad examples given the Secretary’s policy that they will always be the same for all counties. (Always automatically apply high-confidence matches)

[BMc6]Really??? Can you provide some examples of new settings that could be added?