Ch8new2-10 - Chapter 8 part 2 Designing the Human Interface...

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Chapter 8, part 2: Designing the Human Interface Interface D. Harrison McKnight, Eli Broad College of Business of Essential 2 Know—Chapter 8 Essential Be able to describe the steps in the Be process of designing forms, reports process Be able to list the four General Formatting Be guidelines for designing forms and reports guidelines Be able to list four guidelines each for: – Highlighting information – Displaying text Key terms Design Design Phase 3 in SDLC 1st Solution-Oriented Phase Includes – User Interface Design Input & Output Design Interface & Dialog Design – Database Design Normalization Forms & Reports (Input & Output) Forms Form – Business document – About one instance About or “thing” or – Input and/or output – Passive or active Passive document document – Example: Data entry Example: forms forms Report – Business document – About a collection of About “things” “things” – Output – Passive document – Examples: Summary Examples: & detail reports detail Form + Report Design Process Form The analyst must understand: – Who uses form/report (and #) Who – Why/How form/report is used Why/How – When form/report is used When Structure information into initial prototype Have users review/use prototype Revise form/report; iterate Gather usability assessment data Write up design spec (overview, sample design, Write usability stats) usability Dialog Design Dialog Interaction methods (command, menu) Guidelines for menu design Hardware options General Form/Report Guidelines General Use meaningful titles Include only meaningful info. Balanced layout (i.e., on screen) Make navigation easy and clear Highlighting Guidelines Highlighting Use Conservatively-- ONLY to: – Notify users of errors – Provide warning of problems – Draw Attention to Key Items Use consistently and based on level of Use importance of highlighted information importance Use BLINKING only for: – Identify items needing immediate response Displaying Text Guidelines Displaying CASE: Mixed upper/lower CASE: Mixed SPACING: Double spacing best JUSTIFICATION: Left, ragged right JUSTIFICATION: Left, ABBREVIATION: Few, well known HYPHENS: Not between lines Tables and Lists Guidelines Tables Use meaningful row/column labels Format columns/rows and text – Sort in meaningful order (e.g. alphabetically) (e.g. Sort – 2+ Spaces between columns – Avoid fancy fonts, changing typefaces Format numeric, text data – Right-justify numeric data – Left-justify text Left-justify Designing Interfaces: Issues to Address Issues Designing layouts Structuring data entry Controlling data input Providing feedback Providing help Designing Layouts--Guidelines Designing Format consistently across screens or Format applications applications Design to navigate L-R, top-to-bottom Design (English users) (English Make the navigation flexible Structuring Data Entry--Guidelines Structuring Never request already-available data Provide default values when possible Clarify the units--$, #, tons Always place a caption next to entry field Controlling Data Input—Guidelines Check the data against expected value Check Test for missing data Test # data against a range of values Test for too few or too many digits (SSN) Create an audit trail of data entry Create sequence of steps sequence Providing Feedback—Guidelines Providing Provide status information Provide (e.g., display customer name, screen #) (e.g., Give prompting cues Give (e.g., enter Zip Code: _ _ _ _ _ _ _-_ _ _ _) (e.g., Provide error and warning messages Provide (e.g., value out of range) (e.g., Providing Help--Guidelines Providing Simplify—give short messages Organize—place help in organized lists Show—provide examples of proper use User Interface Design User Solution-Oriented... – What will the system look like? What look – How will the user interact with the system? How system But Still User-Focused – Who uses the forms/reports? Why, when, and Who where? – Usability and usefulness What technique(s) are appropriate for What interface design? interface Prototyping the User Interface Prototyping Design the User Interface – Screen & dialog mock-ups To Achieve System Functionality – Usefulness While Considering Human Engineering While Principles Principles – Usefulness Dialog Design Dialog Interaction methods (command, menu) Guidelines for menu design Hardware options Designing Dialogs Designing Designing the dialog sequence Building prototypes and assessing Building usability usability Designing interfaces and dialogs in Designing graphical environments graphical Sources of Bias Sources Improper Scaling Poor use of color/highlighting Poor (to hide) (to Too much on a graph Assessing Usability Assessing Three Objectives: – Speed – Accuracy – Satisfaction Factors: – Consistency – Efficiency – Ease of Use; Easy to Learn Interface Displays & Dialogues Interface Interface Displays – Method (display) by which user interacts with system system – Rules of grammar, Rules sentence construction, etc. construction, Dialog – Sequence of interaction between user + system user – A conversation conversation (that follows the grammar rules) grammar Logical Design Logical 1.0 Design User Interface process models, data models screen, report, & form layouts and media; dialog specifications Project Repository normalized relations data flows, data stores, data models, form & report designs 2.0 Design Relational Database Linking Systems Analysis to Logical Design to Information displayed on one form or Information report does not necessarily correspond to data stored in one entity type stored Information displayed on a form or report Information displayed must be stored as or derived from data stored in the data model stored – (with a few exceptions, of course) Linking Systems Analysis to Logical Design Logical Analysis – data flow from data Source to process Source – data flow from data process to Sink process – attributes (or data attributes derived from attributes) attributes) Design – input form – report – form/report form/report contents contents Essential 2 Know—Chapter 8 Essential Be able to describe the steps in the Be process of designing forms, reports process Be able to list the four General Formatting Be guidelines for designing forms and reports guidelines Be able to list four guidelines each for: – Highlighting information – Displaying text Key terms ...
View Full Document

{[ snackBarMessage ]}

Ask a homework question - tutors are online