Skip to content

Design User Flow

License and Copyright Notice

By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).

Pre-checklist

  • I have searched for, and did not find, an existing issue at the top-level.

Stories

Story 1: As a student I want swipe my card so that I can checkout.

Story 2: As an employee, I want sign in so that I can enter food taken by student and approve checkout.

Ready checklist

  • Independent (of other issues in flow)
  • Negotiable (and negotiated)
  • Valuable (the value to an identified role has been identified)
  • Estimable (the size of this story has been estimated using /weight value or the menu on the right)
  • Small (can be completed in 50% or less of a single iteration)
  • Testable (has testable acceptance criteria)

Also

  • Appropriate role labels have been applied (e.g., role:*).
  • Relevant activity labels have been applied (e.g., activity:*).
  • Linked to related issues, epics, and milestones.

Diagrams

This is the file that contains the wireframe as well as the planned animations but you will need Adobe xD to view it. Thea_s_Pantry_v3.xd

Revision 2

The new user flow is as follows:

landing_page

landing_page_add_guest_button

add_user_active

landing_page_select_guest

landing_page_add_weight_button

add_weight_active

add_weight_active_instructions

Acceptance Criteria

Scenario: A student is signing in to take food
  Given a sign in page
  When a student swipes their card
  Then another student should still be able to sign in thereafter.
Scenario: An employee is signing in to approve changes
  Given a sign in page
  When a user name and password are entered
  Then options become available to approve transactions

Template Version 2.0.0

Edited by Brandon