William H. Bowers – Improving Data Entry Cooper 17.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

Item Banking Neil Wilkinson Item Banking Test development Item banking What data is stored Why use item banking Item bank features Keys to successful.
LCC ImmsLink Program Lost Creek Consulting’s ImmsLink Program is a true, bi-directional interface between your Centricity EMR and your state’s immunization.
Migrating Internet Basic applications to a windowed Graphical User Interface (GUI) Brian Levantine.
College of Alameda Copyright © 2007 Patrick McDermott Vincent van Gogh ( ) The Langlois Bridge March 1888.
1CS 338: Graphical User Interfaces. Dario Salvucci, Drexel University. Lecture 16: Eliminating Errors.
© 2012 Whamcloud, Inc. Lustre Automation Challenges John Spray Whamcloud, Inc. 0.4.
DoD’s FPDS-NG Training Day Project Overview and Status 20 April 2006 Business Transformation Agency.
Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 
Ch 11 Cognitive Walkthroughs and Heuristic Evaluation Yonglei Tao School of Computing and Info Systems GVSU.
1 8. Safe Query Languages Safe program – its semantics can be at least partially computed on any valid database input. Safety is tied to program verification,
Evaluation Entry System Overview NCOER (SGT)
Evaluation Entry System Overview NCOER (CSM/SGM)
Evaluating Architectures Quality control: rarely fun, but always necessary
Troy Eversen | 19 May 2015 Data Integrity Workshop.
William H. Bowers – Planning a UI Design and Development Effort Torres 8.
William H. Bowers – User-Centered Product Teams Torres 4.
William H. Bowers – Designing Look and Feel Cooper 19.
A description of how to construct a Work Breakdown Structure (WBS) with past historical data on a project that is in-flighted to U PlanIT. Next © 2009.
Managing Risk Through Performance Measurement FIRMA Risk Management Training Conference Lori Loken-King - SVP Union Bank, N.A., Operational Risk Management.
William H. Bowers – Synthesizing Good Design: Principles and Patterns Cooper 7.
 CS 5380 Software Engineering Chapter 8 Testing.
Andy Bursavich Justin Farr William Folse Chris Miceli Michael Miceli.
William H. Bowers – High Level Design Torres 16.
William H. Bowers – Making Software Considerate Cooper 14.
William H. Bowers – Usability Evaluation Torres 14.
William H. Bowers – Rethinking Files and Save Cooper 13.
SYSTEMSDESIGNANALYSIS 1 Chapter 20 Software Engineering Jerry Post Copyright © 1997.
Database Security Outline.. Introduction Security requirement Reliability and Integrity Sensitive data Inference Multilevel databases Multilevel security.
Jennifer Thompson Western Michigan University Fermi National Accelerator Lab PST Program July 29, 2008 Mentors: Steve Hahn and JJ Schmidt.
T Iteration demo T Iteration Demo Team Balboa I1 - Iteration
William H. Bowers – Other Communication with Users Cooper 35.
William H. Bowers – Orchestration & Flow Cooper 9.
William H. Bowers – Designing for the Web Cooper 37.
William H. Bowers – Using Controls Cooper 26.
8 th Language Arts Room 203.   Creative  Fun to read  Interesting Pro’s.
Q1 Assume that we determine 2 virtual sectors, and each sectors contain 8 data blocks. If we want to store 9 data in VS0, then this VS0 is insufficient.
William H. Bowers – Menus: The Pedagogic Vector Cooper 27.
Evaluating Architectures. Quality Control Rarely fun, but always necessary 1.
Data Integrity # Best Practices & Lessons Learned. Does It Fit Your Organization?
Data Verification and Validation
Chapter 11 Data Validation. Question Should your program assume the data is correct, or should your program edit the data to ensure it is correct?
(1) Test Driven Development Philip Johnson Collaborative Software Development Laboratory Information and Computer Sciences University of Hawaii Honolulu.
Relational Databases: Why So Many Tables? William Blozan, Ph.D. Fast Answers.
Design Principles and Common Security Related Programming Problems
Name Next Spelling Word #1 Next Previous Spelling Word #2 Next.
William H. Bowers – Eliminating Excise Cooper 10.
William H. Bowers – Requirements Torres 9.
William H. Bowers – Participatory Methods Torres 6.
Naming in Content-Oriented Architectures 1. select produce Data publishing RWINameKey Data own certify 2.
A presentation for ILI Web Site Accessibility: Too Difficult To Implement? Brian Kelly UK Web Focus UKOLN Contents Implementation.
William H. Bowers – Using Toolbars and Tooltips Cooper 29.
TUFMAN April 2015, Noumea, New Caledonia.
Module 6 ********* Data Loading Workforce Information Database Training Last update November 2006.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 10 Using Menus and Validating Input.
Wildfire Costing (WFCST) for Recorders A component of Wildfire One Fire Season 2016.
BACnet Connector Troubleshooting. What is your current issue? 1. My connector is down 2. I get a “Socket Timeout” error 3. I get an “Unknown object” error.
William H. Bowers – Conceptual Design and Architecture Torres 11.
How to validate ISBN/ISSN Available in cataloging, circulation and acquisitions.
Multiplication Timed Tests.
[The Design of Everyday Things, Don Norman, Ch 7]
GRACE Governance, Risk and Control Evaluation.
Data Quality By Suparna Kansakar.
Cooper Part II Making Well-Behaved Products Data Entry
Norman 7 B: Improving Data Entry
Database Management System
User-Centered Design Data Entry CS 4640 Programming Languages for Web Applications [The Design of Everyday Things, Don Norman, Ch 7]
User-Centered Design Data Entry CS 4640 Programming Languages for Web Applications [The Design of Everyday Things, Don Norman, Ch 7]
Validation at Insee.
Presentation transcript:

William H. Bowers – Improving Data Entry Cooper 17

William H. Bowers – Agenda Data Integrity vs. Data Immunity Data Integrity vs. Data Immunity Data Integrity vs. Data Immunity Data Integrity vs. Data Immunity Lost Data Lost Data Lost Data Lost Data Fudgeability Fudgeability Fudgeability Auditing vs. Editing Auditing vs. Editing Auditing vs. Editing Auditing vs. Editing

William H. Bowers – Data Integrity vs. Data Immunity Data integrity Data integrity –Keep ‘bad’ data out of the system –Validate at point of entry –Assumed to be ‘good’ if it is in the DB –Does not require successive validation –Places the needs of the DB over the user

William H. Bowers – Data Integrity vs. Data Immunity Data immunity Data immunity –Programs must look before they leap –Must be trained to ask for help –“Nine” vs. ‘9’ vs. “9” vs. 9 vs. 9.0 –Stopping for corrections may be improper –Incorrect data may be in correct format

William H. Bowers – Lost Data Should the program halt on bad data? Should the program halt on bad data? Use subtle, modeless cues to indicate data status Use subtle, modeless cues to indicate data status Use bounded entry for critical data Use bounded entry for critical data Determine seriousness of lost data Determine seriousness of lost data Can missing information be tolerated? Can missing information be tolerated?

William H. Bowers – Fudgeability Systems tend to be rigid Systems tend to be rigid People tend to be flexible People tend to be flexible Which is more important? Which is more important? –Database –The business supported by the DB Try to model the real world Try to model the real world Difficult to build into the UI Difficult to build into the UI

William H. Bowers – Auditing vs. Editing The user isn’t always right The user isn’t always right Program is responsible for data Program is responsible for data Provide modeless, meaningful warnings Provide modeless, meaningful warnings Maintain audit trail Maintain audit trail Track what was done and by who Track what was done and by who MS Word spell check vs. AutoCorrect MS Word spell check vs. AutoCorrect

William H. Bowers – Questions & Discussion