United States Department of Agriculture (USDA) eGovernment Program

#########  {#section .unnumbered}

######### usda.gov Use Case Scenarios {#usda.gov-use-case-scenarios .unnumbered}

June 2003

![](media/image1.jpeg){width="1.75in" height="1.2666666666666666in"}

**Table of Contents**

[Revision History v](#revision-history)

[Previous Change History v](#previous-change-history)

[Document Sign-off v](#document-sign-off)

[1 Introduction 6](#introduction)

[1.1 Use Case Overview 6](#use-case-overview)

[2 Actor Catalog 8](#actor-catalog)

[3 Register New User 9](#register-new-user)

[3.1 Description 9](#description-1)

[3.2 Actors 9](#actors-1)

[3.3 Pre-Conditions 9](#pre-conditions-1)

[3.4 Flow 9](#flow-1)

[3.5 Post Conditions 10](#post-conditions-1)

[3.6 Requirements Cross-Reference 10](#requirements-cross-reference-1)

[4 Login 11](#login)

[4.1 Description 11](#description-2)

[4.2 Actors 11](#actors-2)

[4.3 Pre-Conditions 11](#pre-conditions-2)

[4.4 Flow 11](#flow-2)

[4.5 Post Conditions 13](#post-conditions-2)

[4.6 Requirements Cross-Reference 13](#requirements-cross-reference-2)

[5 Edit Profile 15](#edit-profile)

[5.1 Description 15](#description-3)

[5.2 Actors 15](#actors-3)

[5.3 Pre-Conditions 15](#pre-conditions-3)

[5.4 Flow 15](#flow-3)

[5.5 Post Conditions 16](#post-conditions-3)

[5.6 Requirements Cross-Reference 16](#requirements-cross-reference-3)

[6 Customize Portal 17](#customize-portal)

[6.1 Description 17](#description-4)

[6.2 Actors 17](#actors-4)

[6.3 Pre-Conditions 17](#pre-conditions-4)

[6.4 Flow 17](#flow-4)

[6.5 Post Conditions 18](#post-conditions-4)

[6.6 Requirements Cross-Reference 18](#requirements-cross-reference-4)

[7 View Portal Content 19](#view-portal-content)

[7.1 Description 19](#description-5)

[7.2 Actors 19](#actors-5)

[7.3 Pre-Conditions 19](#pre-conditions-5)

[7.4 Flow 19](#flow-5)

[7.5 Post Conditions 20](#post-conditions-5)

[7.6 Requirements Cross-Reference 20](#requirements-cross-reference-5)

[8 Conduct Simple Search 21](#conduct-simple-search)

[8.1 Description 21](#description-6)

[8.2 Actors 21](#actors-6)

[8.3 Pre-Conditions 21](#pre-conditions-6)

[8.4 Flow 21](#flow-6)

[8.5 Post Conditions 22](#post-conditions-6)

[8.6 Requirements Cross-Reference 22](#requirements-cross-reference-6)

[9 Conduct Advanced Search 23](#conduct-advanced-search)

[9.1 Description 23](#description-7)

[9.2 Actors 23](#actors-7)

[9.3 Pre-Conditions 23](#pre-conditions-7)

[9.4 Flow 23](#flow-7)

[9.5 Post Conditions 25](#post-conditions-7)

[9.6 Requirements Cross-Reference 25](#requirements-cross-reference-7)

[10 View Frequently Asked Questions
26](#view-frequently-asked-questions)

[10.1 Description 26](#description-8)

[10.2 Actors 26](#actors-8)

[10.3 Pre-Conditions 26](#pre-conditions-8)

[10.4 Flow 26](#flow-8)

[10.5 Post Conditions 26](#post-conditions-8)

[10.6 Requirements Cross-Reference 27](#requirements-cross-reference-8)

[11 View Help 28](#view-help)

[11.1 Description 28](#description-9)

[11.2 Actors 28](#actors-9)

[11.3 Pre-Conditions 28](#pre-conditions-9)

[11.4 Flow 28](#flow-9)

[11.5 Post Conditions 29](#post-conditions-9)

[11.6 Requirements Cross-Reference 29](#requirements-cross-reference-9)

[12 Subscribe/Unsubscribe to Email Notifications
30](#subscribeunsubscribe-to-email-notifications)

[12.1 Description 30](#description-10)

[12.2 Actors 30](#actors-10)

[12.3 Pre-Conditions 30](#pre-conditions-10)

[12.4 Flow 30](#flow-10)

[12.5 Post Conditions 31](#post-conditions-10)

[12.6 Requirements Cross-Reference 31](#requirements-cross-reference-10)

[13 Contact Us 32](#contact-us)

[13.1 Description 32](#description-11)

[13.2 Actors 32](#actors-11)

[13.3 Pre-Conditions 32](#pre-conditions-11)

[13.4 Flow 32](#flow-11)

[13.5 Post Conditions 33](#post-conditions-11)

[13.6 Requirements Cross-Reference 33](#requirements-cross-reference-11)

[14 Ask the Expert 34](#ask-the-expert)

[14.1 Description 34](#description-12)

[14.2 Actors 34](#actors-12)

[14.3 Pre-Conditions 34](#pre-conditions-12)

[14.4 Flow 34](#flow-12)

[14.5 Post Conditions 35](#post-conditions-12)

[14.6 Requirements Cross-Reference 35](#requirements-cross-reference-12)

[15 Terminate User Session 36](#terminate-user-session)

[15.1 Description 36](#description-13)

[15.2 Actors 36](#actors-13)

[15.3 Pre-Conditions 36](#pre-conditions-13)

[15.4 Flow 36](#flow-13)

[15.5 Post Conditions 37](#post-conditions-13)

[15.6 Requirements Cross-Reference 37](#requirements-cross-reference-13)

#   {#section-1 .unnumbered}

# Revision History

## Previous Change History {#previous-change-history .unnumbered}

Table a -- Previous Change History

  --------------------------- ------------------------ -------------------------- -----------------------------
  **[Version]{.smallcaps}**   **[Date]{.smallcaps}**   **[Author]{.smallcaps}**   **[Comment]{.smallcaps}**

  0.0                         04/14/2003               Bernette T. Wheeler        Initial Draft

  0.1                         05/28/2003               Cristin Witcher            Populated draft with use
                                                                                  cases

  0.2                         05/30/2003               Bernette T. Wheeler        Documented initial sections
                                                                                  of the document and updated
                                                                                  use cases

  0.3                         06/04/2003               Cristin Witcher            Updated with formatting
                                                                                  changes

  0.4                         06/05/2003               Bernette T. Wheeler        Updated use cases.

  0.5                         06/05/2003               Cristin Witcher            Updated use case flows with
                                                                                  discussed changes. Added use
                                                                                  cases detailing changing
                                                                                  password, and viewing content
                                                                                  processes.

  0.6                         06/09/2003               Bernette T. Wheeler        Updated use cases.

  0.7                         06/10/2003               Liesl Awalt                Updated use cases.

  0.8                         06/12/2003               Cristin Witcher            Updated use cases.

  0.9                         06/18/2003               Bernette T. Wheeler        Updated use cases with
                                                                                  working group comments.

                                                                                  

                                                                                  

                                                                                  
  --------------------------- ------------------------ -------------------------- -----------------------------

## Document Sign-off {#document-sign-off .unnumbered}

Table b -- Document Sign-off

  ------------------------ ------------------------ ---------------------------------------
  **[Date]{.smallcaps}**   **[Name]{.smallcaps}**   **[Title]{.smallcaps}**

                                                    
  ------------------------ ------------------------ ---------------------------------------

# Introduction

The primary objective of this document is to define use cases, or user
scenarios, for usda.gov. A use case is a goal-oriented sequence of
interactions that occur between the actor and the application in
completing an event online with USDA. Use cases in this document are
cross-referenced to the application requirements, thereby ensuring that
key business objectives are incorporated into the design and development
of the portal. Further, the detailed explanation of these interactions
provides directional focus in testing application functionality prior to
implementation. The use cases serve as input to the creation of test
conditions and expected results in test script documents.

This document includes the following sections:

-   **Use Case Overview:** The use case overview section includes a
    brief description of the use case sections and the type of
    information included in each section.

-   **Use Case Scenario:** The use case scenario sections are a
    collection of individual use cases representing a goal-oriented
    interaction on the system from the trigger event (start) to the goal
    (finish).

The usda.gov Use Case Scenarios should be considered a living document.
The contents of this document might change and evolve in response to
change of initiative direction and/or additional information obtained
from the design phase.

## Use Case Overview

This section describes how each detailed use case scenario will be
structured.

### Description

The Description section includes a brief statement on the objective or
goal of the use case. It may also include a high-level explanation of
the sequence of actions and the outcome of executing the use case.

### Actors

The Actors section lists use case actors, who initiate this use case or
who are involved in executing this use case. It identifies the users of
the system.

### Pre-Conditions

The Pre-Conditions specify requirements on the state of the system prior
to this use case being valid.

### Flow

The Flow section contains the typical flow of the use case along with
alternate and exception flows.

### Post Conditions

Post Conditions describe the state of the system following successful
completion of the use case being valid.

###  {#section-2 .unnumbered}

### Requirements Cross-Reference

The Requirements Cross-Reference section lists the specific requirement
numbers driving each use case.

# Actor Catalog

  -----------------------------------------------------------------------------
  **[A]{.smallcaps}CTOR**   **[D]{.smallcaps}ESCRIPTION**
  ------------------------- ---------------------------------------------------
  Registered Users          This actor represents all users who have created an
                            account in the system and who are able to access
                            personalized areas of the site through a login
                            process.

  All Users                 This actor represents all the above actors and
                            other users of the system.
  -----------------------------------------------------------------------------

# Register New User

## Description

The primary objective of this use case is to describe the user
registration process. Actors will register in order to have access to
personalized portal content.

## Actors

All Users

## Pre-Conditions

The actor has navigated to the usda.gov home page or any page on the
site.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor navigates to    | 2.  The user registration page is    |
|     the user registration     |     displayed with form fields to    |
|     page.                     |     collect registration             |
|                               |     information. Requested           |
|                               |     registration information         |
|                               |     includes:                        |
|                               |                                      |
|                               | > -User ID                           |
|                               | >                                    |
|                               | > -Password                          |
|                               | >                                    |
|                               | > -Confirm Password                  |
|                               | >                                    |
|                               | > -Password Hint (Question and       |
|                               | > Answer)                            |
|                               | >                                    |
|                               | > -Email Address                     |
|                               | >                                    |
|                               | > -Geographic Location (State,       |
|                               | > County)                            |
|                               | >                                    |
|                               | > -Audience Type                     |
+-------------------------------+--------------------------------------+
| 3.  The actor completes and   | 4.  The system validates the         |
|     submits the registration  |     registration information and     |
|     form.                     |     displays a page allowing the     |
|                               |     actor to select his or her areas |
|                               |     of interest.                     |
+-------------------------------+--------------------------------------+
| 5.  The actor completes and   | 6.  The system validates the         |
|     submits the registration  |     registration information and     |
|     form.                     |     displays a verification page for |
|                               |     the actor to confirm the         |
|                               |     submitted information.           |
+-------------------------------+--------------------------------------+
| 7.  The actor confirms the    | 8.  The system displays a            |
|     verification page.        |     confirmation page alerting the   |
|                               |     actor that the operation has     |
|                               |     succeeded. From this             |
|                               |     confirmation page the actor has  |
|                               |     the option to return to          |
|                               |     usda.gov, or view his or her     |
|                               |     personalized portal by           |
|                               |     logging-in with the appropriate  |
|                               |     user ID and password.            |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### Edit Registration Information

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Register New     | 2.  The system displays the          |
|     User use case, Typical    |     registration page populated with |
|     Flow step 6, the actor    |     the actor's original selections. |
|     chooses to edit his or    |     The actor continues from Typical |
|     her registration          |     Flow step 3 or 5 depending on if |
|     settings.                 |     the actor edited profile         |
|                               |     information or areas of          |
|                               |     interest.                        |
+-------------------------------+--------------------------------------+

#### Cancel Registration

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Register New     | 2.  The registration operation is    |
|     User use case, Typical    |     cancelled and the use case ends. |
|     Flow steps 3, 5 or 7, the |                                      |
|     actor cancels the         |                                      |
|     registration process.     |                                      |
+-------------------------------+--------------------------------------+

### Exception Flow

#### Invalid Registration Data

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Register New     | 2.  The system validates the         |
|     User use case, Typical    |     registration information and     |
|     Flow step 3, the actor    |     determines that invalid data was |
|     completes and submits the |     entered or appropriate data is   |
|     registration form.        |     missing. A custom error message  |
|                               |     is displayed prompting the actor |
|                               |     to correct the necessary         |
|                               |     registration information. The    |
|                               |     actor continues from Typical     |
|                               |     Flow step 3.                     |
+-------------------------------+--------------------------------------+

## Post Conditions

Following successful execution of the use case, the actor has created a
new account in the system and may use that account to login to the
personalized areas of the site.

## Requirements Cross-Reference

REG-001, REG-003, TRK-003

# Login

## Description

The primary objective of this use case is to describe the authentication
or login process for registered actors accessing his or her secure
personalized usda.gov portal.

## Actors

Registered Users

## Pre-Conditions

The actor is registered for the member-only services of the usda.gov
portal and has been issued login credentials. The actor is not already
logged in.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor navigates to    | 2.  The login page is displayed with |
|     the login page from the   |     form fields to collect login     |
|     main usda.gov home page.  |     credentials. Required login      |
|                               |     credentials include:             |
|                               |                                      |
|                               | > -User ID                           |
|                               | >                                    |
|                               | > -Password                          |
+-------------------------------+--------------------------------------+
| 3.  The actor enters his or   | 4.  The system verifies the login    |
|     her user ID and password  |     credentials and logs the actor   |
|     and submits the login     |     into the portal. A personalized  |
|     form. The actor also has  |     portal page is displayed to the  |
|     the option to use the     |     actor. The system records an     |
|     password hint.            |     entry in the authenticated       |
|                               |     user's log file.                 |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### Persistent Login

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Login use case,  | 2.  The system verifies the login    |
|     Typical Flow step 3, the  |     credentials and logs the actor   |
|     actor selects the option  |     into the portal. The system      |
|     to save the user ID and   |     saves a persistent cookie in the |
|     password fields.          |     actor's browser so the actor     |
|                               |     does not have to re-enter login  |
|                               |     information at the next login    |
|                               |     attempt. A personalized portal   |
|                               |     page is displayed to the actor.  |
|                               |     The system records an entry in   |
|                               |     the authenticated user's log     |
|                               |     file.                            |
+-------------------------------+--------------------------------------+

#### Cancel Login

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Login use case,  | 2.  The login attempt is cancelled   |
|     Typical Flow step 3, the  |     and the use case ends.           |
|     actor cancels the login   |                                      |
|     process.                  |                                      |
+-------------------------------+--------------------------------------+

####  {#section-3 .unnumbered}

#### Change Password

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Login use case,  | 2.  The system displays the Login    |
|     Typical Flow step 1 OR    |     Help page with the following     |
|     step 2, the actor         |     options:                         |
|     navigates to the Login    |                                      |
|     Help page from the home   | > \- Forgot your password?           |
|     page by selecting "Login  | >                                    |
|     Help" OR from the login   | > \- Forgot your user ID?            |
|     page by selecting "Help". | >                                    |
|                               | > \- Change Password                 |
+-------------------------------+--------------------------------------+
| 3.  The actor decides to      | 4.  The system displays the change   |
|     change his or her         |     password form. The following     |
|     password and selects the  |     information is displayed:        |
|     "Change Password" option. |                                      |
|                               | > \- User ID                         |
|                               | >                                    |
|                               | > \- Password                        |
+-------------------------------+--------------------------------------+
| 5.  The user enters his or    | 6.  The system validates the actor's |
|     her user ID and current   |     information and displays options |
|     password.                 |     to the actor to change his or    |
|                               |     her password:                    |
|                               |                                      |
|                               | > \- New Password                    |
|                               | >                                    |
|                               | > \- Confirm New Password            |
|                               |                                      |
|                               | \- Password Hint Question            |
|                               |                                      |
|                               | \- Password Hint Answer              |
+-------------------------------+--------------------------------------+
| 7.  The actor populates all   | 8.  The system validates the actor's |
|     fields on the change      |     information and displays a       |
|     password form and submits |     verification page to verify that |
|     the form.                 |     the actor wants to change his or |
|                               |     her password. (Password fields   |
|                               |     are encrypted).                  |
+-------------------------------+--------------------------------------+
| 9.  The actor confirms the    | 10. The system stores the updated    |
|     verification page.        |     password settings and displays a |
|                               |     confirmation page to the actor.  |
+-------------------------------+--------------------------------------+

#### Password Hint

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Login use case,  | 2.  The system displays the Login    |
|     Typical Flow step 1 OR    |     Help page with the following     |
|     step 2, the actor         |     options:                         |
|     navigates to the Login    |                                      |
|     Help page from the home   | > \- Forgot your password?           |
|     page by selecting "Login  | >                                    |
|     Help" OR from the login   | > \- Forgot your user ID?            |
|     page by selecting "Help". | >                                    |
|                               | > \- Change Password                 |
+-------------------------------+--------------------------------------+
| 3.  The actor selects the     | 4.  The system displays the password |
|     "Forgot your password?"   |     hint form. The following         |
|     option.                   |     information is displayed:        |
|                               |                                      |
|                               | > \- User ID                         |
+-------------------------------+--------------------------------------+
| 5.  The user enters his or    | 6.  The system retrieves the         |
|     her user ID and retrieves |     information associated with the  |
|     the password hint         |     user ID. The following           |
|     question.                 |     information is displayed:        |
|                               |                                      |
|                               | \- Password Hint Question            |
|                               |                                      |
|                               | \- Password Hint Answer              |
+-------------------------------+--------------------------------------+
| 7.  The actor enters the      | 8.  The system validates the actor's |
|     answer to the password    |     information and displays options |
|     hint question.            |     to the actor to change his or    |
|                               |     her password. This use case      |
|                               |     continues from the Login Use     |
|                               |     Case, Change Password Alternate  |
|                               |     Flow step 4.                     |
+-------------------------------+--------------------------------------+

####  {#section-4 .unnumbered}

#### Forgotten User ID

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Login use case,  | 2.  The system displays the Login    |
|     Typical Flow step 2, the  |     Help page with the following     |
|     actor navigates to the    |     options:                         |
|     usda.gov login page but   |                                      |
|     has forgotten his or her  | > \- Forgot your password?           |
|     user ID. The actor        | >                                    |
|     selects the "Help" option | > \- Forgot your user ID?            |
|     from the login page.      | >                                    |
|                               | > \- Change Password                 |
+-------------------------------+--------------------------------------+
| 3.  The actor selects the     | 4.  A message is displayed prompting |
|     option for forgotten user |     the actor to create a new        |
|     ID.                       |     account with new login           |
|                               |     credentials.                     |
+-------------------------------+--------------------------------------+

### Exception Flow

#### Invalid Password

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Login use case,  | 2.  The system attempts to verify    |
|     Typical Flow step 3 OR    |     the login credentials and        |
|     from the Change Password, |     determines that the actor's      |
|     Alternate Flow step 5,    |     password is invalid. A custom    |
|     the actor enters his or   |     error message is displayed to    |
|     her login credentials and |     the actor prompting them to try  |
|     submits the login form.   |     the login again and it also      |
|                               |     displays the number of attempts  |
|                               |     remaining.                       |
+-------------------------------+--------------------------------------+
| 3.  The actor enters his or   | 4.  The system attempts to verify    |
|     her user ID and password  |     the login credentials and        |
|     in the login fields a     |     determines that the actor's      |
|     second time and submits   |     password is invalid. A custom    |
|     the login form.           |     error message is displayed to    |
|                               |     the actor prompting them to try  |
|                               |     the login again and it also      |
|                               |     displays the number of attempts  |
|                               |     remaining.                       |
+-------------------------------+--------------------------------------+
| 5.  The actor enters his or   | 6.  The system attempts to verify    |
|     her user ID and password  |     the login credentials and        |
|     in the login fields a     |     determines that the actor's      |
|     third time and submits    |     password is invalid. A custom    |
|     the login form.           |     error message is displayed       |
|                               |     alerting the actor that the      |
|                               |     account has been disabled or     |
|                               |     locked out and prompting the     |
|                               |     actor with further actions to    |
|                               |     take.                            |
+-------------------------------+--------------------------------------+

####  {#section-5 .unnumbered}

#### Invalid User ID

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Login use case,  | 2.  The system determines that the   |
|     Typical Flow step 3 OR    |     user ID is invalid. The system   |
|     from the Change Password, |     displays a custom error message  |
|     Alternate Flow step 5 OR  |     to the actor notifying him or    |
|     from the Password Hint    |     her that the user ID does not    |
|     Alternate Flow step 5,    |     exist. The actor continues from  |
|     the actor enters his or   |     Forgotten User ID Alternate Flow |
|     her login credentials and |     step 1\...                       |
|     submits the login form.   |                                      |
+-------------------------------+--------------------------------------+

## Post Conditions

In successful execution of the use case, the actor is logged into the
system and may navigate to the personalized areas of interest.
Otherwise, the system's state is unchanged and the actor may navigate to
other areas of the site.

## Requirements Cross-Reference

REG-004, REG-006, REG-007, REG-008, TRK-001, TRK-002, TRK-005, SEC-002,
SEC-007

# Edit Profile

## Description

The primary objective of this use case is to describe the process of
updating user registration information. Registered users will have the
ability to update his or her profile settings at any time. Editable
information includes email address, user group, areas of interest, and
geographic location.

## Actors

Registered users

## Pre-Conditions

The actor has registered for a personalized portal account and had
logged into usda.gov using his or her login credentials.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor navigates to    | 2.  The system displays the actor's  |
|     the edit profile page.    |     profile form populated with the  |
|                               |     actor's previously selected      |
|                               |     profile settings or registration |
|                               |     information. Profile settings    |
|                               |     include:                         |
|                               |                                      |
|                               | > -Change Password                   |
|                               | >                                    |
|                               | > -Email Address                     |
|                               | >                                    |
|                               | > -Geographic Location (State,       |
|                               | > County)                            |
|                               | >                                    |
|                               | > -Audience Type                     |
|                               | >                                    |
|                               | > -Areas of Interest                 |
+-------------------------------+--------------------------------------+
| 3.  The actor modifies the    | 4.  The system validates the profile |
|     profile form with the     |     settings and displays a          |
|     desired updates and       |     verification page for the actor  |
|     submits the form.         |     to confirm the submitted         |
|                               |     information.                     |
+-------------------------------+--------------------------------------+
| 5.  The actor confirms the    | 6.  The system stores the updated    |
|     verification page.        |     profile settings and displays a  |
|                               |     confirmation page to the actor.  |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### Edit Profile Settings

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Edit Profile use | 2.  The system displays the profile  |
|     case, Typical Flow step   |     form populated with the actor's  |
|     4, the actor chooses to   |     previously selected profile      |
|     edit his or her profile   |     information. The actor returns   |
|     settings.                 |     to Typical Flow step 3.          |
+-------------------------------+--------------------------------------+

#### Change Password

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Edit Profile use | 2.  The system displays the change   |
|     case, Typical Flow step   |     password form and the use case   |
|     3, the actor selects the  |     continues with Login use case,   |
|     "Change Password" option. |     Alternate Flow Change Password   |
|                               |     step 4.                          |
+-------------------------------+--------------------------------------+

### Exception Flow

#### Invalid Profile Data

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Edit Profile use | 2.  The system attempts to validate  |
|     case, Typical Flow step   |     the profile data and determines  |
|     3, the actor completes    |     that invalid data was entered or |
|     and submits the profile   |     that data is missing. A custom   |
|     form.                     |     error message is displayed       |
|                               |     prompting the actor to correct   |
|                               |     the necessary profile data. The  |
|                               |     use case continues with Typical  |
|                               |     Flow step 3.                     |
+-------------------------------+--------------------------------------+

## Post Conditions

In successful execution of the use case, the registered actor is able to
update his or her usda.gov account profile. A confirmation message will
be displayed to actor once the profile updates are successfully
completed.

## Requirements Cross-Reference

REG-005

###  {#section-6 .unnumbered}

# Customize Portal

## Description

The primary objective of this use case is to describe the customization
process for registered users wishing to further personalize his or her
usda.gov portal. Individual portal pages may also be customized to
reflect the user's content preferences.

## Actors

Registered users

## Pre-Conditions

The actor has registered for a personalized portal account and has
logged into usda.gov using his or her login credentials.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor accesses the    | 2.  The system displays a page that  |
|     page to be customized and |     allows the actor to specify and  |
|     navigates to the          |     organize the content they wish   |
|     customize options page.   |     to view on the portal page.      |
|                               |     Customization options include:   |
|                               |                                      |
|                               | > \- News Stories                    |
|                               | >                                    |
|                               | > \- Personalized Topics of Interest |
|                               | >                                    |
|                               | > \- Local Events                    |
|                               | >                                    |
|                               | > \- Programs                        |
|                               | >                                    |
|                               | > \- Reports and Publications        |
+-------------------------------+--------------------------------------+
| 3.  The actor selects the     | 4.  The system stores the actor's    |
|     content to be displayed   |     preferences and displays the     |
|     on the portal page, and   |     newly customized page to the     |
|     then submits the          |     actor.                           |
|     customized changes.       |                                      |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### Edit Customization Preferences

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Customize Portal | 2.  The system displays the          |
|     use case, Typical Flow    |     customize options page and the   |
|     step 4, the actor wishes  |     use case continues from Typical  |
|     to further customize his  |     Flow step 2.                     |
|     or her usda.gov portal.   |                                      |
|     The actor returns to the  |                                      |
|     customize options page.   |                                      |
+-------------------------------+--------------------------------------+

#### Cancel Customization

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Customize Portal | 2.  The system returns to the        |
|     use case, Typical Flow    |     current page without any         |
|     step 3, the actor chooses |     customized content.              |
|     to cancel the             |                                      |
|     customization process by  |                                      |
|     canceling changes and not |                                      |
|     submitting preferences.   |                                      |
+-------------------------------+--------------------------------------+

## Post Conditions

Following successful execution of the use case, the actor will have
created his or her own customized view of the portal page. Otherwise,
actors will only be able to view the default personalized portal pages.

## Requirements Cross-Reference

PER-002

# View Portal Content

## Description

The primary objective of this use case is to describe the process of
viewing the individual content sections available on portal pages.

## Actors

All users

## Pre-Conditions

The actor has navigated to the usda.gov home page.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the usda.gov home    | 2.  The system displays the chosen   |
|     page, the actor chooses   |     content to the actor. Types of   |
|     to view specific portal   |     content available from the home  |
|     content.                  |     page include:                    |
|                               |                                      |
|                               | > \- Top Stories                     |
|                               | >                                    |
|                               | > \- Information for (citizens,      |
|                               | > partners, and employees)           |
|                               | >                                    |
|                               | > \- USDA Highlights                 |
|                               | >                                    |
|                               | > \- Programs and Services Spotlight |
|                               | >                                    |
|                               | > \- Events                          |
|                               | >                                    |
|                               | > \- USDA Agencies and Offices       |
+-------------------------------+--------------------------------------+
| 3.  The actor selects the     | 4.  A list of programs is displayed  |
|     Programs section.         |     alphabetically by topic.         |
+-------------------------------+--------------------------------------+

###  {#section-7 .unnumbered}

### Alternate Flow

#### View Top Stories

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the View Portal      | 2.  The desired news content is      |
|     Content use case, Typical |     displayed.                       |
|     Flow step 3, the actor    |                                      |
|     chooses to view the full  |                                      |
|     article based on one of   |                                      |
|     the displayed top news    |                                      |
|     stories summaries.        |                                      |
+-------------------------------+--------------------------------------+

####  {#section-8 .unnumbered}

#### View Information For...

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the View Portal      | 2.  A secondary page that contains   |
|     Content use case, Typical |     related information based on the |
|     Flow step 3, the actor    |     topic selected by the user is    |
|     selects a specific topic  |     displayed.                       |
|     from the Information      |                                      |
|     for... section.           |                                      |
+-------------------------------+--------------------------------------+

#### View USDA Highlights

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the View Portal      | 2.  The desired news content is      |
|     Content use case, Typical |     displayed.                       |
|     Flow step 3, the actor    |                                      |
|     chooses to view the full  |                                      |
|     article based on one of   |                                      |
|     the displayed USDA        |                                      |
|     Highlights summaries.     |                                      |
+-------------------------------+--------------------------------------+

####  {#section-9 .unnumbered}

#### View Programs and Services Spotlight

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the View Portal      | 2.  The desired programs and         |
|     Content use case, Typical |     services content are displayed.  |
|     Flow step 3, the actor    |                                      |
|     chooses to view a         |                                      |
|     specific program update   |                                      |
|     or success from the       |                                      |
|     Programs and Services     |                                      |
|     Spotlight section.        |                                      |
+-------------------------------+--------------------------------------+

#### View Events

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the View Portal      | 2.  A list of events is displayed    |
|     Content use case, Typical |     grouped by the related area of   |
|     Flow step 3, the actor    |     interest. Events are further     |
|     chooses to view a list of |     organized by scheduled event     |
|     events from the Events    |     date.                            |
|     section.                  |                                      |
+-------------------------------+--------------------------------------+

####  {#section-10 .unnumbered}

#### View Agencies and Offices

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the View Portal      | 2.  A list of USDA agencies is       |
|     Content use case, Typical |     displayed alphabetically by      |
|     Flow step 3, the actor    |     mission area.                    |
|     selects the Agencies and  |                                      |
|     Offices section.          |                                      |
+-------------------------------+--------------------------------------+

## Post Conditions

In successful execution of the use case, the actor is able to view
content on the usda.gov portal.

## Requirements Cross-Reference

COM-008

# Conduct Simple Search

## Description

The primary objective of this use case is to describe the process of
conducting a search on the usda.gov portal. Actors are able to perform a
simple search by entering a keyword in the search text field on the
usda.gov home page.

## Actors

All users

## Pre-Conditions

The actor has navigated to the usda.gov home page or any page on the
usda.gov site.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor enters a search | 2.  The system performs a search     |
|     term in the simple search |     using the specified keyword. A   |
|     text field and submits    |     result set of information        |
|     the form.                 |     matching the search request is   |
|                               |     displayed. A defined number of   |
|                               |     result abstracts appear per page |
|                               |     and the search term is           |
|                               |     highlighted in each. The search  |
|                               |     result set includes:             |
|                               |                                      |
|                               | > -Title                             |
|                               | >                                    |
|                               | > -Subject                           |
|                               | >                                    |
|                               | > -Short abstract                    |
|                               | >                                    |
|                               | > -Publication date                  |
|                               | >                                    |
|                               | > -File format                       |
|                               | >                                    |
|                               | > -Agency affiliation (if available) |
+-------------------------------+--------------------------------------+
| 3.  The actor chooses to view | 4.  The system retrieves the         |
|     a specific item from the  |     selected search result and       |
|     search result set.        |     displays the content to the      |
|                               |     actor.                           |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### Refine the Search Term

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 3.  From the Conduct Simple   | 4.  The system performs the search   |
|     Search use case, Typical  |     and the use case continues from  |
|     Flow step 3, the actor    |     Typical Flow step 2.             |
|     chooses to refine his or  |                                      |
|     her search term. The      |                                      |
|     actor enters a new search |                                      |
|     term in the simple search |                                      |
|     text field and submits    |                                      |
|     the form.                 |                                      |
+-------------------------------+--------------------------------------+

#### Advanced Search

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Conduct Simple   | 2.  The system displays the advanced |
|     Search use case, Typical  |     search form. The simple search   |
|     Flow step 3, the actor    |     keyword is pre-populated in the  |
|     chooses to perform an     |     keyword field of the advanced    |
|     advanced search. The      |     search form. The actor continues |
|     actor selects the         |     with the Advanced Use Case       |
|     "Advanced Search"         |     Typical Flow step 2.             |
|     hyperlink.                |                                      |
+-------------------------------+--------------------------------------+

#### Cancel Search

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  After completion of the   | 2.  The search operation is          |
|     Conduct Simple Search use |     cancelled and the use case ends. |
|     case, Typical Flow step   |                                      |
|     1, the actor chooses to   |                                      |
|     cancel the search         |                                      |
|     operation.                |                                      |
+-------------------------------+--------------------------------------+

###  {#section-11 .unnumbered}

#### No Search Results

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Conduct Simple   | 2.  No results match the keyword     |
|     Search use case Typical   |     search criteria. The search      |
|     Flow step 1, the actor    |     mechanism offers alternative     |
|     conducts a simple search  |     search terms of related keyword  |
|     using a keyword.          |     topics and spelling suggestions. |
+-------------------------------+--------------------------------------+
| 3.  The actor performs        | 4.  The system performs the search   |
|     another simple search     |     and the use case continues from  |
|     using one of the          |     Typical Flow step 2.             |
|     suggested search terms or |                                      |
|     using a refined search    |                                      |
|     term.                     |                                      |
+-------------------------------+--------------------------------------+

### Exception Flow

#### No Search Results, No Search Suggestions

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 5.  From the Conduct Simple   | 6.  No results match the keyword     |
|     Search use case Typical   |     search criteria, and no          |
|     Flow step 1, the actor    |     alternative search term          |
|     conducts a simple search  |     suggestions are available in the |
|     using a keyword.          |     system. A message is displayed   |
|                               |     prompting the user to perform    |
|                               |     another search using different   |
|                               |     search criteria. This page also  |
|                               |     lists search tips.               |
+-------------------------------+--------------------------------------+
| 7.  The actor performs        | 8.  The system performs the search   |
|     another simple search     |     and the use case continues from  |
|     choosing another search   |     Typical Flow step 2.             |
|     term.                     |                                      |
+-------------------------------+--------------------------------------+

## Post Conditions

In successful execution of the use case, relevant search results are
displayed to the actor. Otherwise, the actor may perform an advanced
search or modify his or her search terms.

## Requirements Cross-Reference

SEA-001, SEA-007, SEA-008, SEA-009, SEA-010, SEA-011

# Conduct Advanced Search

## Description

The primary objective of this use case is to describe the process of
conducting an advanced search of usda.gov. Actors are able to perform
the search by entering search criteria in the advanced search form.

## Actors

All users

## Pre-Conditions

The actor has navigated to the usda.gov home page or any page on the
site.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor navigates to    | 2.  The system displays a page which |
|     the advanced search form. |     allows the actor to search using |
|                               |     one or more of the following     |
|                               |     pre-defined criteria:            |
|                               |                                      |
|                               | > \- Title                           |
|                               | >                                    |
|                               | > \- Subject                         |
|                               | >                                    |
|                               | > \- Publication date range          |
|                               | >                                    |
|                               | > \- File format (doc, .xls, .ppt,   |
|                               | > .pdf, .html, .txt)                 |
|                               | >                                    |
|                               | > \- Document / publication author   |
|                               | >                                    |
|                               | > \- Agency affiliation              |
|                               | >                                    |
|                               | > \- Keyword                         |
|                               | >                                    |
|                               | > \- Category                        |
|                               | >                                    |
|                               | > \- USDA program / service          |
|                               | >                                    |
|                               | > \- Relevant legislation / bill     |
|                               | > number                             |
|                               | >                                    |
|                               | > \- Language (multi-lingual)        |
|                               | >                                    |
|                               | > \- Number of results returned      |
|                               | >                                    |
|                               | > \- Sort order                      |
+-------------------------------+--------------------------------------+
| 3.  The actor submits the     | 4.  The system performs an advanced  |
|     search form.              |     search using the specified       |
|                               |     search criteria. A result set of |
|                               |     information matching the search  |
|                               |     request is returned to the       |
|                               |     actor. A defined number of       |
|                               |     result abstracts appear per page |
|                               |     and the search term is           |
|                               |     highlighted in each. The result  |
|                               |     set includes:                    |
|                               |                                      |
|                               | > -Title                             |
|                               | >                                    |
|                               | > -Subject                           |
|                               | >                                    |
|                               | > -Short abstract                    |
|                               | >                                    |
|                               | > -Publication date                  |
|                               | >                                    |
|                               | > -File format                       |
|                               | >                                    |
|                               | > -Document / publication author (if |
|                               | > available)                         |
|                               | >                                    |
|                               | > -Agency affiliation (if available) |
+-------------------------------+--------------------------------------+
| 5.  The actor chooses to view | 6.  The system retrieves the         |
|     a specific search result  |     selected search result and       |
|     based on the abstract and |     displays the content to the      |
|     data returned in the      |     actor.                           |
|     result set.               |                                      |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### Refined Search Criteria

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Conduct Advanced | 2.  The system displays the search   |
|     Search use case, Typical  |     form with the actor's previously |
|     Flow step 4, the actor    |     specified search criteria. The   |
|     chooses to refine the     |     actor continues from Typical     |
|     search criteria. The      |     Flow step 3.                     |
|     actor navigates to the    |                                      |
|     previous page.            |                                      |
+-------------------------------+--------------------------------------+

####  {#section-12 .unnumbered}

#### Cancel Search

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Conduct Advanced | 2.  The search operation is          |
|     Search use case, Typical  |     cancelled and the use case ends. |
|     Flow step 3, the actor    |                                      |
|     chooses to cancel the     |                                      |
|     search operation.         |                                      |
+-------------------------------+--------------------------------------+

###  {#section-13 .unnumbered}

#### No Search Results

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Conduct Advanced | 2.  No results match the keyword     |
|     Search Typical Flow step  |     search criteria. The search      |
|     3, the actor conducts an  |     mechanism offers alternative     |
|     advanced search by        |     search terms of related keyword  |
|     filling out the search    |     topics and spelling suggestions. |
|     criteria.                 |                                      |
+-------------------------------+--------------------------------------+
| 3.  The actor performs        | 4.  The system performs the search   |
|     another advanced search   |     and the use case continues from  |
|     using one of the          |     Typical Flow step 4.             |
|     suggested search terms.   |                                      |
+-------------------------------+--------------------------------------+

### Exception Flow

#### No Search Results, No Search Suggestions

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Conduct Simple   | 2.  No results match the keyword     |
|     Search use case Typical   |     search criteria, and no          |
|     Flow step 1, the actor    |     alternative search term          |
|     conducts a simple search  |     suggestions are available in the |
|     using a keyword.          |     system. A message is displayed   |
|                               |     prompting the user to perform    |
|                               |     another search using different   |
|                               |     search criteria. This page also  |
|                               |     lists search tips.               |
+-------------------------------+--------------------------------------+
| 3.  The actor performs        | 4.  The system performs the search   |
|     another simple search     |     and the use case continues from  |
|     choosing another search   |     Typical Flow step 2.             |
|     term.                     |                                      |
+-------------------------------+--------------------------------------+

## Post Conditions

In successful execution of the use case, relevant search results are
displayed to the actor. Otherwise, the actor may modify his or her
search criteria.

## Requirements Cross-Reference

SEA-001, SEA-002, SEA-003, SEA-004, SEA-005, SEA-006, SEA-007, SEA-008,
SEA-009, SEA-010, SEA-011

# View Frequently Asked Questions

## Description

The primary objective of this use case is to describe the process of
viewing a static list of Frequently Asked Questions from the usda.gov
portal. This list can be organized by topic (default) or by agency.

## Actors

All users

## Pre-Conditions

The actor has entered navigated to the usda.gov home page or any page on
the site.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor navigates to    | 2.  The system displays a list of    |
|     the list of Frequently    |     FAQs, organized alphabetically   |
|     Asked Questions (FAQs).   |     by topic.                        |
+-------------------------------+--------------------------------------+
| 3.  The user selects an FAQ   | 4.  The FAQ detail is displayed.     |
|     by clicking on the        |                                      |
|     hyperlink.                |                                      |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### FAQs by Agency

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the View Frequently  | 2.  The system displays a list of    |
|     Asked Questions use case, |     FAQs, organized alphabetically   |
|     Typical Flow step 2, the  |     by agency.                       |
|     actor chooses to view     |                                      |
|     FAQs sorted by agency.    |                                      |
+-------------------------------+--------------------------------------+

####  {#section-14 .unnumbered}

#### Unlisted FAQs

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor's desired       | 2.  The system loads the online      |
|     question is not detailed  |     feedback form. See section       |
|     under the "FAQs" section. |     14.4.1.                          |
|     The actor chooses to      |                                      |
|     submit feedback to        |                                      |
|     usda.gov and selects the  |                                      |
|     "Contact Us" hyperlink.   |                                      |
+-------------------------------+--------------------------------------+

## Post Conditions

In successful execution of the use case, the Frequently Asked Questions
list is displayed to the actor, and is sorted by either topic or agency.
Otherwise, the actor may need to contact the USDA or submit his or her
question to "Ask the Expert" in order to find a resolution.

## Requirements Cross-Reference

HLP-001

# View Help

## Description

The primary objective of this use case is to describe the process of
viewing help available to help actors in navigating through usda.gov
functionality. This guide is accessible from any page in the usda.gov
portal. Actors will also be able to view context sensitive help where
available.

## Actors

All users

## Pre-Conditions

The actor has entered the usda.gov home page or any page on the site.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor navigates to    | 2.  The system verifies whether      |
|     the help section.         |     context-sensitive help is        |
|                               |     available for the current page   |
|                               |     from the actor requested help.   |
|                               |     Where context-sensitive help is  |
|                               |     available, the appropriate help  |
|                               |     guide is displayed. Examples of  |
|                               |     context-sensitive help pages     |
|                               |     include:                         |
|                               |                                      |
|                               | > \- Forms (e.g., Feedback form)     |
|                               | >                                    |
|                               | > \- Portal Customization            |
|                               | >                                    |
|                               | > \- Advanced Search                 |
+-------------------------------+--------------------------------------+
| 3.  The actor views displayed | 4.  The use case ends.               |
|     help pages.               |                                      |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### Static User Guide 

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the View Help use    | 2.  The system displays the static   |
|     case, Typical Flow step   |     help guide.                      |
|     2, the actor chooses to   |                                      |
|     view the static user      |                                      |
|     guide by selecting the    |                                      |
|     corresponding option on   |                                      |
|     the context-sensitive     |                                      |
|     help page.                |                                      |
+-------------------------------+--------------------------------------+
| 5.  The actor views displayed | 6.  The use case ends.               |
|     help pages.               |                                      |
+-------------------------------+--------------------------------------+

#### Unavailable Contextual Help

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the View Help use    | 2.  The system displays the static   |
|     case, Typical Flow step   |     help guide.                      |
|     2, no context-sensitive   |                                      |
|     help is available for the |                                      |
|     current page.             |                                      |
+-------------------------------+--------------------------------------+

####  {#section-15 .unnumbered}

#### Unlisted Help Topic

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor's desired help  | 2.  The system loads the online      |
|     topic is not detailed     |     feedback form. See section       |
|     under the hyperlink. The  |     14.4.1.                          |
|     actor chooses to request  |                                      |
|     help from usda.gov and    |                                      |
|     selects the "Contact Us"  |                                      |
|     hyperlink from the page   |                                      |
|     header.                   |                                      |
+-------------------------------+--------------------------------------+

## Post Conditions

In successful execution of the use case, help topics are displayed to
the actor, which guide the actor through portal functionality.
Otherwise, the actor may need to contact the USDA, or submit his or her
help request to "Ask the Expert" in order to find a resolution.

## Requirements Cross-Reference

HLP-007, HLP-008

# Subscribe/Unsubscribe to Email Notifications

## Description

The primary objective of this use case is to describe the process of
subscribing to periodic topic of interest email notifications. Actors
are able to receive information and updates on pre-selected newsletter
topics.

## Actors

All users

## Pre-Conditions

The actor wishes to subscribe/unsubscribe to USDA email newsletters and
accesses the subscription page, profile settings or a newsletter, which
was sent to his or her email address.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor navigates to    | 2.  The system loads a form allowing |
|     the subscription services |     the actor to choose the specific |
|     section of the usda.gov   |     areas of interest about which    |
|     portal.                   |     they desire email notifications. |
|                               |     Form fields include:             |
|                               |                                      |
|                               | > \- Email address                   |
|                               | >                                    |
|                               | > \- Areas of interest / Newsletter  |
|                               | > types                              |
+-------------------------------+--------------------------------------+
| 3.  The actor completes and   | 4.  The system validates the         |
|     submits the subscription  |     information, displays a          |
|     request form.             |     verification page to the actor.  |
+-------------------------------+--------------------------------------+
| 5.  The actor confirms the    | 6.  The system displays a            |
|     verification page.        |     confirmation page to the user. A |
|                               |     system generated confirmation    |
|                               |     email is sent to his or her      |
|                               |     email inbox. This email confirms |
|                               |     that the actor has intentionally |
|                               |     registered for this service.     |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### Cancel Subscription Request

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Subscribe to     | 2.  The operation is cancelled and   |
|     Email Notifications use   |     the use case ends.               |
|     case, Typical Flow step   |                                      |
|     3, the actor chooses to   |                                      |
|     cancel the subscription   |                                      |
|     request.                  |                                      |
+-------------------------------+--------------------------------------+

#### Unsubscribe to Newsletter from Email

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Subscribe to     | 2.  The system displays a newsletter |
|     Email Notifications use   |     cancellation page prompting the  |
|     case, Typical Flow step   |     user to enter his or her email   |
|     4, the actor follows the  |     address.                         |
|     subscription cancellation |                                      |
|     instructions at the       |                                      |
|     bottom of the             |                                      |
|     confirmation email. The   |                                      |
|     actor accesses a cancel   |                                      |
|     newsletter subscription   |                                      |
|     page.                     |                                      |
+-------------------------------+--------------------------------------+
| 3.  The actor enters his or   | 4.  The system displays the actor's  |
|     her email address.        |     newsletter subscription options  |
|                               |     based on the email address       |
|                               |     entered.                         |
+-------------------------------+--------------------------------------+
| 5.  The actor chooses to      | 6.  The system stores the actor's    |
|     unsubscribe from one or   |     preferences and removes the      |
|     more email newsletters.   |     actor from the newsletter        |
|                               |     subscription list.               |
+-------------------------------+--------------------------------------+

#### Unsubscribe to Newsletter from usda.gov portal

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor navigates to    | 2.  The system displays a newsletter |
|     the newsletter            |     cancellation page and continues  |
|     subscription page and     |     from the Unsubscribe to          |
|     accesses the cancellation |     Newsletter from Email, Alternate |
|     option on that page.      |     Flow steps 2 to 6.               |
+-------------------------------+--------------------------------------+

### Exception Flow

#### Invalid Subscription Data

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Subscribe to     | 2.  The system validates the         |
|     Email Notifications use   |     information, determines that the |
|     case, Typical Flow step   |     information entered was invalid  |
|     3, the actor submits the  |     and prompts the actor to correct |
|     subscription form.        |     the information. The use case    |
|                               |     continues from Typical Flow step |
|                               |     3.                               |
+-------------------------------+--------------------------------------+

## Post Conditions

In successful execution of the use case, the actor has intentionally
registered to receive email newsletter notifications about USDA
information.

## Requirements Cross-Reference

COM-004, COM-005, COM-006

# Contact Us

## Description

The primary objective of this use case is to describe the process of
submitting questions and feedback to usda.gov via an online form.

## Actors

All users

## Pre-Conditions

The actor has navigated to the usda.gov home page or any page on the
site.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor navigates to    | 2.  The online feedback form         |
|     the online feedback form. |     requests the following           |
|                               |     information:                     |
|                               |                                      |
|                               | > \- Email address                   |
|                               | >                                    |
|                               | > \- Geographic Location (State,     |
|                               | > County)                            |
|                               | >                                    |
|                               | > \- Reason for submitting feedback  |
|                               | >                                    |
|                               | > \- Feedback message                |
|                               | >                                    |
|                               | > The online feedback form includes  |
|                               | > content to inform actors that they |
|                               | > are not required to provide        |
|                               | > personal contact information to    |
|                               | > USDA. Should they desire a         |
|                               | > response, an email address must be |
|                               | > supplied.                          |
+-------------------------------+--------------------------------------+
| 3.  The actor completes and   | 4.  The system validates the         |
|     submits the feedback      |     information and displays a       |
|     form.                     |     verification page prompting the  |
|                               |     actor to edit his or her         |
|                               |     feedback or continue.            |
+-------------------------------+--------------------------------------+
| 5.  The actor chooses to      | 6.  The system submits feedback to   |
|     continue with the submit  |     the appropriate USDA contact and |
|     feedback process.         |     displays a confirmation page to  |
|                               |     the actor.                       |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### Edit Feedback

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Contact Us use   | 2.  The actor continues from the     |
|     case, Typical Flow step   |     Contact Us use case, Typical     |
|     4, the actor chooses to   |     flow step 3.                     |
|     edit his or her feedback  |                                      |
|     form.                     |                                      |
+-------------------------------+--------------------------------------+

#### Cancel Feedback Submission

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Contact Us use   | 2.  The operation is cancelled and   |
|     case, Typical Flow steps  |     the use case ends. The user is   |
|     3 or 5, the actor chooses |     returned to the current page.    |
|     to cancel the feedback    |                                      |
|     submission.               |                                      |
+-------------------------------+--------------------------------------+

### Exception Flow

#### Incomplete Form

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Contact Us use   | 2.  The actor is alerted that        |
|     case, Typical Flow step   |     required fields are not          |
|     4, the actor has omitted  |     completed correctly and the      |
|     or incorrectly completed  |     actor continues from Typical     |
|     required form fields.     |     Flow step 3.                     |
+-------------------------------+--------------------------------------+

## Post Conditions

In the successful execution of the use case, the actor submits feedback
to usda.gov and receives confirmation that the message has been sent.
The appropriate USDA party will respond to the actor query according to
the defined workflow process.

## Requirements Cross-Reference

GEN-003, GEN-004, HLP-002, HLP-004, HLP-005

# Ask the Expert

## Description

The primary objective of this use case is to describe the process of
submitting questions to the "Ask the Expert" section of usda.gov. An
appropriate USDA party will respond to the actor query according to the
defined workflow process.

## Actors

All users

## Pre-Conditions

The actor has entered usda.gov in the address bar of an active browser
window.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor navigates to    | 2.  The system displays the "Ask the |
|     the "Ask the Expert"      |     Expert" form allowing actors to  |
|     page.                     |     submit questions to subject      |
|                               |     matter experts for his or her    |
|                               |     review. Form fields include:     |
|                               |                                      |
|                               | > \- Email address                   |
|                               | >                                    |
|                               | > \- Geographic Location (State,     |
|                               | > County)                            |
|                               | >                                    |
|                               | > \- Audience Type                   |
|                               | >                                    |
|                               | > \- Area of Interest                |
|                               | >                                    |
|                               | > \- Question for the subject matter |
|                               | > expert                             |
+-------------------------------+--------------------------------------+
| 3.  The actor completes and   | 4.  The system validates the         |
|     submits the "Ask and      |     information and displays a       |
|     Expert" form.             |     verification page prompting the  |
|                               |     actor to edit the form or        |
|                               |     continue.                        |
+-------------------------------+--------------------------------------+
| 5.  The actor chooses to      | 6.  The system submits the actor's   |
|     continue with the "Ask    |     question to the appropriate USDA |
|     the Expert" process.      |     contact and displays a           |
|                               |     confirmation page to the actor.  |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### Edit Form

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Ask the Expert   | 2.  The system validates the         |
|     use case, Typical Flow    |     information and the use case     |
|     step 4, the actor chooses |     continues from Typical Flow step |
|     to edit and resubmit the  |     4.                               |
|     question form.            |                                      |
+-------------------------------+--------------------------------------+

#### Cancel Question Submission

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Ask the Expert   | 2.  The operation is cancelled and   |
|     use case, Typical Flow    |     the use case ends. The user      |
|     steps 3 or 5, the actor   |     continues from the current page. |
|     chooses to cancel the     |                                      |
|     question submission.      |                                      |
+-------------------------------+--------------------------------------+

### Exception Flow

#### Incomplete Form

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Ask the Expert   | 2.  The actor is alerted that        |
|     use case, Typical Flow    |     required fields are not          |
|     step 3, the actor submits |     completed correctly and the      |
|     the question form.        |     actor continues from Typical     |
|                               |     Flow step 3.                     |
+-------------------------------+--------------------------------------+

##  {#section-16 .unnumbered}

## Post Conditions

In successful execution of the use case, the actor is able to submit a
question to an USDA employee subject matter expert for review. The actor
receives confirmation that the message has been sent. The appropriate
USDA party will respond to the actor query according to the defined
workflow process.

## Requirements Cross-Reference

COM-001

# Terminate User Session

## Description

The primary objective of this use case is to allow the actor to logout
of the portal and terminate his or her secure session.

## Actors

Registered Users

## Pre-Conditions

The actor is logged in.

## Flow

### Typical Flow

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor selects to      | 2.  The system ends the actor's      |
|     logout of the system.     |     session and a logout page is     |
|                               |     displayed with the option for    |
|                               |     the actor to re-login.           |
+-------------------------------+--------------------------------------+

### Alternate Flow

#### Close Browser

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor logs out of the | 2.  The system ends the actor's      |
|     system using the          |     session.                         |
|     browser's Close action    |                                      |
|     button.                   |                                      |
+-------------------------------+--------------------------------------+

#### Session Timeout Due to Inactivity

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  The actor remains         | 2.  The actor is alerted that his or |
|     inactive in the system    |     her session will timeout due to  |
|     for 15 consecutive        |     inactivity. The actor is given   |
|     minutes.                  |     the option to continue the       |
|                               |     session.                         |
+-------------------------------+--------------------------------------+
| 3.  The actor remains         | 4.  The system ends the actor's      |
|     inactive for another 15   |     session. A logout page is        |
|     consecutive minutes.      |     displayed with the option for    |
|                               |     the user to re-login to usda.gov |
+-------------------------------+--------------------------------------+

#### Continue Session

+-------------------------------+--------------------------------------+
| **[Actor                      | **[System Response]{.smallcaps}**    |
| Actions]{.smallcaps}**        |                                      |
+===============================+======================================+
| 1.  From the Terminate User   | 2.  The actor is returned to the     |
|     Session use case, Session |     current page view and the        |
|     Timeout Due to Inactivity |     session is not timed out.        |
|     Alternate Flow step 2,    |                                      |
|     the actor requests more   |                                      |
|     time to complete tasks in |                                      |
|     usda.gov.                 |                                      |
+-------------------------------+--------------------------------------+

## Post Conditions

In successful execution of the use case, the actor is logged out the
system. Otherwise, the system's state is unchanged and the actor may
navigate to other personalized areas of the site.

## Requirements Cross-Reference

SEC-004, SEC-005, TRK-005, TRK-006