xxiv. user interface design - department of computer science
TRANSCRIPT
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 1
XXIV. User Interface DesignXXIV. User Interface Design
What is Human-Computer Interaction?Affordances, Mappings, Mental Models,Feedback, Forcing Functions, Learning
How to Design InterfacesUser Dialogue Design
Inputs and Outputs
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 2
HCI = Human-Computer InteractionHCI = Human-Computer Interaction
Why should a Systems Analyst Know HCI?Why should a Systems Analyst Know HCI?
n 40-60% of today’s software does user interface management -high interactivity with the user, much end-user programming
n User interactivity is only going to get more complexü3D graphics and Virtual RealityüMore augmented reality activities
n Many of the problems with introducing and maintaining asystem can be traced back to a bad interface designüUsers sabotage systems they don’t understandüUsers make more errors when dealing with systems that
are difficult to usen A good user interface can reduce coding costs, reduce high
costs of interface problems, reduce serious life-threateningerrors, sell more products, lead to increased use of computers
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 3
Increased ProductivityIncreased Productivity
20 usersX 230 daysX 100 screens per dayX 10 sec per screen (savings)
= 1278 hours or 32 weeks
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 4
Reduced Training CostsReduced Training Costs
20 employeesX 2 systems/applications per yearX 2 1/2 days per application (saved)
= 100 days or 20 weeks of savings
Training and support often more costlyTraining and support often more costly
than hardware and softwarethan hardware and software
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 5
Preventable User ErrorsPreventable User Errors
500 usersX 20 errors per yearX 15 minutes per error
= 2500 hours lost or 63 weeks
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 6
Increased ProductivityIncreased Productivity
500 menu selections per dayX 2 sec per selection (saved)X 230 days per year
= 320 hours or 8 weeks
For a $100K person-year cost, saved timeFor a $100K person-year cost, saved timetranslates to $15,000translates to $15,000
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 7
Serious Life-Threatening ErrorsSerious Life-Threatening Errors
n Analysis of transcript of 911 call announcing bomb inCentennial Park at the Atlanta Olympics indicated that 20minutes were needed to call dispatchers
Dispatch system required an address for Centennial ParkDispatch operators could not find anyone who knew addressBomb was set to go off 30 minutes after call
n Airline crashed into a mountainside in Colombia in 1996,killing all aboard (including a well-known computer scientistand his whole family!)
Pilot typed in “R” rather than full name of airportGuidance system took first airport in the list beginning with
“R” which was the wrong airportPlane ran into mountain...
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 8
User Interface EconomicsUser Interface Economics
n Good user interfaces sell systems!üWindows is a copy of the Macintosh interfaceüThe Mac interface is a copy of Bravo - developed by user
interface researchers at Xerox PARCn User interface capabilities and awareness help get contractsn Poor user interfaces can cripple a system that is outstanding in
all other respectsn Computer-driven interfaces placed in most mechanical
products we knowüClassic problem of users not being able to set the clock on
their VCRüUsers often can’t use a photocopy machine, a fax machine,
a cash register, a candy machine, a bank machine or evena telephoneüCars will eventually be completely computer driven...
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 9
Why Are User Interfaces Poor?Why Are User Interfaces Poor?
n Inadequate training of people developing interfacesn Diversity of knowledge required to design good interfacesn Rapid technological advancesn Reluctance of companies to commit resourcesn Poor management - programmers do not talk to user design
teams and vice versan User Interface specialists rarely involvedn The "bricklayers" (programmers) are left to design the user
interface, by default
“Ignorance by software engineers of usability“Ignorance by software engineers of usabilityand how to measure it is roughly equivalent toand how to measure it is roughly equivalent to
an electronics engineer not knowingan electronics engineer not knowingwhat volts and watts are and how to measure them."what volts and watts are and how to measure them."
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 10
What’s Wrong with this Interface Design?What’s Wrong with this Interface Design?
Design of User Interface for CAVECAT Media SpaceDesign of User Interface for CAVECAT Media Space
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 11
Why is thisWhy is thisDesignDesignBetter?Better?
Design of UserDesign of UserInterface forInterface for
TelepresenceTelepresenceMedia SpaceMedia Space
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 12
Some Basic Human CharacteristicsSome Basic Human Characteristics
n Humans like to problem solve, but don’t like unsolvable problems!n Humans are always learning, but learning is hard!n Humans use prior learning to support new learning.n Users don’t read manuals but work by copying and askingn Users are always building models of their worldn ImplicationsüBuild interfaces that allow people to learn by usinglearn by using the
interface;üBuild interfaces that suggest correct models;üBuild interfaces that rely on prior learning.
n Users don’t mind if something doesn’t make sense -- they buildtheir own model to make it make sense.
n Users prefer simple models.n Inconsistency doesn’t bother users -- A simple model which
doesn’t always match is better than a complex model that is toohard to learn.
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 13
Characteristics of a Well-Designed InterfaceCharacteristics of a Well-Designed Interface
The design of the user interfacenHas affordancesaffordances - makes each operation visiblenOffers obvious mappingsmappings - makes the relationship between
the actual action of the device and the action of the userobviousnProvides feedbackfeedback on the user's actionnProvides a good mental modelmental model of the underlying behaviour of
the devicenProvides forcing functionsforcing functions -- prevents a user from making
bad errorsnSupports automatic learningautomatic learning -- provides consistencies and
practice that help the user acquire interface skills
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 14
AffordancesAffordances
nn AffordanceAffordance of an artifact means that the design of the artifactin some way describes what the user can do with it, i.e.,indicates what operation the user may perform.
n Good example of affordance -- buttons which indicate to theuser that they are to be pressed
n Bad example of affordance -- the "put-away” box in the upperright hand corner of a Macintosh window.
n Well-known affordances:Glass is for looking through (...or breaking)Cardboard is for writing on...Radio buttons are for pushing or turning…Icons are for clicking…Door handles are for pulling, door bars are for pushing...
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 15
DifferentDifferent Affordances Affordances
PULLSIDE
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 16
Mapping FunctionsMapping Functions
nn Mapping FunctionalityMapping Functionality - the design in some way shows amapping between the intended use of the tool and the action ofthe underlying technology
n Good example of mapping: -- the presentation of the font to beselected in the form and shape of the font
n Bad example of mapping: function keys in general -- themapping is totally arbitrary
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 17
Some Interfaces Work Better Than OthersSome Interfaces Work Better Than Others
BackRight
FrontLeft
FrontRight
BackLeft
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 18
Paired Stove ControlsPaired Stove Controls
Back Front Back Front
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 19
Fully Natural Mapping of Controls and BurnersFully Natural Mapping of Controls and Burners
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 20
Fully Natural Mapping of Controls and BurnersFully Natural Mapping of Controls and Burners
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 21
Mental ModelsMental Models
nn Mental ModelMental Model - the underlying understanding that aperson has about how a technology or device works so thatthe user has some idea that if she performs action A, thenevent B will follow
n Good example of mental model usage:WYSIWYG - What you see is what you get
n Example of systems with no mental model: onlineonlineretrieval systems, extra functions on a telephoneretrieval systems, extra functions on a telephone
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 22
Forcing FunctionsForcing Functions
nn Forcing FunctionsForcing Functions are designs that prevent users from takingactions which are inappropriate or which would lead to error
n Good example of a forcing function design:the Macintosh menu bar - grays out and prevents the selection
of those items inapplicable to the current contextn A bad example of a forcing function design:
Unix - every command is allowed as long as it is typed correctlyn Exercise: You buy some groceries on your way to work and put
them in the office refrigerator; how do you make sure that youwon’t leave work without the groceries?
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 23
FeedbackFeedback
n Feedback - a design in which a form of visual, auditory or othermodality response is given immediately after the user action toindicate that the action has been received
n Good example of feedback:icons on the screen which show a reverse video image when
selectedn Example of non-use of feedback :
Latex and other text formatting systems
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 24
Automatic LearningAutomatic Learning
nn Automatic LearningAutomatic Learning - a design can force learning on the userby offering repetitive patterns of user actions or screen displays
n Good examples of Automatic Learning:user actions always involve same number of steps, e.g., select
object, select general action to perform on object, selectspecific case of action
n Example of non-use of Automatic Learning :Screens which change standard menu item locations from
display to displayn Bad Example of Automatic Learning Usage:
A confirmation action that always requires a carriage returnn Good example of Automatic Learning Usage:
Confirmations that require some knowledge of context, e.g., thefirst character of the file to be deleted
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 25
Where are the Where are the AffordancesAffordances, Mappings, etc. ?, Mappings, etc. ?
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 26
Where are theWhere are the Affordances Affordances, Mappings,...?, Mappings,...?
mappings
affordance
forcingfunction
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 27
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 28
Where are theWhere are the Affordances Affordances, Mappings,...?, Mappings,...?
n Affordances: Slider on the right side. Arrows at the top andbottom suggest sliding the bar (even though they are buttons). Thesize/location of the bar suggests the allowable directions that thiscan be slid.
n Mappings: Search button, the icon with the magnifying glass.Magnifying glass used to look for things/expand things.
n Feedback: The scrolling logo on the top right to indicate that asearch for a page is in progress. Tells the user that their last jumpto a hyperlink is being processed.
n Mental Model: Following a sequence of links forms a chain. TheUI allows navigation of this chain via the forward and back buttons.
n Forcing Functions: The forward/back buttons are enabled only ifnavigation of the chain in the specified direction is allowed.
n Automatic Learning: Links always consistently highlighted,visited links consistently highlighted. OR, interface uses theNetscape/Explorer layout and functions.
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 29
Are we Good Designers?Are we Good Designers?
n Do we put things in the same place in our kitchen and on the sameshelf in our refrigerator so that after constant use, we learn exactlywhere things are through automatic learning?
n Do we organize our clothes in random fashion throughout our closetand our desktop giving no overall mental model of storage?
n Do we post up signs above water faucets and doors indicating thatone should turn them right or left or push or pull them - when theoriginal designer of our apartment left no affordances to tell us this?
n Do we constantly bump into things, knock our head, hurt our kneesetc.? Do we avoid moving the furniture so that it creates a forcingfunction that prevents us from walking into something
n Do we store things with no identification labels that would provide amapping function to the item we want, e.g., keys on a ring that all lookalike
n Do we respond to email confirming that a time has been set and themessage has been received, thus giving feedback to our friends?
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 30
Designing User Interfaces:Designing User Interfaces:Three Easy StepsThree Easy Steps
n I/O Design: Decide who inputs what data when; this may involve
üBatch input, such as reading data from a file to update adatabase at 7pm each day, orüBatch output, such as producing a report every Friday, or
ü Interactive input and/or output, such as customer accesstheir accounts at the rate of 1,500/hr
n Dialogue Design: For each input and/or output session designthe dialogue structure that will be supported; for example, anATM session dialogue structure involves user inserting card,system prompting for PIN etc.
n Screen Layout and I/O Format Design: For each interactivedialogue, design the screens that will be presented to the user(this will depend heavily on the hardware and software platformchosen earlier); for each batch I/O design the format of the inputdata, or the output report.
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 31
User GroupsUser Groups
n In general, an information system will be used by severaldifferent groups, including non-technical people (clerks,managers) and technical people (system operators, databaseadministrators, ...)
n Each one of these groups may require its own interface (someassuming no technical background on the user’s part, othersassuming a lot)
nn End users End users are the non-technical users of an informationsystem.
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 32
User Interface Medium: MonitorsUser Interface Medium: Monitors
nn MonitorsMonitors used to display input/output; key characteristics ofmonitors:
nn Display areaDisplay area -- how large is the screen;nn Character sets and graphicsCharacter sets and graphics -- older monitor technology was
character-based (i.e., the monitor could display one of Xcharacters in one of N screen positions, e.g., 60×80); newtechnology is bitmap-based (i.e., monitor can display a pointof different grayscale intensity/colour in one of N screenpositions, e.g., 480×640);
nn Paging and scrollingPaging and scrolling -- data are displayed a page-at-a-time, orcontinuously through scrolling
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 33
Windows and Graphical User InterfacesWindows and Graphical User Interfaces
n Windows provide a user-defined partition of the screen intomultiple working areas, much like the documents one may havelying on her desk
n Windows have become an interface standard, with OSF Motif(Unix) Microsoft Windows (IBM PC OS), Apple MacOS (AppleMacintosh OS)
n Graphical user interfaces (GUIs) use icons (graphic symbols), pop-up windows, scroll bars and pull-down menus to offer a userfriendly interface
n Other features of GUIs: radio buttonsradio buttons, check boxes check boxes anddialogue boxesdialogue boxes
n User friendliness is enhanced by a mouse, trackball, pen or otherpointing and input device which reduces the need for a keyboard
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 34
Layout ConceptsLayout Concepts
n The screen is often divided into three boxes
üNavigation area (top)üStatus area (bottom)
üWork area (middle)n Information can be presented in multiple areasn Like areas should be grouped togethern Areas and information should minimize user movement from one
to anothern Ideally, areas will remain consistent inüSize
üShapeüPlacement for entering data
üReports presenting retrieved data
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 35
Content AwarenessContent Awarenessand Aestheticsand Aesthetics
n All interfaces should have titlesn Menus should show clearly where you are, also where you came
from to get theren It should be clear what information is within each arean Fields and field labels should be selected carefullyn Use dates and version numbers to aid system usersn Interfaces need to be functional and inviting to usen Avoid squeezing in too much, particularly for novice usersn Design text carefullyüBe aware of font and sizeüAvoid using all capital letters
n Colors and patterns should be used carefullyüTest quality of colors by trying the interface on a black/white
monitorüUse colors to separate or categorize items
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 36
User Experience and ConsistencyUser Experience and Consistency
n How easy is the program to learn?n How easy is the program to use for the expert?n Consider adding shortcuts for the expertn Where there is low employee turnover, some training can lessen
the impact of less precise interfacesn Consistency enables users to predict what will happenn Reduces learning curven Considers items within an application and across applicationsn Pertains to many different levelsüNavigation controlsüTerminologyüReport and form design
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 37
Dialogue ModesDialogue Modes
nn Menu selectionMenu selection -- user given a number of options listed on a menu,selects one and the system carries out the option selected or updatesits database accordingly, then displays another menu;ne.g., macOS and applications, including Powerpoint (used to
create these slides)nn Instruction setsInstruction sets -- dialoque structured around instruction sets which
provide the user with a command language (using structured English,mnemonics or free-format syntaxne.g., Unix
nn Question-AnswerQuestion-Answer dialoque dialoque -- system or user asks questions andgets answers; system-driven (as opposed to user-driven) Q-A easierbecause it can have built-in structure
nn Graphic-basedGraphic-based dialoque dialoque structure structure -- builds on the monitor+mousecapabilities described earlier; uses menus but also many otherfeatures
Graphical User Interfaces clearly the way of the futureGraphical User Interfaces clearly the way of the future
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 38
Designing Dialogue StructureDesigning Dialogue Structure
One could use state diagrams to specify dialogue structure to besupported by a user interface. Such diagrams may have only inputfrom the user (“events”), conditions on, and output (“actions”) to theuser.
Machine ON
Application ON
Machine OFF
Click on icon/open window
Click on box/close window
Click on application/open application
Quit/Close application
Shut down option/turn off
Input from user/Output by machine
Press turn on button/turn on
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 39
Start
CancellationRequest
End
End/end query
reservation not possible;ask for alternative
ReservationRequest
Have Detailson Reservation
Confirm request/confirm reservation
Info Request
ask for info/prompt
Confirm request/change not possible
end dialogue/’bye’
Details onCancellation
ChangeRequest
Details onChange
Give details/Confirm prompt
query/give info
Confirm request/confirm cancellation
Airline Reservation Dialogue StructureAirline Reservation Dialogue Structure
reservation/prompt
change/prompt
cancel/prompt
Give details/Confirm prompt
Confirm request/confirm change
Give details/Confirm prompt
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 40
Dialogue Structure for an ATMDialogue Structure for an ATM
Card entered/PIN?
PIN/-Valid PIN/Transation?
Invalid PIN/Return card
Withdrawal/Amount?
Deposit/Amount+Envelop?
Amount+Envelop/Print receipt
Amount/Sufficient funds?
No/Amount?
Yes/Cash+receipt
Balance/Print balance
Cancel/Return card
No/Return card
Yes/Transaction?
-/Another transaction?
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 41
How to Design a User Interface: IterativeHow to Design a User Interface: IterativeDesignDesign
Plan Prototype
MeasureLearn
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 42
Iterative Interface DesignIterative Interface Design
PlanPlan -- identify what needs to be learned; do highest risk itemsfirst, identify why they are high risks; identify user(s), tasks tobe performed through the interface, time allowed to doiteration
e.g., temporary secretary, type letters, 1hrPrototypePrototype -- prototype only the pieces that are needed; intended
to minimize effort and maximize feedbackMeasureMeasure -- gather data on how effective the prototype is; look
for false affordances, missing affordances, useful affordances;also check for overhead in learning the interfaces as opposedto doing useful work
LearnLearn -- evaluate the data to identify areas that need furtherelaboration
User must be in the loop of the iterative design process!User must be in the loop of the iterative design process!
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 43
PrototypingPrototyping
n Build a “quick-and-dirty” implementation of the interface in avery high level language (Lisp, Prolog, 4GL) or GUI tools, justto show the user what the interface looks like
n Do a paper mock-up paper mock-up using cardboard, index cards, colourmarkers, tape, scissors,...
Use cardboard rectangles or flip charts to represent thescreen; use index cards for drop down menus
Avoid technical terms, “very intelligent” help,unimplementable assumptions
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 44
Paper Mock-UpsPaper Mock-Ups
n Designer plays “the computer”, write on tape or transparencycomputer’s response
n Users use their fingers as a mousen Users write “typed” input on removable tape or transparencyn Mock-ups take away the intimidation of the “technology
barrier”, make users feel at ease; users’ imagination fills thegaps
n Mock-ups can be changed very quickly (quick feedbackimportant to users)
n However, mock-ups only approximate look-and-feel ofinterface, can’t be used to assess response times
Do users and organizations accept mock-ups?Do users and organizations accept mock-ups?Yes, they do!Yes, they do!
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 45
Other Input/Output DesignOther Input/Output Design
n Apart from user interfaces, through which the usersinput/output directly information into/out of an informationsystem, other input or output modes may have to be designedas well.
n For example, a government information system may require adata entry interface, where staff input data read in from formsfilled out by people (because government can’t assume thateveryone has and can use a computer)
n Or, an output report format may be designed for bankexecutives who don’t have the time to learn to use a particularsystem, but do want to keep track of certain statistics.
n Below we list some of the options in designing such such I/Ointerfaces.
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 46
Output Design: Types of OutputsOutput Design: Types of Outputs
•• External outputs External outputs -- leave the system permanentlye.g., paycheques, airline tickets, boarding passes,...
•• Turnaround outputs Turnaround outputs -- leave and later re-enter the systeme.g., invoices, purchase orders
•• Internal outputs Internal outputs -- never leave the system (useful formonitoring and management purposes)
e.g., internal reports, summary reports etc., used for systemadministration
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 47
Input Design:Input Design:Data Capture, Data Entry and Data InputData Capture, Data Entry and Data Input
nn Data capture Data capture involves the identification of new data to beinserted in an information system, e.g., a photo
nn Data entry Data entry is the process of translating the source documentinto a machine readable form
e.g., digitizing the photonn Data input Data input is the actual entry of data (already in machine-
readable form) into the computer
Input/Output Media and FormatsInput/Output Media and Formats
n An input/output mediummedium is the material used to recordinformation
e.g., punched cards, tape, diskette, paper or video displaydevice
n An input/output formatformat determines the way information isorganized on the medium
e.g., for output, tables, bar or pie charts,...
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 48
OutputOutput
•• Output media Output media -- paper used most frequently, but alsomicrofiche (good for archiving), video (fast-growing use)
•• Output formats Output formats -- tabulartabular format, zonedzoned or form-basedformat places text or numbers in designated areas, graphicgraphicformat uses graphs or charts to display information, narrativenarrativeformat uses narrative form to present information
1stQtr
2ndQtr
3rdQtr
4thQtr
020406080
100
1stQtr
2ndQtr
3rdQtr
4thQtr
EastWestNorth
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 49
Preparing Graphs and Charts with a SpreadsheetPreparing Graphs and Charts with a Spreadsheet
1st Qtr 2nd Qtr 3rd Qtr 4th Qtr
East 20.4 27.4 90 20.4
West 30.6 38.6 34.6 31.6
North 45.9 46.9 45 43.9
South 153.1 32.6 47.9 22.1
1stQtr
2ndQtr
3rdQtr
4thQtr
0
50
100
150
200
1stQtr
2ndQtr
3rdQtr
4thQtr
EastWestNorthSouth
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 50
Preparing Graphs and Charts with a SpreadsheetPreparing Graphs and Charts with a Spreadsheet
1st Qtr 2nd Qtr 3rd Qtr 4th Qtr
East 20.4 27.4 90 20.4
West 30.6 38.6 34.6 31.6
North 45.9 46.9 45 43.9
South 153.1 32.6 47.9 22.1
1st Qtr
2nd Qtr
3rd Qtr
4th Qtr
0% 50% 100%
1st Qtr
2nd Qtr
3rd Qtr
4th Qtr
SouthNorthWestEast
13%
17%57%
13%1st Qtr 2nd Qtr 3rd Qtr 4th Qtr
1stQtr
2ndQtr
3rdQtr
4thQtr
East
North0
50
100
150
200EastWestNorthSouth
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 51
Internal Controls for Inputs and OutputsInternal Controls for Inputs and Outputs
nn Monitor number of inputs Monitor number of inputs -- keep track of batch#, # ofdocuments, # of lines; these can be compared with outputs
nn Data validation for inputs Data validation for inputs -- this involves programs whichcheck for typos, missing or suspicious information
Data errors can be reduced dramaticallyData errors can be reduced dramaticallybecause of data validation proceduresbecause of data validation procedures
n Internal controls for outputs include specifying exactly thetime, volume and destination of each output, also accesscontrols (e.g., password)
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 52
SummarySummary
n The acceptance of an information system by its usersdepends critically on its user interfaces
n User interfaces are best developed through prototyping,involving prototype implementations or paper mock-ups
n In designing a user interface, one needs to keep in mindcognitive principles about human information processing, andmemory organization
n Human-Computer Interaction is the area of Computer Sciencewhich studies such principles and offers ways they can beexploited to build better user interfaces
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 53
Questions?
?
Information Systems Analysis and Design csc340
2001 Marilyn Mantei and John Mylopoulos Interface Design -- 54
Additional ReadingAdditional Reading
[Norman88] Norman, D., The Psychology of Everyday Things, BasicBooks, 1988.
[Shneiderman92] Shneiderman, B., Designing the User Interface:Strategies for Effective Human-Computer Interaction, Addison-Wesley,1992.