/ VoteCal Statewide Voter Registration System Project
Use Case: UC05.19.01 / Add/Edit Customer Organization Contact

Use Case: UC05.19.01 / Add/Edit Customer Organization Contact

Attribute / Details
System Requirements: / S26.1 VoteCal must allow authorized SOS administrators and authorized county users to input, track and review Public Voter Registration Data Requests (PVRDRs), including:
  • Requestor name;
  • Requestor ID number and type;
  • Requestor organization;
  • Requestor residence and business addresses;
  • Requestor contact information (phone, fax, email addresses);
  • If Requestor is acting as an authorized agent for a qualified party, the name, address and contact information for the party legally qualified to purchase the data;
  • Requestor’s stated purpose/use for the data;
  • Date of application;
  • Date application received;
  • Basis for qualification (election, party, academic, journalist, etc.);
  • Date of application fulfillment or denial;
  • Status of application;
  • Criteria used to select/exclude records for the extract; and
  • Filename(s) and number of records provided in the extract.
S28.1 VoteCal must allow an authorized SOS or county user the ability to record the issuance of blank voter registration affidavits to an individual or organization from SOS, including:
  • The name and contact information of the person who requested and received the affidavits;
  • The name of the organization if any;
  • The date of issuance; and
  • The range of affidavits issued.

Description: / The purpose of this use case is to allow a user to create or modifya contact for a customerorganization in the system.
Actors: / SOS User, CountyUser
Trigger: / User initiates the use case when there is a need to create or edit a new Contact[IV&V1]for aCustomer Organization in the system. This use case is always invoked from another use case.
System: / VoteCal Application
Preconditions: /
  • All global preconditions apply.

Post conditions: /
  • AnewContact record is createdor modified for the selected Customer Organization. The new or modifiedContact record is passed back to the invokinguse case[IV&V2].
  • All global post conditions apply.

Normal Flow: /
  1. Use case is invoked from another use case to add a Contact.
  2. System presents UI05.xxxAdd Customer Organization Contactscreen.
  3. User enters information for the new Contact, such as (* required):
  • Name*
  • Address, City, State, Zip Code*
  • Phone Number
  • Email address
  • Status* – Active or Inactive
  • Comments
  1. User selects the “Save” command to create the new contact.
  2. System validates that no business rules are violated, and then stores data.
  3. System creates a new Contact, and associates it to the Customer Organization.
  4. The new Contact is passed back to the invoking use case.

Alternative Flows: / 1a Use case is invoked from another use case to edit a Contact.
1a.1 System presents UI05.xxx Edit Customer Organization Contactscreen.
1a.2 User modifies information about the Contact, including:
  • Name*
  • Address, City, State, Zip Code*
  • Phone Number
  • Status* – Active or Inactive
  • Comments
1a.3 User selects the “Save” command to updatethe contact.
1a.4 System validates that no business rules are violated[IV&V3]all required fields are entered, and then stores data.
1a.5 System updates the Contact record.
1a.6 The use case ends[IV&V4].new Contact is passed back to the invoking use case.
Exceptions: / N/A
Includes: / N/A
Frequency of Use: / TBD.
Business Rules: / N/A
Assumptions: /
  • A Customer Organization may have multiple Contacts.

Notes and Issues: / N/A

Revision History

Date / Document
Version / Document Revision
Description / Revision Author
11/30/2009 / 0.1 / Initial Draft / Victor Vergara
01/12/2010 / 1.0 / Release to Client / Victor Vergara
02/02/2010 / 1.1 / Incorporate Client Feedback / Victor Vergara
02/03/2010 / 1.2 / Submit to client for review / Maureen Lyon
02/11/2010 / 1.3 / Incorporate Client Feedback / Victor Vergara
03/17/2010 / 1.4 / Incorporate Client Feedback / Kimanh Nguyen
03/19/2010 / 1.5 / QA and Release to Client 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

[IV&V1]Paula: Missing reference to edit Contact.

KN: Accepted. Added “or edit”.

[IV&V2]Paula: Missing the reference to edit Contact.

KN: Accepted. Modified text accordingly

[IV&V3]Art: We should either define the business rules being checked or indicate by reference where they can be found.

KN: Added one basic validation.

[IV&V4]Paula: Would the edited contact be passed back to the invoking use case?

KN: Accepted.