1 / 17

UIs for Embedded Systems

UIs for Embedded Systems. By Prof. Dr. Karin Coninx and Drs. Jan Van den Bergh. Overview. Introduction Approach UIs for Embedded Systems Inventory of UI Realization Systems Evaluations and Results Conclusions Future work. Introduction.

osanna
Download Presentation

UIs for Embedded Systems

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. UIs for Embedded Systems By Prof. Dr. Karin Coninx and Drs. Jan Van den Bergh

  2. Overview • Introduction • Approach • UIs for Embedded Systems • Inventory of UI Realization Systems • Evaluations and Results • Conclusions • Future work

  3. Introduction • task 4.1 "Evaluation of Existing UI Realization Systems" • Goals • Orientation with regard to UIs in the context of ES • Overview of existing systems • Insight in problems • Practical work as part of the evaluation • UI or GUI

  4. Approach • Information sources: • Literature • Internet and related media • ESC Europe conference • Seminar on Windows CE by Prof. M. Timmerman • Company visits (user group) • Inventory of GUI realization tools • Evaluation through "Hands on" Experience

  5. User Interfaces for Embedded Systems • Not a lot of information in literature • Programming techniques borrowed from mainstream UI • Usability engineering and safety issues • Current interest: Graphics, Java • Downscaled desktop GUI? • Programming: OK, expertise available • Desktop metaphors not always usable! • UI in ES: who’s responsible? • Design by product management or software developer • Realization: lack of UI expertise of developers

  6. User Interfaces for ES (continued) • Problems • Decision to use a third party API or tool • Lack of tool knowledge • Limited experience with design and development of GUIs • Frequently changing definition of specs

  7. Inventory of GUI tools • Two approaches • Adapt desktop controls and APIs • Design controls and APIs from scratch • Different levels of tool support • Only API • GUI builders (visual UI building, code generation) • Prototypers

  8. Evaluations • Local vs. Remote interfaces • Attention points when selecting the UI systems • Cover a range of UIs for ES • OO programming, C++ and Java • MFC based for Windows CE (C++) • Personal/Embedded Java, VisualAge MicroEdition • UI realization systems from several vendors • Windows CE from Microsoft • Java tools from Sun and IBM • Windows CE: promising RTOS?

  9. Evaluations (continued) • Choice of case • Not too complex, realize in different UI tools/systems • Display of data (output) • Change of parameters (input) • Remote interface possible • Signal generated and displayed,depending on function and parameters

  10. Evaluations (continued) • Architectural/Conceptual model of the case

  11. Evaluations (continued)

  12. Evaluations (continued)

  13. Evaluations (continued) • Customizable look-and-feel • PersonalJava: Truffle provides AWT implementations • Standard • Touchable • VisualAge: GUI design tool MicroView (MVC based) • Windows CE: limited through dialogs

  14. Evaluations (continued) • Networked user interfaces • Swing? • Requires Java2 or JFC1.1 • Platform independent look-and-feel • Allows component oriented design • Allows customization • Large memory consumption • Dynamic change of look-and-feel • XML • Structured document/data description standard • Compagnion standards provide stylesheets, extended linking, ...

  15. Conclusions • Evaluations • Test application provided feeling with UI for ES • Existing UI realization systems • Are promising • Become increasingly mature

  16. Conclusions (continued) • Trends • Use of downscaled desktop techniques (and metaphors?) • Move towards Java and OO for UI design • Networking • More prominent UI in ES (e.g. remote interface) • Emerging application domains (e.g. wireless services)

  17. Future work • Components in UI… • Integrate HMI (HCI) in development methodology,in collaboration with the product design team

More Related