Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
42 Cards in this Set
- Front
- Back
|
System interface |
these are "connections" with other systems, where systems exchange information with each other. They are designed as a part of program design. |
|
|
User interface |
these are "connections" with users. They entail navigation mechanism, input mechanism, output mechanism, and GUI. |
|
|
Navigation mechanism |
this is a part of user interface that provides the way for users to tell the system what to do |
|
|
input mechanism |
this is a part of user interface that defines the way the system captures information |
|
|
output mechanism |
this is a part of user interface that defines the way the system provides information to users or other systems. |
|
|
Graphical User Interface (GUI) |
a part of UI that is the most common type of interface in use today. |
|
|
Principles for User Interface Design |
Layout Content awareness Aesthetics Usage Level Consistency Minimize User effort |
|
|
Layout |
-principle of UI design Screen divided in a way where information can be presented in multiple areas, like areas group together. areas/info minimizes user movement. |
|
|
Navigation area |
top area of UI layout |
|
|
status area |
bottom area of UI layout |
|
|
work area |
middle area of UI layout |
|
|
content awareness |
-principle of UI design all interfaces should have titles menus show location, where you came from, clarity of information within each area fields/labels should be selected carefully dates/version numbers to aid system users |
|
|
aesthetics |
-principle of UI design interfaces need to be functional and inviting to use avoid squeezing desgin text carefully colors/patterns should be used carefully |
|
|
usage level |
-principle of UI design ease of use desired (easy completion of job tasks) ease of learning desired (quick/easy ways to figure out what to do) |
|
|
frequent users usage level |
include ways to perform tasks directly (hot keys, short-cuts, etc) |
|
|
infrequent users usage level |
include careful menu designs, tool tips, extensive help systems |
|
|
Consistency |
-principle of UI design elements are the same throughout the application enables users to predict what will happen reduces learning curve |
|
|
Minimize effort |
-principle of UI design 3 clicks rule: users should go from start / main menu of system to information/action they want in no more than 3 mouse clicks/3 keystrokes |
|
|
UI design Process |
1. understand the users 2. organize the interface 3. define standards 4. develop prototypes 5. evaluation/testing |
|
|
Understand the users |
-first process in UI design use personas plan UI that is satisfying for particular user group use scenarios |
|
|
Personas |
In understanding the users, develop characterizations of various users groups. Look at interests, typical behaviors, goals and objectives, expectations |
|
|
Scenarios |
outline steps that users perform to accomplish part of their work |
|
|
Organize the Interface |
-2nd process of UI design define basic components of interface, and how they work together to provide functionality to users show how all information on site fits together helps establish hierarchy of info on site. |
|
|
Define Standards |
-3rd process of UI design Clarify decisions on al key interface elements to ensure consistency: -basic common elements (screens/forms/reports) -interface metaphor (calendar/checkbook/shopping cart) -interface objects (customer/client, employee/associate) -interface actions (buy/purchase/check out, exit/quit -interface icons (pictures |
|
|
Design Prototyping |
-4th process of UI Mock up or simulation of screens, forms, reports common methods: -paper sketches -wireframe diagrams -storyboarding -wireflow diagrams -html prototype -language prototype |
|
|
Interface Evaluation |
-5th process of UI design eval methods: -heuristic evaluation -walkthrough evaluation -interactive evaluation -formal usability testing |
|
|
Heuristic evaluation |
-evaluation method where you compare design to checklist |
|
|
Walkthrough evaluation |
-evaluation method where team simulates movement through components |
|
|
Interactive evaluation |
-evaluation method where users try out the system |
|
|
Formal usability testing |
-evaluation method that is considered expensive. it is detailed use of special lab testing. |
|
|
Navigation design principles |
-assume users have no knowledge/ prior experience -all controls should be clear/understandable and placed in intuitive location on screen -prevent mistakes, gray out unusable commands -simplify recovery mistake -use consistent grammar order |
|
|
Menu tips |
-broad/shallow design preferred -logical categories are objects or actions -common menu formats include menu bars, drop-down menus, popup menus, etc -menus may become less popular with touchscreen trend |
|
|
message tips |
common message types: -error message -confirmation message -ack message -delay message -help message strive for clear/concise should be grammatically correct, free of jargon |
|
|
Input design principles |
simply/easily capture accurate information for system reflect nature of inputs find ways to simplify their collection |
|
|
online processing |
immediately records transaction in appropriate database |
|
|
batch processing |
collects input over time, holds them temporarily, processes all transactions at one time in a batch |
|
|
Benefits of capturing data at source |
-reduces duplicate work -reduces processing time -decreases cost -decreases probability of error |
|
|
Source Data Automation |
can be obtained by using following technologies -bar code readers / scanners -optical character recognition -magnetic stripe readers -smart cards -RFID tags |
|
|
Minimize keystrokes |
keyboard entry is slow/error prone don't ask for info that can be obtained in other ways |
|
|
input validation |
apply a judicious amount of input validation to ensure accuracy -completeness check -format check -range check -check digit check -consistency check -database checks |
|
|
Output design |
convey information the user needs |
|
|
output design principles |
-understand report usage -manage information load -minimize bias -utilize various report types (detail, summary, exception, graphical) and media to satisfy users' output requirements. |
