1 / 18

Introduction to User Interface

Introduction to User Interface. Instructor: Jingwu He. Sample View of the User Interface. User Interface. User. Computer Program. A user interface is the junction between the user and computer. Correct View. A user interface is much more than a layer between the user and the computer

mason-kramer
Download Presentation

Introduction to User Interface

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction to User Interface Instructor: Jingwu He

  2. Sample View of the User Interface User Interface User Computer Program A user interface is the junction between the user and computer

  3. Correct View • A user interface is much more than a layer between the user and the computer • Incorporates an understanding of • The user • The task flow • The environment • Etc.

  4. DemoLargestConsole.java • DemoLargestGUI.java

  5. User • Issues involved in designing a user interface for even a sample task can be complex • There are lots of ways to design an interface to the same task (we just saw examples)

  6. Usable for Whom?

  7. Possible Usability Issues?

  8. Bug’s Life Example • Consider who the users are • Is the GUI attractive to user? • Is the program easy to install and use?

  9. What is the User Interface (UI) • Different actors perceive it very differently • Developer’s view • Application functionality is separate from UI • UI often seen as an add-on • User’s View • Users don’t distinguish between the UI and the entire application • If the UI is well designed and usable, then entire application appears usable

  10. What is the UI? (continued) • UI includes all aspects of the system that influence interaction with users • This includes: • Conceptual model (how UI objects correspond to real-world objects) • Input control, and their behavior • Means for navigation within and flow between screens • Integration among different applications • Visual design of the screens

  11. Technology Trends • Trends in technology have increased the need for improved UIs and UI design practices, such as mobile computing • New Interface technology alone does not produce usable interfaces! • GUIs can be less usable if they are poorly designed.

  12. User Interfaces: Code/Cost/Effort • Different statistics • UI is 47%-60% of the total code • The GUI is minimally 29% of the software development project budget • The GUI may take as much 40% of the development effort

  13. High Quality UIs are in Demand • A good UI is vital for a quality software product • UIs that do not work well make it impossible for user to access the functionality they require; • Therefore need UIs and systems that are: • Learnable, efficient, memorable • Not error prone • Satisfactory for the user

  14. Example for Bad UI

  15. Bad UIs lead to Major Problems • A $3 million application for an insurance company to be used by independent agents to support them in selling their company’s products. However, agents refused to use the application because the system was “un-learnable” and “unusable” • In a customer service organization, training on the system took 6 months, but employee typically stayed only 18 months in that department. • Extensive and expensive functionality in a Human Resource system was not used because users forget how to access it one week after training.

  16. Good Designs.. • Work the way the user thinks they should (intuitive) • Easier to learn and use than previous technology • More efficient than manual systems • Minimize user errors • Promote user satisfaction • Lower support costs • Transfer skills across applications • Fully utilize system functionality

  17. Good are UIs hard to build • Need abort, undo, redo • Real-time requirements • API & UI logic complexity • Hard to modularize (OO design helps)

  18. Where do we go from here? • Implementation • Java AWT • Java Swing • MFC

More Related