SYS364Input Design

Today and next week Agenda

Input Design (Chap.11) Objectives Source Document Design Screen DesignHuman Factors (Chap.12)

Input DesignGIGO (it’s worse than this)Input Technologies (make a list)

Pen, Paper & FormsKeyboard, MouseScreen widgets: check box, radio button, pick listsTouch screenVoice recognitionATMs, Portable devices (e.g. Telxon, PalmPilots)

Bar code, MICR, stripe readersOCR, scannerE-pens, drawing tabletsE-whiteboardVideo captureBiometric devices:thumbprint, retinal scan,face recognitionTelephone keypad

Input Design Goalselect the best strategy to get quality data into the system in a timely and accurate manneri.e. Good & Fast or Fast & Good

but almost never CheapSystem boundary is the edge of accessible information

QuestionIf you are working on a development team creating a tourist information kiosk for airports, what input devices might you consider and why?

Design of System InputsTextbook, page 407:1. Identify devices and mechanisms2. List system inputs with data content3. Input controls & security4. Design and prototype input methods

What is wrong with this order?Sequence: 2, 4, 3, 1. Do you agree?

Input Designdefine the methods used for data capture, entry and inputData Capture – record the source dataData Entry – convert Captured data into computer readable formData Input – process Entered data into the Information System

Input Design ObjectivesDevelop efficient input procedures:Make it easy to do the right things and hard to do the wrong things. Don’t penalize good users.Reduce input volumeReduce input errors

With these objectives in mind, does anything change regarding the Kiosk example?

Data Input TechniquesCapture and validate data at source,reduce the information float (time from beginning of Capture to end of Entry)Reduce input volume (codes, scanners)Streamline data entryif hard to scan, SKU must be keyed.e.g. poor quality labels, heavy boxes/fixed counter scanner

Data IntegrationRetrieve data, avoid reentry.Use PK lookup to get related data.Integrate systems:Use EDI, XML, WS-IWeb Services Inspection spec (WS-I) describes what services a business offers and how users can access those services. Allows the components of one application to be used by other applications in different locations via the Web and XML

NEWSWire/400 - 01.25.01“There's still an immense number of Web sites out

there that have a manual back end. They put up a storefront, but the orders get printed somewhere, and a sales-entry person enters them into the real application to be processed. But that manual link can end up being both a business exposure and an expense. Every time you re-key data, you risk having it entered wrong. There are a fair number of cases where the screen tools are linking into e-business, but not performing e-business."-- Janet Krueger, analyst at Andrews Consulting Group

Data Entry MethodsBatch vs On-line data entry On-line advantages

Immediate validation Immediate availability of data

Source Data Automation POS terminals (how long did it take until

almost everything had a bar code?) Data strips on cards for security, access

…list the advantagesOf on-line data entry and/or automated data captureWhat are some of the disadvantages? Information exchange standards Cost of coding and reading (e.g. barcodes)? Peak demand? (OLTP throughput) Inflexible? (alternate input method) Hardware requirements?

Develop Efficient Input Procedures

Efficient Use codes Necessary data only (no black holes) Retrieve data from system files or

calculate from other dataTimely

Seconds multiplied by thousands equals hours. Bottlenecks? Do a stress test.

Manual backup methods?

Reduce Input Errors: control the data

Sequence – complete and togetherExistence – is it all there?Validity – is it a real code?Data Type – is it the right kind?Range – allowable valuesReasonableness – sensible valuesNASA’s ozone measurementsCombination – logic Batch Controls – hash totals

Timecard InputSequence Existence Data Type Range Reasonableness Validity Combination

Batch Controls

each day in order# of hours requirednumeric0 <= hours <=243 <= hours <=12Employee No. on fileEmp.Name matcheson screen and card;O/T rate if hours >40time card counttotal hourshash total of Emp.No.

Key Tasks in Input Design1. List system inputs with data content

examine the output requirements2. Design and prototype input methods3. Input controls & security4. Identify devices and mechanisms

Source Document DesignSource Document (i.e. paper) Forms: software that runs on people Forms used to request and collect

input data (i.e. Data Capture) Also used to trigger or authorize an

input action Provides a record of the original

transaction

Why paper is still around:Familiarmany people are scared of using computersand with good reason :-)Accessiblenot everyone has access to a computer or network connection when they need itExchangeableif you can read, you can exchange itPortableno power or equipment requiredLegiblehigher resolution than screen outputreading a screen is 25% slower than reading print

Form layoutSource Document Zones

Heading Control(DB key)

Instructions Body

Total Authorizations

Source Document DesignFlow follows data capture sequenceInternal vs External Document Quality and appearanceCost of using a document is greater than the cost of the form itself.

Screen follows Form Form follows Function

Screens should be attractive- not too much stuff at one timeInformation displayed in a logical order- follow the formScreens should be consistent- titles, layout, F keys, buttons, termsMessages should be specific- help, not error messagesMsgs stay on screen until next user input

Screen follows Form Form follows Function

vertical column alignment – people scan screens – no one reads themUse special effects sparingly (no blinking!)Feedback regarding delays are important – e.g. progress barPrototype screens with users– usability testing

Screen DesignData Entry Process ControlGraphical User Interfaces

Data Entry Screen DesignRestrict user accessProvide a caption for every fieldShow sample formats for valuesRequire an ending keystroke for every field- except for single character fields?- may break rule for high volume data entryDon’t require use of special charactersDon’t require leading zeroes to fill or trailing zeroes for decimals

Data Entry Screen DesignDisplay default values and be careful using them!Display acceptable values whenever possible– e.g. on screen help, pull down lists, check boxes, buttonsProvide method to exit without recording valuesProvide opportunity to confirm action – for non-recoverable, low volume transactions onlyProvide means to move among fields – cursor defaults to left-right, top-bottom. You can override this.Design screen layout to match source documentAllow for people to make mistaeks and change their mindsAllow for searching

Process Control Screen Design

Users can enter commands using interactive input Menu Screens Prompt Screens

Graphical User InterfacesUses graphics such as windows, menus and boxes to allow users to communicate with the system Double clicking… Right clicking… Keyboard shortcuts for expert users To reap advantage, must have

common look and feel

HelpUsers do not read manuals (RTFM)A user reading a manual is a user in deep trouble.on screen help (labels, prompts, codes)context sensitive help- single sentence: how to, what for, what is.AS/400 model: Msg, Cause, Recovery.detail help -- the online manual

Input ControlEnsure data is correct, complete, secureAudit trail- transaction logging in computer file- initials, stamps in paper documents- control number referencesWorkflow- Lotus Notes

Input ControlComputer security- access to programs & filesPhysical security- paper, tapes, microfilm, etc.- access and borrowing privileges- offsite storage & records retention

SummaryInput Design Objectives Source Document Design Screen Design