Human Computer Interaction CSC 4730 User System Interface CSC 8570 Meeting 8 October 23, 2012.

Slides:



Advertisements
Similar presentations
Introduction to Instructor-Led Online Learning Kevin R. Duffy, M.A.Ed. Daytona State College Daytona Beach Police Department.
Advertisements

Point of Sale (POS) Client & Back Office Server. Operational Concept What is our Objective? What is our Objective? What are our Goals? What are our Goals?
Pitch Guidelines Lesson 10. Check-in: Presentation You should be at least halfway done with your presentation Raise your hand if you have done this.
By: Rachel Hall and Amy Austin.  Grade: All levels  Price  Host App: $24.99  Student App: free (allows up to 32 students)  Location: App Store 
Human Computer Interaction CSC User System Interface CSC Meeting 2 September 4, 2012.
SalesPad SalesPad delivers an all-in-one order entry, inventory and sales management solution integrate seamlessly with Dynamics GP SalesPad simplifies.
INFORMATION TECHNOLOGY Data Capture and Input Methods.
Claims Analysis: Example ‘Hall of Fame/Shame’ Presentation Chris North CS 3724: Intro to HCI.
Banking Addressing Standard 2.0
CPSC 481 Foundations and Principles of Human Computer Interaction
CSC USI Class Meeting 7 October 19, 2010.
Saul Greenberg CPSC 481 Foundations and Principles of Human Computer Interaction James Tam.
From Class Diagrams to Databases. So far we have considered “objects” Objects have attributes Objects have operations Attributes are the things you record.
Term Project AssignmentCS-502 Fall Term Project Assignment CS-502 Operating Systems Fall 2007.
Design Process …and the project.
Term Project AssignmentCS-502 (EMC) Fall Term Project Assignment CS-502, Operating Systems Fall 2009 (EMC)
James Tam CPSC 481 Foundations and Principles of Human Computer Interaction James Tam.
From Scenarios to Paper Prototypes Chapter 6 of About Face Defining requirements Defining the interaction framework.
Ch 5 Specification page 1CS 368 Context Specification one of the most commonly cited reasons for an IT project failure is unclear objectives and requirements.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 6.
CSC USI Class Meeting 9 November 2, 2010 Election Day.
FINANCIAL SOCCER Module 3 Credit, debit and prepaid cards Collect a quiz and worksheet from your teacher.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
The Internet & The World Wide Web Notes
MyIsagenix - Intro Class. Intro Class Agenda  MyIsagenix Overview  Getting Started  Page by Page Walkthrough  Q & A.
FatMax Licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.5 LicenseCreative Commons Attribution-NonCommercial-ShareAlike 2.5.
Welcome to a tour of ProCom’s Work Order System. Please touch the mouse to begin. Welcome to Work Orders “Our goal is very simple: to give you the most.
Human Computer Interaction CSC User System Interface CSC Class Meeting 4 September 18, 2012.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Chapter 2: Understanding and conceptualizing interaction Question 1.
2-1 Chapter 2 Information Systems for Collaboration.
Restaurant Management Systems
Ch 6 - Menu-Based and Form Fill-In Interactions Yonglei Tao School of Computing & Info Systems GVSU.
TOPICS TO BE DISCUSSED  Mobile Commerce Mobile Commerce  M-Commerce Technology M-Commerce Technology  M-Commerce Services and Applications M-Commerce.
1 SWE 513: Software Engineering Usability II. 2 Usability and Cost Good usability may be expensive in hardware or special software development User interface.
E-Commerce and the Entrepreneur
Countdown Timer: What is the definition of a main idea? How can we identify the main idea? Why is it important.
Human Computer Interaction CSC User System Interface CSC Class Meeting 5 September 25, 2012.
Allen Stauffer Rarihwenhawi LaFrance.  University students often lack time to keep track of grades and monitor progress  System would focus on providing.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
FALL 2009 WRITING – END-OF-COURSE. WHO MUST TEST:  ALL students enrolled in English 11  ALL Term Graduates who have not passed the writing test.
I Information Systems Technology Ross Malaga 4 "Part I Understanding Information Systems Technology" Copyright © 2005 Prentice Hall, Inc. 4-1 DATABASE.
COMP106 Assignment 2 Proposal 1. Interface Tasks My new interface design for the University library catalogue will incorporate all of the existing features,
SiS Technical Training Development Track Day 9. Agenda  Understand Workflow Technology  Practice of Workflow (Instructor Led)
Human Computer Interaction CSC User System Interface CSC Class Meeting 7 October 9, 2012.
GOMs and Action Analysis and more. 1.GOMS 2.Action Analysis.
October 3, 2002Initial Proposal - Board of Directors1 SYSTEM-TO-SYSTEM WORKGROUP.
Recuperação de Informação B Cap. 10: User Interfaces and Visualization , , 10.9 November 29, 1999.
1 SY DE 542 Navigation and Organization Prototyping Basics Feb 28, 2005 R. Chow
Team 13 Prathibha and Shrimi 11/12/13 Mobile Credit Card Processing.
Design Process … and some design inspiration. Course ReCap To make you notice interfaces, good and bad – You’ll never look at doors the same way again.
CSC USI Class Meeting 7 February 24, 2009.
Implementing Attaché Webstore. Ninja-Stat Sales through our sites in 2013.
Introduction to Usability By : Sumathie Sundaresan.
CSC USI Meeting 8 October 26, Designing the Perfect Phone™ Meet as design teams this evening Interim design report due by 9:00 p.m. EDT.
CSC USI Class Meeting 9 October 31, 2007.
Amicus Point of Sale and Business Management System Amicus Hospitality.
ONLINE SHOPPING. Refers to buying and selling of goods and services using websites accessed through the internet physical goods such as clothes and books.
E-Commerce & M-Commerce. Introduction Electronic commerce, commonly known as e- commerce, It is a type of industry where buying and selling of product.
InLoox PM Product Presentation Slide 1 InLoox PM Product Presentation © InLoox, Inc. InLoox PM 8 for Outlook Product Presentation The Project.
“Candidates were not advantaged by defining every type of operating system provided as examples in the explanatory notes of the standard. Candidates who.
/16 Final Project Report By Facializer Team Final Project Report Eagle, Leo, Bessie, Five, Evan Dan, Kyle, Ben, Caleb.
Telephone: (408) | | | © 2016 Doubleknot, Inc. Doubleknot for Education Programs.
The Project. A little video inspiration IDEO – an industrial design company.
Computers and Programming
Preliminary Design Review
Class Meeting 8 November 1, 2005
CSC USI Class Meeting 6 October 3, 2007.
Taxi Booking App Development Introduction About Taxi App When every start-up or business owner was seeking for the solution, Uber.
User/System Interface
Presentation transcript:

Human Computer Interaction CSC 4730 User System Interface CSC 8570 Meeting 8 October 23, 2012

Preliminaries Research project Presentations Calendar Questions

The Mobile Wallet Project Goal: Create a user interface design for a Mobile Wallet Worth Having (MWWH). The UI design should be: – As powerful as possible – As worthful as possible – As intuitive as possible Process: – Divide into design teams – Brainstorm design and features, in several rounds, tonight – Choose components for actual design process

The Mobile Wallet Project (2) Design Teams are: Team P: Andrew D, John, Ken, Shishir Team Q: Donald, James B, James N, Kevin Team R: Andrew L, Anthony, Kristin Team S: Chris, Mike, Tyler

The Mobile Wallet Project (3) Move into groups, separating each group from all others as much as possible. Take about 20 minutes to read and discuss – The articles linked from: techcrunch.com/tag/mobile-wallet – The website paywithisis.com – The definitive (but older) survey from IEEE Communications found at csc.villanova.edu/~beck/csc8570/2004_COMSOC- SURVEYS.pdf Then we’ll think creatively

The Mobile Wallet We’ll approach understanding the design of the Mobile Wallet Worth Having in four ways: By perception By design philosophy By task By physical interface But first:

The Old Wallet List everything that is currently in your wallet and determine: – What the reason is for having each of these things in your wallet? – Could any of these things be moved elsewhere?

The Old Wallet Contains Credit cards (several) Medical insurance cards (several) AAA card Shopper loyalty cards Transportation card Driver’s license Other IDs (work, school) Gift cards Social security card Cash Medical condition Business cards Pictures Receipts Stamps Key Train ticket Boarding pass Membership card Key card BandAid Phone numbers Coupons

The Old Wallet (2) What difficulties do you have with the old wallet? How is your old wallet imperfect?

The Old Wallet Difficulties Too big Destroys clothes Things fall out Not well organized Things not readily visible Wallet costs money Easy to use if stolen Breaks credit cards Can get wet Degrades over time

Mobile Wallet: Perception What do you think of when someone starts talking about a mobile wallet? What is your mental model of the device? – Theories or beliefs about its operations – A “space” in which problems are solved through a sequence of steps – A representation of the device in a more familiar or “easier” setting – Created from an understanding of a textual description of the device

Perceptions; Mental Models Act like a credit, loyalty, membership … card Incorporates loyalty transactions Rapid, easy method of payment – Compare with EZPass Facilitates transactions – Monetary – Identity verification – Borrowing – Pricing/buying

Mobile Wallet: Design Philosophy How does the perception of a MWWH translate to an overall design? An Analogy: – A toaster should make toast. – A toaster can be easily made to toast more than bread (bagels, English muffins, crullers, …) – Sometimes the item needing toasted is frozen. – A toaster should operate wherever it can be plugged in. – But it has to be plugged in to work.

Design Philosophy Hint: Sometimes you can state a design philosophy by developing a marketing campaign for your product. Simple to use No cash needed Purchases made easily Throw away your wallet, go green Important information at your fingertips Secure

Mobile Wallet: Physical Interface What should the physical design of the MWWH and its physical interface widgets be?

Physical Interface Transmit w/ near field communication Camera for scanning input Power on/off Touch screen GPS (interface or feature) Accelerometer (eg. bump communication) Network connection Sound / tactile feedback Virtual representation of typical wallet contents – Perhaps hierarchical, perhaps linear, perhaps ? Configuration state

Mobile Wallet: Task List What tasks would you like to accomplish with your mobile wallet?

Task List Pay for things – Add gratuity – Multiple currencies Transfer money between – Two of your accounts – You and someone else Record, review, analyze transactions – Including location Record, review, analyze loyalty bonuses Access/demonstrate identity Access/demonstrate medical history Location services: find vendors, receive promotions from vendors Subscription services: Membership services: Transportation services: Manage security – Tracking, destruction, if lost – Personalization Manage accounts Cloud sourced – Synchronization – Multiple devices

Perhaps More Tasks These next slides are extracted from a SXSW 2012 presentation given by Omar Green, Director of Strategic Mobile Initiatives at Intuit

The mobile wallet works in the context of your life.

WALLET WORTH HAVING

Mobile Wallet: Design Task Each design team chooses X of the Y tasks in order of preference. Submit choice by 10/29 – One alternate task can be proposed. – Instructor will assign tasks based on preference ordering – Important: The teams are designing the user interface for the functionality described, not the implementation of the functionality itself. Design teams meet Tuesday, 10/30, during class time Interim design report due by 9:00 p.m. EDT that evening. Final design report due Wednesday, 11/7

Mobile Wallet: DT (2) Being as creative as possible Develop a task analysis Use an FSM model or a GOMS model, if appropriate Propose a design for the MW to accomplish the team’s assigned task Implement a prototype of the design (implement can mean “screen shots” or a running program) Analyze the prototype in light of the GUEPs and CDs Use other ideas from course as appropriate to justify your design. Submit a report with the results of your work.

Mobile Wallet: DT (3) Results should be four designs that, when combined, describe a device that is close to a mobile wallet worth having.

To Do Submit choices of mobile wallet tasks by Monday, October 29. Submit (by ) Progress Report 1 by Tuesday, October 30. Meet as an interface design team on Tuesday, October 30. Submit initial design report by 9:00 p.m. EDT.