Refresher/m/SDLC/Functional Design

Requirements - Part 2
Gohome.png
Functional Design
OOP
   
OOP
Ledgray.png
 Metaphor: the use of a vehicle (e.g. stage) to visualize a tenor (e.g. the world or a screen area)
Ledgray.png
 Design: relationship between users with problems to solve and designers with solutions to offer
Ledgray.png
 Successful metaphor examples are Microsoft Windows or a mouse pointing device
Ledgray.png
 Progress bar: reducing the user's perception of waiting
Ledgray.png
 Dropdown: big list in small space
Ledgray.png
 Data entry QA measures: show examples, validate entry, check DB, minimize typing, progressive lookup, autocomplete
Ledgray.png
 Sample prototyping techniques: sequence diagram, UI mockups, and throw-away code
Ledgray.png
 How to anticipate user behavior: modeling based on usage and prediction based on models
Ledgray.png
 Access to countless features: menu controls, ribbon interfaces, query language
Ledgray.png
 Editor for few items of many fields: listbox for items, tab controls for fields
Ledgray.png
 Editor for many items of few fields: use grid control or add logic for grouping, paging, filtering or autocomplete
Ledgray.png
 Too many colors: untidy, unprofessional and hard to read
Ledgray.png
 Web environment: easier to deploy, more collaboration, slower performance
Ledgray.png
 Desktop environment: harder to deploy, less collaboration, faster performance