Show Me: Automatic Presentation for Visual Analysis

Slides:

Advertisements

Similar presentations

Requirements gathering

Advertisements

© 2003 By Default! A Free sample background from Slide 1 A First Course in Database Management Jeanne Baugh Department of.

The Systems Analysis Toolkit

Evaluating Requirements. Outline Brief Review Stakeholder Review Requirements Analysis Summary Activity 1.

Evaluating Requirements

UI Standards & Tools Khushroo Shaikh.

Usability presented by the OSU Libraries’ u-team.

Evaluating Requirements

Multiscale Visualization Using Data Cubes Chris Stolte, Diane Tang, Pat Hanrahan Stanford University Information Visualization October 2002 Boston, MA.

Preece Chapter 7.7 & Mc Cracken Chapter 3

Evaluating Requirements

Task analysis 1 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis Preece et al Chapter 7.

1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.

Software Development, Programming, Testing & Implementation.

Rationalising Data Collection: Automated Data Collection from Enterprises Seminar on New Frontiers for Statistical Data Collection

Team Skill 1 Analyzing the Problem Business Modeling (6) 1.

User Interface Theory & Design

RUP Requirements RUP Artifacts and Deliverables

® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.

Determining System Requirements Classes 9,10. SDLC Project Identification & Selection Project Initiation & Planning Analysis ** Logical Design Physical.

As you read the assignments, make note of the type of writing you are required to complete, the sources you may need to describe and discuss in your writing,

1. Topics to be discussed Introduction Objectives Testing Life Cycle Verification Vs Validation Testing Methodology Testing Levels 2.

Year 11 Unit 2 – Controlled assessment (25%)

Chapter 8: Systems analysis and design

CSE323 การวิเคราะห์และออกแบบระบบ (Systems Analysis and Design) Lecture 03: Requirements Capture Requirements Analysis.

Software Testing The process of operating a system or component under specified conditions, observing and recording the results, and making an evaluation.

OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.

How to Know That What You Want Has Been Done- 1 Claire Lohr Member, SESC Management Board Chair IEEE 829 Working Group How to Know That.

Copyright (c) Cem Kaner. 1 Software Testing 1 CSE 3411 SWE 5411 Assignment #1 Replicate and Edit Bugs.

Software Construction Lecture 18 Software Testing.

1 Presentation Template: Instructor Comments u The following template presents a guideline for preparing a Six Sigma presentation. An effective presentation.

Introduction to Software Development. Systems Life Cycle Analysis  Collect and examine data  Analyze current system and data flow Design  Plan your.

1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.

Usability Engineering Dr. Dania Bilal IS 582 Spring 2006.

Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.

(SRS) SOFTWARE REQUIREMENT SPECIFICATION(SRS) 1. Topics to be discussed.. What is an SRS? Purpose of an SRS Who reads the SRS? Who writes the SRS? Characteristics.

Verification & Validation. Batch processing In a batch processing system, documents such as sales orders are collected into batches of typically 50 documents.

E Safety & Cyber bullying Today’ Behavioural Objective If you complete today's objective a positive log will be given on SIMs! If you don’t, a negative.

Facilitating testing and monitoring of number entry systems in medical devices Abigail Cauchi, Christian Colombo, Mark Micallef & Gordon Pace.

Introduction to Evaluation without Users. Where are you at with readings? Should have read –TCUID, Chapter 4 For Next Week –Two Papers on Heuristics from.

Evaluating Requirements

5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.

Strategies YOU can try. When you hear the word “literacy,” what do you think of? Try to list as many words and phrases as you can.

ESSnet project "Automated data collection and reporting in accommodation statistics" Objectives, achievements and results Köln,

Day 8 Usability testing.

Software Development Overview

Chapter 6 : User interface design

What is technical communication?

Software Engineering (CSI 321)

Chapter 11 Designing Inputs, Outputs, and Controls.

Six Sigma Approach.

Topic for Presentaion-2

Usability Evaluation, part 2

INFO 3: Use of ICT In The Digital World

Define phase Interview the client to understand goals, audience, content, design, and delivery requirements. Organize and outline interview information.

Displaying Your Primary Data

Feedback & Evaluation.

ESSnet project "Automated data collection and reporting in accommodation statistics" Objectives, achievements and results

CSc4730/6730 Scientific Visualization

Test Driven Lasse Koskela Chapter 9: Acceptance TDD Explained

Software Engineering Lecture #14.

Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT

MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS

Overview of the ETSI Test Description Language

Unit 4 - A06 – Review Grade Criteria To get a c

Cognitive Walkthrough

The Software Production View Project Summary

Software Development Overview

How To Write An Impressive Business To Business Content.

Presentation transcript:

Show Me: Automatic Presentation for Visual Analysis Jock Mackinlay, Pat Hanrahan, Chris Stolte to be presented at InfoVis 2007

Summary Visual analysis process in Tableau: Analyst specifies each field via “Add to Sheet”. Automatic Marks chooses a good/best viz based on characteristics of those fields Show Me & Show Me Alternatives: Developed to streamline the analysis process, focus on the user experience Analyst selects many fields at once Sees many valid visualizations Analyst chooses the preferred

Summary Goal: Focus on the user experience to support the flow of visual analysis Evaluation: Informal– from customer feedback, employees Semi-formal– used UI logs from beta testers and “active users” Three conclusions: Automatic Marks is mostly correct, 6.8% error rate Skilled users are not using “Add to Sheet” Show Me/Show Me Alternatives is modestly used “We aren’t getting negative feedback about “Show Me”. If “Show Me” is being used by skilled users, then it must be at least kinda good.”

Good Things The software is described in good detail The UI follows good principles Quantity user data have been collected

Room for Improvement The paper required a lot of software description and definitions The chart types really provided too much detail and could have been condensed Who is the target audience– felt more like a user manual or white paper rather than a research paper The evaluation 

Discussion Topics How to define the criteria for “Skilled Users” How does this software support both novice and skilled users? What kind of data could be captured that could support evaluating Show Me/SMA? How can users be involved in improving the software? (Interviews vs. logging)