/ VoteCal Statewide Voter Registration System Project
Use Case: UC05.25.01 / Enter Eligible Registrants Estimates for ROR

Use Case: UC05.25.01 / Enter Eligible Registrants Estimates for ROR

Attribute / Details /
System Requirements: / S24.6 VoteCal must provide the ability for authorized SOS administrators to input and store the estimated number of persons “eligible to register to vote” for each county as of a specified date for each ROR and keep the data permanently.
Description: / The purpose of this use case is for an SOS user to add or modify the estimated number of persons eligible to register to vote for each county.
Actors: / SOS User
Trigger: / SOS User completes manual calculation of the estimates for the number of persons eligible to register to vote for a county, as of a specified date for each ROR.
System: / VoteCal Application
Preconditions: / §  Calculation of the number of eligible registrants is complete for each county.
§  All global preconditions apply.
Post conditions: / §  ROR Eligible Registrants Estimates records will be added or updated, and associated to the appropriate ROR record.
§  All global post conditions apply.
Normal Flow: / 1.  User accesses the Survey Management section of the application.
2.  System presents UI09.xxx Survey Management screen.
3.  User selects the “ROR Estimates” command.
4.  System presents UI09.xxx ROR Eligible Registrants Estimates screen.
4.1.  System retrieves all ROR records and presents them to the user.
5.  User selects the ROR that the estimates will apply to.
6.  System presents UI09.xxx ROR Eligible Registrants Estimates Detail screen.
6.1.  System retrieves selected ROR record, and presents details including:
§  ROR Date – the date of the ROR
§  Comments – more detailed information about the ROR
6.2.  System presents in tabular form the ROR estimates for all counties. The columns are:
§  County Name – read-only
§  Estimate – The estimated number of persons eligible to register to vote for the county. If an ROR Eligible Registrants Estimate record exists for the specific county and ROR, then this will be pre-populated with the current value.
7.  User modifies the Estimate fields in the table as the data for counties become available.
8.  User saves changes.
9.  System validates business rules, and then stores the data.
9.1.  System creates an ROR Eligible Registrants Estimate record to capture the entered estimate for each county. The ROR Eligible Registrants Estimates will be associated to the appropriate ROR record.
10.  System presents message confirming success of the update.
Alternative Flows: / N/A
Exceptions: / N/A
Includes: / N/A
Frequency of Use: / Frequency of ROR (EC 2187):
§  Gubernatorial Election Years: 5 RORs
§  Presidential Election Years: 8 RORs, 2 of which overlap
§  Odd-Numbered Years: 1 ROR
Business Rules: / §  SOS Users can edit estimates for ROR’s that are open or closed.
§  Once the ROR is finalized and published, the data associated with that ROR, including the estimated eligible voters, should be locked down and changes prohibited (except maybe by someone with extra special privilegeswith the appropriate security role).
§  Data in the ROR Eligible Registrants Estimate record for an individual county must be numerical.
§  Data in the ROR Eligible Registrants Estimate record for an individual county must be no higher than 99,999,999.
Assumptions: / N/A
Notes and Issues: / N/A

Revision History

Date / Document
Version / Document Revision
Description / Revision Author
02/05/2010 / 0.1 / Initial Draft / Victor Vergara
02/05/2010 / 1.0 / Minor edits and release to client. / Maureen Lyon
02/08/2010 / 1.1 / Incorporate Client Feedback / Victor Vergara
02/08/2010 / 1.2 / Submit to client for review / Maureen Lyon
03/17/2010 / 1.3 / Incorporate Client Feedback from QA Checklist / Kimanh Nguyen / Kalyn Farris
03/22/2010 / 1.4 / QA and Release to Client for Review / Don Westfall
04/05/2010 / 1.5 / 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/05/2010
Version: 1.54 / Page 3