Roy Zornow MS Word version

IA / UX Designer

email:
 
  wireframes site maps process flows ui design documents misc
  · dashboard
· big company · clearance · Google redesign · func specs · configurator
  · mobile
· finance demo · flash minisite · compare nav. · user task map · feature spectrum
  · magazine
· numbered pages · decision matrix · insurance form · use case · best practices
  · simple
· dynamic content · create account · admin page · visualization · mobile voice
  · message board · products · wizard · plugin · fields defined · mobile search
  · templates                 · mobile conversion

 

Field inheritances:  

Question

Current page

If answer is yes

If answer is no

“Employer Information” questions

emp_1.html

pre-populate fields (alternative: do not show questions) if this data can be inherited from Employer logon

“Is this claim for the Employee or for a Dependent?      

emp_1.html

If employee “Next” button should not link to dependent questions (dep.html), should go directly to cov_1.html

If dependent:

a)       “Next” button should go to dependent questions

dep.html

 

“Was Life Insurance ever cancelled?”

emp_1.html

display subsequent “Cancellation Date” question

either:

 a) do not generate a “Cancellation Date” question at all or

 b) if system must display all questions,   gray it out

 

“Is this claim for the Employee or for a Dependent?      

emp_1.html

If employee either:

 display both subsequent “employee” questions, hide dependeing q’s (ci_d3.html)

If dependent:

b)       do not generate subsequent employee questions, go directly to dependent questions

 

“Absolute Assignment?”

cov_1.html   

 

Display subsequent “Assignment Date” question

a) do not generate a “Assignment Date” question at all or

 b) if system must display all questions, gray it out

 

“Evidence of Insurance Required?”

cov_1.html   

 

Display “Date Evidence of Insurance approved” question

Either:

a) do not generate a “Date Evidence of Insurance approved” question at all or

 b) if system must display all questions, gray it out

 

Life Plan

cov_1.html

User selects plan(s), clicks “Confirm Choices”, system stores choices to be used later in Beneficiary section.  In the beneficiary section the user will be asked which Life Plans apply to a particular beneficiary.  The pool of available Life Plan choices is created by the answer to the “Life Plan” question on cov_1.html

“Number of Beneficiaries”

ben_1.html

System should generate questions based on the answer to this number. 

 

If user selects “2”, generate 2 sets of beneficiary questions: Beneficiary 1 questions and Beneficiary 2 questions. (there will always be a “Beneficiary 1”)

 

If user selects “1”, generate 1 set of beneficiary questions: and do not show the subsequent question “same address for all?” and “same address as previous beneficiary?”

 

“Same Address for all?”

 

precondition: user has selectd more than one beneficiary in “Number of Beneficiaries” question, which directly precedes “Same Address for All”

ben_1.html

if yes,  pre-populate subsequent beneficiary address fields with answer received in Beneficiary 1 addess fields.

 

ALSO: do not display a “same address as previous beneficiary” option for ben’s subsequent to Beneficiary 1

if no, do not pre-populate subsequent beneficiary address fields with answer received in Beneficiary 1 addess fields.

 

ALSO: display a “same address as previous beneficiary” option for ben’s subsequent to Beneficiary 1

“Beneficiary Entity”

ben_1.html

If user selects “Trust”:

Generate Trust Date” and “Trustee Executor” questions

a) do not generate a “Trust Date” and “Trustee Executor” question at all or

 b) if system must display all questions,   gray out these questions

 

Use same coverage dates as above?

ben_1.html

if “yes” prepopulate coverage fields based on answers in preceding plan.

Select coverage(s) for Beneficiary 1:

ben_1.html

System generates fields for this question (in a combo box) based on inheriting plan names from “Life Plan” question on cov_1.html

Use same address as a previous beneficiary?

ben_2.html

if “yes” prepopulate address fields based on answers in preceding beneficiary.

Use same Basic Life: coverage dates as a previous beneficary?:

ben_2.html

if “yes” prepopulate date fields based on answers in preceding beneficiary section, specifically the answers given for the same Life Plan, in this case “Basic Life”.

Link at bottom of all pages: “Save Application and Finish Later”

All pages

This link has two child pages (not in prototype)

-          child page “Are you sure you want to stop now and save your application for later?”

o        child of child page: “Your application has been saved” (show link to submit new application)

 

Link at bottom of all pages: “Cancel Application”

All pages

-          child page “Are you sure you want to cancel your application? It will not be saved.”

o        child of child page: “Your application has been canceled.” (show link to submit new application)