Skip to content

Use Cases

Ceyhun edited this page Mar 8, 2017 · 13 revisions

USE CASES

Use Case 1: Creating a Heritage Item

  • Actors: Registered User
  • Purpose: Creating a cultural heritage item.
  • Pre-conditions:
    • User must be logged in.
  • Action Items:
    • Users clicks "Create Item" button.
    • Heritage item creation page is shown.
    • User types a title for the heritage item.
    • User types the relevant information on their respective areas.
    • User uploads the multimedia items if there are any.
    • User clicks "Save changes" button.
    • System takes the information and processes it.
  • Post-conditions:
    • The item is created.
    • If the process is successful, the user is directed to the item page.

Use Case 2: Guest Basic Search

  • Actors: Unregistered User
  • Purpose: Searching a query
  • Pre-conditions: None
  • Action Items:
    • Unregistered user opens the website.
    • Unregistered user types the query on search bar.
    • Unregistered user clicks Search button.
    • System returns with a result page.
  • Post-conditions:
    • If there is a result, it is shown in result page in a list.
    • When unregistered user wants to click to a result. Sign-up page appears and system tells guest that only registered users can open a result.

Use Case 3: Registered User Basic Search

  • Actors: Registered User
  • Purpose: Searching a query
  • Pre-conditions:
    • User must logged in to system.
  • Action Items:
    • User types the query on search bar.
    • User clicks Search button.
    • System returns with a result page.
  • Post-conditions:
    • If there is a result, it is shown in result page in a list.
    • When user clicks to a result he/she is directed to the page he/she wants.

Use Case 4: Sign up.

  • Actors: Unregistered User
  • Purpose: Signing up to system.
  • Pre-conditions:
    • User must be unregistered to system.
    • User's email address should not be in the database that keep registered users accounts.
    • User must give an e-mail address and password.
  • Action Items:
    • Users clicks "Sign Up" button.
    • Sign up page is shown.
    • User should fill the signing up form that includes name, surname, email, unique username and password spaces.
    • User clicks "Send" button after filling the sign-up form.
    • System takes the information and processes it.
    • An activation e-mail will be sent to the given e-mail address.
  • Post-conditions:
    • The account for this user will be created.
    • User should verify his account by clicking the confirmation link in the email, sent by system.
  • Constraints:
    • Given password must be at least 8 characters, at most 15 characters.

Use Case 5: Sign In.

  • Actors: Registered User
  • Purpose: Signing in to system.
  • Pre-conditions:
    • User must have a verified account.
  • Action Items:
    • User clicks "Sign In" button.
    • Sign in page is shown.
    • User should enter username/email and password.
    • User clicks "Log-in" button.
    • System takes the information and processes it.
  • Post-conditions:
    • User should sign in to system.
    • System should direct the user to the homepage.
Clone this wiki locally