Reading...
Play button
Play button
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;
24 Cards in this Set
- Front
- Back
|
User-friendly
|
Easy input, clear output
|
|
|
Effective
|
Accurate input and output
|
|
|
Efficient
|
Best use of features and resources
|
|
|
Satisfying
|
Comforatble to use, perhaps familiar
|
|
|
GUI
|
Graphical User Interface
|
|
|
UX
|
User experience
|
|
|
Layout
|
Take advantage of space; group items
|
|
|
Order
|
Left to right (culture note); consistent action buttons
|
|
|
Validation
|
GUI should reject invalid data
|
|
|
GUI Objects
|
make input efficient and accurate
|
|
|
Help and Information
|
Keep the user informed; Progress indicators; link to help
|
|
|
Data Capture Paper Forms
|
Match fields; Consistent with GUI; instructions
|
|
|
Reports
|
Logical; option to print or store; title; production date
|
|
|
Embedded software
|
Device control; GUI Interfaces
|
|
|
Data Dictionary
|
Identifier name; Data type or structure; Size of data; Validation required
|
|
|
Modular
|
Top-down; stepwise refinement; structure diagram
|
|
|
Modular advantages
|
Writing and testing; Clarity of structure; expertise split; Code re-use; Black-box testing
|
|
|
Algorithm
|
Steps to be carried out by computer
|
|
|
Flowchart
|
Graphical representation of algorithm
|
|
|
Pseudo-code
|
Simplified programming language
|
|
|
Pseudo-code format
|
Brief step descriptions; Uppercase keywords; Begin/End blocks;
|
|
|
Rapid Application Development
|
Successive prototypes until final version; Cycles of dvelopment; Iterative
|
|
|
RAD Advantages
|
End-user involved; Prototype is valuable; Easy to evaluate UX
|
|
|
RAD Disadvantages
|
Not efficient large-scale projects; Focus on end rather than process; Software required early
|
