User Stories
Ursula Undergrad
I am an undergrad student researching for a gen ed class. I want information on infectious respiratory illnesses for my research paper.
I want to easily find projections for the most common respiratory illnesses.
I want to quickly access overall data.
I want to ensure I am looking at the correct data for my research question.
Phillip PhD
I am an epidemiology PhD student with a vast understanding of infectious diseases. I want information on different illnesses for my research.
I want to quickly navigate between different respiratory illness forecasts without introductory explanations.
I want confidence that the forecasts are distinct from raw surveillance data, so I do not confuse projections with observed trends.
Helena Healthcare
I am a healthcare worker who monitors respiratory illness forecasts to anticipate patient volume and seasonal trends.
I want to easily identify forecasts for the most relevant respiratory illnesses so I can stay informed about upcoming surges.
I want a simple, reliable way to access overall respiratory forecasts without needing advanced research knowledge.
I want the navigation labels to be clear and intuitive, allowing me to quickly find the information I need during a busy workday.
Requirements
On a broader scale, the majority of our work on this project will be redefining how users can interact, visualize, and overall understand the data that is presented in the website. We are currently assuming a user background of academia researchers, but hope to also expand the data for intuitive public usage.
Functional
Definite: New UI must allow users to select and toggle multiple disease data layers and statistical views simultaneously
Definite: For every data view selected, we must display specific researchers or organizations that have compiled or are otherwise responsible for the data
Definite: The system must maintain the user’s selection state if they navigate between different sections of the modeling tool
Perhaps: Exportable citation button that generates properly formatted bibliographic entries for all the data views that are currently selected by the user
Improbable: Custom view settings to save collections of views for future sessions
Improbable: General Audience Lite mode that simplifies the terminology or technical jargon of the UI for non-professional users that don't have a good background in disease forecasting.
Non-Functional
Definite: The interface must prioritize a high information density suitable for disease modeling researchers while reducing click-depth for frequent actions.
Definite: The code must be compatible with the existing ACCIDDA repository structure and modularized enough to "hand off"
Definite: Development must be managed through a fork of the public ACCIDDA repository
Definite: The UI must not obscure the underlying disease model or map while the selection menu is open.
Perhaps: The selection interface should initialize and update in under 200ms to ensure no lag during research workflows.
Perhaps: Creating a new approach for disease modeling views which should be documented in the README to allow ACCIDDA engineers to add future custom views easily.
Improbable: High-contrast modes and full keyboard navigability for the "general audience" expansion.
Improbable: Responsive design for viewing models on tablet devices.
Interface
Definite: The new UI must match the existing styling (CSS/Framework) used in the current ACCIDDA tool.
Definite: Attribution links must be visually distinct but secondary to the primary selection controls to prevent clutter.
Definite: The team will interface with the client via Pull Requests on the public repository after acceptance of the design.
Perhaps: A one-time overlay explaining the new selection and attribution features to returning researchers.