1 / 11

User Interface Design

User Interface Design. Jie Cai Tiem-Yen Liang Soodtida Tangpraphaphorn. What is a User Interface?. UI is the basic format allowing a user to operate a program Command Line (CLI) is text-based Graphical User Interface (GUI) relies on pictures

brandie
Download Presentation

User Interface Design

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. User Interface Design Jie Cai Tiem-Yen Liang Soodtida Tangpraphaphorn

  2. What is a User Interface? • UI is the basic format allowing a user to operate a program • Command Line (CLI) is text-based • Graphical User Interface (GUI) relies on pictures • Both user interfaces can be applied to biomedical informatics • But when?

  3. UI Components • Most common GUI configuration • WIMP – window, icon, mouse, pointer • CLI configurations can vary • Scripts • TUI – looks like graphic, but comprised of text characters

  4. Design Principles • Know your users! • Needs and goals • Special professional jargon • Computer literacy • Emulate a familiar system • Nobody loves an ugly GUI

  5. Human-Computer Interaction • Study of interactions between computers and people • Interdisciplinary field draws from informatics, psych, cog. sci., comp. sci., etc. • Clear understanding of HCI improves user-friendliness

  6. Clinical Contexts • Identify need • Clinical, administration, research • A precise definition of the problem • Tech solution is unacceptable if it misses the point • Technology addresses the need • Development driven by tech often fails • To do or not to do?

  7. Buy It? Develop It? • Off-the-shelf software • Less expensive • Expensive to customize • If it works well enough, BUY it! • Custom development • Expensive • Can we actually do this? • If it ain’t broke, don’t fix it

  8. When Things Go Awry • If the user is not comfortable with the interface, he/she will give up • Mistakes can be ¢o$t£y • Case example (Ch. 5)

  9. How to Make It All Better • User involvement • Model user habits indirectly • Direct user involvement better, but complicated • Medical information specialists • Mediate between users and software developers

  10. How to Make It All Better (con’d) • User testing • Prototyping • Spiral model • Evaluation • Case example (Ch. 5)

  11. THE END

More Related