Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Discussion 4 - Trung Lai
Option I: User Interface
1. What are some things to consider when developing a UI for K-12?
- They do not know much about standard UI design, therefore, we cannot assume that they can figure out how to perform certain actions
- Since theyíre students, not researchers, they require more graphical icons and nice-viewing windows
- Mistakes are unavoidable, so there must be a way to roll back and undo certain actions
- And lastly, error messages have to be written in their language (not entirely using SAT words).
2. What are some things to consider when developing a UI for senior citizens?
- They are not patient user, therefore, the less time consuming the better.
- For the majority of them, their eye-sights are not perfect, so font have to be bigger and clearer with color that are not too bright nor too dark
- Error messages have to be very detailed for they may not understand computer concepts
- Being able to undo previously performed actions is a must
- Instructions for usage may be very lengthy for detail step-by-step walkthrough (a wizard for each major task is good)
- Error messageís tone must be very neutral in order for not offending them
3. What are ways to test your user interface? Both before the users are involved and after?
- Heuristic evaluation: evaluate
- The usefulness of error messages
- The language on screen and its meanings
- The requirements for certain display screen
- The support they may require
- Review guidelines
- Check up the guidelines to see if those meets required goals or not
- Check up to match with standard guidelines such as menus, toolbars, and help options.
- Cognitive walkthrough
- Walkthrough the program using a userís perspective
- Asking along the way what is needed, what is not
- Determine if the program make sense to potential users
- Try to understand the predict how a user will interactive the program at any particular time instance
- User Feedbacks
- Test prototypes with users and groups of users and get helful feedbacks for current designs
- Collect all surveys and logs from user's opinions then redesign the system before releasing an updated version
4. What is a cognitive walkthrough and when is it useful?
- It is a process start out with a description of how the system works, the potential users, the goals those users want to accomplish, and a description for each useful task
- It is useful when we want to make sure that our program meets with our clientís requirements. We may want to use this method to determine if our program is useful or not, and how useful it can be. It can also point out the weakness of our program
5. What is wrong with the UI for the clock on page 187?
- No support or descriptions of any kind
- Buttons are too big which may draw attention of the user from the clock itself
- Fonts are not proportional with the whole window
- Chances are this interface does not meet enough of userís expectation (unable to control the clock in a regular fashion)
6. What is a process that you could follow for developing a good user interface?
- We can use User Centered Design process for developing a good user interface
- Define contexts Ė its usefulness based on clientís requirements
- Describe users: descriptions and expectations of potential users; including personalities, origins, special needs and certain restrictions
- Task analysis: list all tasks out, then break each into steps for further designs
- Function allocation: allocate the responsibilities to certain group of users for specific tasks (or privilege)
- System layout / basic design: draft a simple design and cross check with clientís requirements for compatibility and programís constraints for its effectiveness and extensibility
- Mockups and Prototype: create a prototype of the final product to test with potential users
- Usability Testing: keep logs, taking notes, and observe all actions and functionality performed by real user on prototype to evaluate our programís usefulness. Take in feedbacks and determine what need to be done to improve current state of program
- Iterative testing and redesigns: iterate through the whole testing and design process until we are sure that the program is at least up to a certain acceptable standard (testing through prototypes and redesign the system/ subsystems if needed, also plan out to release periodical versions of program to public or client)
- Updates and maintenance: periodically update our programs based on user feedbacks or in order to fix bugs that existed after an extensive period of usage
Link to this Page