+ All Categories
Home > Documents > Screen Flow Diagrams

Screen Flow Diagrams

Date post: 03-Feb-2022
Category:
Upload: others
View: 22 times
Download: 0 times
Share this document with a friend
16
Screen Flow Diagrams This section illustrates the flow of screens in the functional parts of the site. It shows in detail the sequence in which forms, pop-up windows and confirmation windows are presented.
Transcript

Screen Flow Diagrams

This section illustrates the flow of screens in the functional parts of the site. It shows in detail the sequence in which forms, pop-up windows and confirmation windows are presented.

33

Log In for Members and Registered Guests | Screen Flow Diagram

User enters e-mail address and password. Here are the possible outcomes:

login_f.jsp

E-mail address is recognized, but password doesn’t match the password on the record:

Log in is attempted five times without success:

Log in successful:

loginpassed_p.htm loginfailed_p.htm loginlocked_p.htm

34

Forgot Password | Screen Flow Diagram

User is a member or registered guest, and has forgotton their password.

login_f.jsp

E-mail address is on record:

forgotPassword_f.htm

email_pwd_d.jsp

E-mail address is not on record:

email_pwd_d.jsp

User enters e-mail address and submits form. There are two possible outcomes:

35

Change Password | Screen Flow Diagram

User is a member or registered guest, and wants to change their password.

login_f.jsp

Password changed successfully:

new_pwd_f.jsp

change_pwd_d.jsp

Old password entered is not on record:

User enters e-mail address, old password, new password and re-enters new password. The following outcomes are possible:

change_pwd_d.jsp change_pwd_d.jsp

System error:

36

Site Registration | Screen Flow Diagram

User registers as a guest. This function can also be accessed from Job Bank and Help.

login_f.jsp

User completes these required fields. There are two possible outcomes:

Registration is successful:

register_f.jsp

regpassed_p.htm

regfailed_p.htm

Registration is unsuccessful due to system problems :

Thank you for registering on the DMI Web site.Here is your personal login information. Your login id is: #loginId#Your password is: #password#

37

Membership Application | Screen Flow Diagram

Users can access the membership application from the “Join DMI” link at the top of the page, Member Center, or pop-up windows verifying membership for member-only benefits.

User completes the required fields and clicks on “Continue”.

If user is logged in as a registered guest, information from their client record will automatically populate this form.

See next page.

member_f.jsp

38

Membership Application | Screen Flow Diagram

The system checks to see if it has a client record with this user’s e-mail address and password. If not, the user is asked to create a password.

If a client record containing an e-mail address and pass-word already exists for this user, they go to the payment screen. See next page.

User enters password and re-enters password. See next page.

create_pwd_f.jsp

39

Membership Application | Screen Flow Diagram

User is alerted they are going to a secured site for payments.

payment_f.jsp

User completes these required fields.

If user is logged in as a regis-tered guest, information from their client record will auto-matically populate this form.

There are three possible out-comes.

See next page.

40

Membership Application | Screen Flow Diagram

Payment is successful:

memconf_f.jsp

Payment fails due to system error:

paymentfailed_p.htm

Payment rejected because credit card was declined:

paymentRejected.jsp

Dear #FirstName# #LastName#,

Thank you for becoming a DMI member.You will receive in the next two weeks a membership packet, which includes a membership directory and the latest issue of the DMI Journal.

Membership Type:--------------------------------------------------------------------------------&Items&--------------------------------------------------------------------------------Total: #Total#

Thank you for supporting DMI.

Voice: 617-338-6380 Fax: 617-338-6570 E-Mail: [email protected]: http://www.dmi.org

User is returned to underlying page.

41

News Subscription | Screen Flow Diagram

subscribe_f.jsp

If user is logged in as a regis-tered guest, information from their client record will auto-matically populate this form.

User completes required fields.

The system checks to see if it has a client record with this user’s e-mail address and password. If not, the user is asked if they want to become a registered guest by creating a password.

If a client record containing an e-mail address and pass-word already exists for this user, they go to the confirma-tion page.

newsconf_f.jsp

User enters password and re-enters password.

wantregister_p.jsp

create_pwd_f.jsp

42

Conference Registration - Conference Not Full | Screen Flow Diagram

register_f.jsp

The name, dates and loca-tions of the conference are dynamically generated here.

If user is logged in, informa-tion from their client record will automatically populate this form.

User completes required fields.

If user is not logged in as a member or registered guest, the user is asked if they want to become a registered guest by creating a password.

If a client record containing an e-mail address and pass-word already exists for this user, they go to the payment screen. User enters password and re-

enters password.

wantregister_p.jsp

create_pwd_f.jsp

See next page for payments.

43

Conference Registration - Conference Not Full | Screen Flow Diagram

User is alerted they are going to a secured site for payments.

payment_f.jsp

Charges are calculated on membership level if user is logged in. Otherwise the full price is charged.

User completes these required fields.

If user is logged in as a regis-tered guest, information from their client record will auto-matically populate this form.

There are three possible out-comes.

See next page.

44

Conference Registration - Conference Not Full | Screen Flow Diagram

Payment is successful:

confconf_f.jsp

Payment fails due to system error:

paymentfailed_p.htm

Payment rejected because credit card was declined:

paymentRejected.jsp

User is returned to underlying page.

Dear #FirstName# #LastName#,

You are confirmed to attend this DMI conference.Your confirmation number is #Confirmation#.

You will also receive written confirmation in the mail. Please use your confirmation number for further reference.

Registered Conference:--------------------------------------------------------------------------------&Items&--------------------------------------------------------------------------------Total: #Total#

Check the DMI Web site for additional details about the conference.http://www.dmi.org/conference/conferences_s.htm

Thank you for supporting DMI.

Voice: 617-338-6380 Fax: 617-338-6570

E-Mail: [email protected]: http://www.dmi.org

45

Conference Registration - Conference Is Full | Screen Flow Diagram

conffull_f.jsp

The name, dates and loca-tions of the conference are dynamically generated here.

If user is logged in, informa-tion from their client record will automatically populate this form.

User completes required fields.

wantregister_p.jsp

See next page for payments.

register_f.jsp

If user is not logged in as a member or registered guest, the user is asked if they want to become a registered guest by creating a password. If a client record containing an e-mail address and password already exists for this user, they go to the payment screen.

create_pwd_f.jsp

User is returned to underlying page.

46

Conference Registration - Conference Is Full | Screen Flow Diagram

User is alerted they are going to a secured site for payments.

payment_f.jsp

Charges are calculated on membership level if user is logged in. Otherwise the full price is charged.

User completes these required fields.

If user is logged in as a regis-tered guest, information from their client record will auto-matically populate this form.

There are three possible out-comes.

See next page.

47

Conference Registration - Conference Is Full | Screen Flow Diagram

Payment information is provided correctly:

waitlist_p.htm

User is returned to underlying page.

If there is a cancellation, the user will be notified and payment processed manually.


Recommended