OOI User Experience Vision, Strategy, Progress and Plans · 2011-05-16 · OOI Annual Review May 16-20 2011 • Characterized by • Observational user research and ﬁeld interviews

OCEAN OBSERVATORIES INITIATIVE

OOI Annual ReviewMay 16-20 2011

OOI User ExperienceVision, Strategy, Progress and Plans

Annual ReviewWoods Hole MA, 16 May 2011

1


Overview

• Vision for the OOI user experience

• Strategy and process for delivering the vision

• R1 progress

• R2 engagement plans

2


OOI User Experience Vision

wherever they are,

whenever they want,

OOI users roam the living ocean,

creating an ever-evolving world of scientific

discovery, learning and exchange

3


whereever they are

The OOI is designed to be used and useful in users’ normal

working contexts

from a university office to a ship at sea to a high school soccer

field

The OOI can be accessed with users’ normal tools

from a laptop to a smartphone to a mainframe

4


whenever they want

The OOI is designed to be immediately useful and usable

from first release to last

The OOI provides interactive access to

real-time data, real-time instrument and observatory control, and

real-time data analysis tools

The OOI is always open

every day, all day, all night

5


OOI users roam the living ocean

The OOI is about ocean science

from controlling an instrument to surfing the science,

OOI tools are transparent

The OOI lets users work and play with non-OOI tools

on their computer, on the OOI network, on the internet

6


creating an ever-evolving world of scientific

The OOI is developed by, with and for science communities

user-driven evolution from conception to decommision

OOI tools are trusted, reliable and replaceable

flexible, extensible, customizable framework for new tools and ideas

7


discovery, learning and exchange

The OOI is supports ready exchange of ideas, tools and results

from novel teaching plans to dynamic modeling to breakthrough

analysis

The OOI lets users work and play with each other

whatever their age, whatever their interests

Learning is at the heart of science

and the OOI user experience

8


User Experience Iterative Design Process

• Applying principles, methods and techniques of user-centered design, we

work with prospective users and stakeholders to

• Identify and verify assumptions about users and the worlds in which they

live and work

• Define and validate user interface

requirements

• Create user interface designs

• Test user interface designs and

functioning systems to

ensure they meet user needs

Problem Analysis

Design Generation

Design Realization

Design Evaluation

9


• Characterized by

• Observational user research and field interviews

• Conceptual design

• Diagrammatic representations

• Idea prototyping

User Experience in the Inception Phase

Problem Analysis

Design Generation

Design Realization

Design Evaluation

Identify user needsDefine user interface requirements

Map and prioritize targetedusers, tasks, contexts, tools, and partners

Articulate workflows Design interaction architectureDesign information architecture

Design view flowsPrototype designs for critical interactions

Baseline released productVerify needs and requirements

Validate design assumptions

10



• Artifact-driven scenario-based interviews and user testing

• Participatory design

• Graphical representations

• Functional specification

User Experience in the Elaboration Phase

Problem Analysis

Design Generation

Design Realization

Design Evaluation

Map user needs, requirements and characteristics toscreen and interaction designs

Detailed screen and interaction designsFunctional specification

Computational infrastructureHeuristic usability testing of proposed designs

11



• Design-driven hands-on testing

• Machine-readable representations

• Production assets

User Experience in the Construction Phase

Problem Analysis

Design Generation

Design Realization

Design Evaluation

Identify design flaws

Graphical asset productionUser help and documentation

Computational implementationFormal usability testing

12



• Field-based observation

• Critical error correction

User Experience in the Transition Phase

Problem Analysis

Design Generation

Design Realization

Design Evaluation

Identify critical usability flaws

Corrective measuresPilot studies

13


Structuring User and Stakeholder Engagement

• UX Steering Committees provide input, feedback and direction from

internal experts and stakeholders

• Release- and theme-specific (e.g., Marine Networks, Scientific

Uses)

• Subject-matter experts drawn from OOI project members and, if

appropriate, select external experts

• Individual members may serve as participatory design partners

• Review meeting at least once every iteration

• Early Adopters provide input and feedback from external users

• Interest-specific (e.g., dynamic visualization tool integration)

14


Crowdsourcing Broader Engagement

• Get community contributions early and often

• On-line discussion forum and FAQ

• Run by OOI/CI Communications teams

• Design-a-thons

• 1-2 workshop-like events with user experience experts,

expert users, developers, et al.

• Provide Grand Challenge, see what participants produce

• CIUX in collaboration with other CI subsystems, and other

IOs

15


R1 Progress

Context Area Focus AreaDetail Area

All elements modular and replaceable

16


• Flexible and extensible visual and interaction architecture

created, documented in• DCN 2130-00005 OOI-CI ION R1.0 Functional Design Specification

• Release 1 Data Distribution Network interface designed,

documented in• DCN 2130-00006 OOI-CI ION R1.0 Functional

Detail Specification (CIUX Assets Database)

• R1_workflows.GRAFFLE

• R1_screens.pptx

• R1_panels.ai

UI Design

• 10 workflows

• 24 screens

• 72 panels

• 21 graphical items

• 8 icons

17


R1.0 Coverage - Designed and Implemented

• Interaction and visual architecture

• Enabling users to

• Browse ION data resources

• Search for data resources by geographic location, and temporal or vertical extent

(textual input)

• View metadata and provenance associated with a particular data resource

• Download data

• Request to receive notifications about changes to data resources (email

notifications only)

• Register a new data source with the ION (CF-compliant sources only)

• Create and manage an ION user account

• Limited system administration support

18


R1.X Coverage - Design

• Visual search input (map- and slider-based)

• Paradigm for multiple-view/multiple-representation management

• Additional detailed views of single data resource

• Static visualization display

• Data resource summary

• Data variables list view

• Data variables value distribution (histogram) view

• Data variables times series view

• Recursive drill-down interaction for increasing levels of detail

• Preview paradigm, e.g., for download, notifications

• History and favorites mechanisms

19


UX User Engagement Year 2

• User research (field)

• IMCS Rutgers University (Jul 2010)

• Scripps Institute of Oceanography (Aug 2010)

• R/V New Horizons cruise (Dec 2010)

• User research (community events)

• OOI Tempe Science Community meeting (Apr 2010)

• OOI Technical and Programmatic Meeting (Sep 2010)

• AGU 2010 (Dec 2010)

• R1 Early Adopter contacts

• Rutgers Ocean Modeling Group, Rutgers University

• Powell Lab, University of Hawaii

• Usability testing

• IMCS Rutgers University (Apr 2011)

• 69 individual interviews

• 4 group interviews

• 60+ gB of audiovisual

data collected

20


Early User Testing

• (Quotes and picture from 2011_0422_019)

21


CI Release 1: Data Distribution Network

• Provide framework for discovery and interaction based on

data-intensive users’ needs

CI Release 2: Managed Instrument Network

• Provide support for operations and maintenance of marine

networks based on RSN and CGSN needs

CI Release 3: On Demand Measurement Processing

• Provide dynamic analysis and visualization tools based on

science communities’ user needs

CI Release 4: Interactive Ocean Observatory

• Provide mission control and collaboration support based

on science communities’ needs

R2 Engagement Plans

S c i e n t i f i c C o l l a b o r a t i o n

G e n e r a l S c i e n c e U s e r s

S c i e n c e E x p e r t s

R e s o u rc e P ro v i d e r s

22


R1 Lessons

• Need earlier and more user research

• Must leverage limited design resources through

participatory design and crowd-sourcing

• Need interactive prototype to be living testbed and

communication tool

23


R2: Earlier and More Focus on Engagement• May 2011 form Release 2 UX Steering Committees

• (Planning in collaboration with program managers and project scientists)

• Managed Instrument Network (CG and RSN, O&M and project scientists)

• CI Infrastructure and Network Management (CI, O&M)

• Enhanced Data Interaction and Visualization & Early Prototyping (OOI, project scientists)

• May 2011 recruit Early Adopters

• Enhanced Data Interaction and Visualization & Early Prototyping

• Jun-Jul 2011 ethnographic site visits and user-focused workshops

• (Planning in collaboration with program managers, project scientists, EPE liaisons)

• RSN: UW, Pacific City shore station

• CGSN: OSU, WHOII

• Jul-Aug 2011 technology-focused workshops

• Jul-Nov 2011 participatory design

• OOI project scientists and UX steering committee members

• UX Steering Committee reviews

• Jun 2011 requirements from DOORS

• Jul 2011 feature requirements

• Aug 2011 design assumptions and requirements

• Aug - Nov 2011 detailed screen designs

24


CI Engagement Collaborations

• CIUX - other CI subsystems

• User interface and interaction requirements

• User-focused workshops

• CI - EPE

• Leveraging user research

• Leveraging design ideas and efforts

• Developing crowdsourcing opportunities

• CI - RSN/CGSN

• Steering committee members

• Participatory design partners

• CI - the world

• Crowdsourcing needs, ideas, tools

• Solicit feedback and suggestions

25

Documents

OOI User Experience Vision, Strategy, Progress and Plans · 2011-05-16 · OOI Annual Review May 16-20 2011 • Characterized by • Observational user research and ﬁeld interviews