5. User stories & requirements

User Stories and Requirements

User Stories

These are the user stories we generated using the traveler personas’ needs and protections, and using the four frames outlined in the previous section.

(As the transportation system evolves, user stories may change, as might the degree to which user needs are satisfied. SDOT should continue to reevaluate these stories against the current technologies and the state of the system.)

AS A TRAVELER USING THE TRANSPORTATION SYSTEM, I NEED TO KNOW …

A.    Information imperatives

ACCELERATE DECARBONIZATION

…how much carbon a travel option (or a delivery) will generate or save

ADVANCE EQUITY
…that I am not being discriminated against because of my age, race, gender identity, sexual orientation, disability, ethnicity, nationality, or religion; and
…that the information is available to me in ways that don’t require a personal smartphone or an internet account

PROTECT PRIVACY
…that my private information, my travel patterns and my location data will not be used for profit or resold without my express consent; and
…that the data or information I generate or is generated about me is not used for surveillance purposes without legal authorization

LEVEL THE PLAYING FIELD
…all the transportation options and services available to me at each stage of the journey; and
…the comparative costs (in $) of the travel option or delivery service I am using or will use

 

B.    Location and navigation information

…the best or recommended route to my destination (this includes the conditions of the physical infrastructure along the route)

…the exact location of transportation options (stations, parking locations, etc.) relative to my location

…how to connect to another travel mode if I need to.

…the locations of parking spaces, load zones, boarding and hailing zones, stations, and where to wait for a vehicle

C.    Notification and status information

…the current state of sidewalks, roads, routes, and schedules

  • This should include current traffic, wait times and passenger volumes
  • This information must be accurate and dependable

…if there are sidewalk and road closures, changes in schedules or routes that will affect my trip

…how many parking slots are available (car, bike or scooter, etc.)

…If there are areas or routes where the mode or vehicle I am taking is prioritized or is not allowed

D.    Reporting and safety information

…who is operating the vehicle (if it’s not me) and that I can trust them, and if it is run by a human or by AI

…how to (and be able to) report conditions that affect my trip

…how to (and be able to) request for help for emergencies

D.    Payment information

…how to pay for my trip if there are any fees, fares or tolls required (and how I will be refunded for failures in service)

…if there are incentives or restrictions,

…that there are other ways to pay for fares or fees if I don’t have a credit card, a smartphone or internet access

Requirements for Actors

Based on the user needs enumerated above, we generated a list of information needs for the actors in the ecosystem. We set out three categories of actor: 1) emergency responders; 2) information and mobility service providers; and, 3) SDOT.

(We used the requirements for SDOT to include requirements from other government agencies.)

The information needs of the actors are listed below.

Emergency responders

As an Emergency Responder, I need …

….a way to receive emergency requests with location information

…to know the current state of roads, routes, and schedules

  • This information must be accurate and dependable

…to know the best possible or prioritized route to the incident and to hospitals This information must be accurate and dependable

…a way to inform others of our estimated time of arrival to an incident

…to know if there are road closures, changes in schedules or routes that will affect the emergency response

…to know what other services are responding …a way to inform other responders of the status of the emergency

…a way to inform traffic managers of the status of the emergency

…a way to warn other travelers to avoid the area where there is an emergency response

…a way to record the status and conditions of the emergency and the response

…a way to inform traffic managers of what route I am going to take so they can prioritize that route

…a way to digitally inform the traffic managers in real-time that emergency services are closing a road segment, sidewalk or loading zone for incident response

 

Information or mobility service providers

As an Information or Mobility Service Provider, I need … 

…the most current infrastructure maps and plans

…to know the current and future state of roads, routes, and schedules, including current traffic and volumes

This information must be accurate and dependable

…real-time, validated information on traffic lights, speed limits, and other road or mobility rules

…to know if there are current or future road closures, changes in schedules or routes that will affect anyone who uses my service

…to know the locations of parking spaces, load zones, drone docks or parking, boarding and hailing zones, transit and bus stations, charging infrastructure, and wait zones

…to know the schedules of parking spaces, load zones, drone docks or parking, boarding and hailing zones, transit and bus stations, and where to wait for a vehicle or a rider

…accurate and verified information from traffic managers on current and historical transportation data

…accurate and verified information from transportation planners on future plans for transportation

…access to accurate and verified data from other information service operators and from mobility service operators

…the most current versions of relevant policies and rules

…the most current fee and fare schedules for my service and for other available services

…the rules for autonomous vehicles and drones

…to be notified of any changes in policies and rules

…to be notified of any changes in fee and fare schedules

…to be able to report conditions that affect the experience of my customers and my service

…to be able to request for help for emergencies

…to assure my customers/the users of my service that they can trust my service with their data

That I will not resell it without their express consent

That I will not use it for surveillance

…all the above information in open standard, usable data formats that don’t tie me down to any single software service or platform

 

Requirements for SDOT Functions

We identified seven functional roles in SDOT that are relevant to our ability to deliver information to the traveling public and to the other actors in the ecosystem. The functions are:

  • SDOT traffic managers[40] and traffic control planners are staff who manage the transportation network and respond to the conditions in real-time, hourly, daily, weekly or monthly
  • SDOT maintenance managers are staff who maintain the transportation infrastructure (including urban forestry) and respond hourly, daily, weekly or monthly to the conditions.
  • SDOT curb use and parking managers are staff who manage parking, load zones and other uses of the curb
  • SDOT transportation planners and mobility program managers are staff who manage mobility programs and plan the transportation infrastructure and services for the next three to five years or longer
  • SDOT project and construction managers are staff who design, manage and build transportation projects
  • SDOT street use managers are staff who permit and regulate activities on the right of way
  • SDOT asset owners are staff who are accountable for certain classes of physical assets (for example, sidewalks or bridges). This includes staff responsible for maintaining data about these assets.

To deliver the user needs enumerated above, we developed a list of information needs for each function. These needs also come in the form of user requirements.

For example, we might say:

As SDOT traffic managers, we need …

  • …near-term (next day and day after) scheduled road closures or road work on arterials

Or

  • …advance notice (30 minute to one hour) of emergency road maintenance work on arterials

This is a list of both current and aspirational needs. We are already collecting some or most of the requirements. There are requirements we may want to collect but our current technology or infrastructure does not yet allow us to do so.

The information needs for each function are listed in Appendix E.

Footnotes:

[40] We use “manager” as a function, not a title or role. For example, by “street use managers,” we don’t mean people with the title “manager” in our Street Use division. We mean SDOT staff who are charged with managing the permitted uses in the right of way.

Need More Information?

This is a draft plan. It was developed by Benjamin de la Pena, Mary Alyce Eugene, Alex Hagenah, and Sam Marshall along with their colleagues from across the Seattle Department of Transportation (SDOT).

If you have questions about this plan, please send us email via draft_tiip@seattle.gov.

If you have questions about SDOT, please visit our website at www.seattle.gov/transporation.

Designed by Story 2 Designs

Privacy Policy