Use Case

This is the latest iteration of an ever-evolving use case scenario for our device. While this scenario represents one of the primary ways in which we expect people to use the device, we recognize that people will not necessarily follow this recipe step-by-step. However, thinking thru the process informs our design and helps us clearly define hardware and software requirements and capabilities.

  • need to be alerted that the building is equipped
    • phone must be constantly scanning
    • need a header for protocol to alert the device that this tag is part of our system
    • tags at entrances can be smarter
      • need URL to download map and other data like a hash of the datapack, and date of last update
    • need Internet connection
    • what if we were on the phone?
      • subtle call-waiting-like beep
    • if not on the phone, do a regular cell-phone configurable event
  • determine if phone has latest data for the building
    • make this s/w configurable
      • like MS update, do it in batch mode later rather than requesting permission to go online everytime user enters a building
    • how do we determine the building uniquely?
      • hash
      • URL
      • GUID of smart tag
      • some unique name for the building??? (namespace?)
    • need to deal with multiple entrances to the same building
  • ask user if we should download new data if necessary
    • voice and screen
    • "You have entered a smart building."
      • "You do not have a map for this building."
      • "Would you like to download the map?"
      • pause "Please say yes or no."
      • feedback on d/l process
    • if user says no, remember the building and give a smaller alert the next time (so the user doesn't forget that this building is instrumented)
  • menu system starts
    • gives information on the building
      • building name
      • which entrance
      • what floor
      • "You are in NSH near the north entrance, 3rd floor."
    • asks user to select type of destination from high-level categories
      • room
        • "Please state the room number or name"
      • find a person
        • "Please spell the last name of the person you would like to find."
      • washroom
      • elevator
      • stairs
      • cafeteria
      • other domain-specific categories
        • ticket counter
        • gate
        • security
        • transportation
        • front desk
      • "Please state your destination, or select from the following menu..." then read the categories
        • categorical sub-menus repeat the name of the category, then give a list starting with "closest"
    • response by voice or button
    • give more specific information
      • speak room number
      • spell person's last name
  • repeat destination to confirmation
  • gives directions
    • options for stairs or elevators???
      • global preferences to always take elevator/wheelchair ramp?
    • alternate route
      • e.g. elevator out of order
      • don't deal with this yet
  • we're still lost in terms of RFID tags
    • range: can we see them from across the hallway?
    • price / range
    • how do we make the map?
    • how does the person deploying these tags get the URL into them
      • even better, we can sell tags with known object ID portion of the GUID that lets the device know that it is at the entrance to an instrumented building
  • alert the user when destination tag is found
    • due to possible overlap in coverage, we should also tell the user which door to look for when they enter a hallway (e.g. 3rd door on right)