1 / 31

Advancements in Model-based and Model-driven Design of User Interfaces

This document explores the evolution of user interface design through Model-based User Interface Design (MBUID) and Model-Driven Engineering (MDE). It discusses the complexities of user interfaces in modern software engineering, focusing on the need for various abstraction levels to accommodate different devices and user contexts. The agenda includes an introduction to MBUID, current activities in the domain, and concluding remarks on the integration of abstract models with context-sensitive capabilities. It highlights the importance of designing reusable and adaptable interfaces in a rapidly evolving technological landscape.

zona
Download Presentation

Advancements in Model-based and Model-driven Design of User Interfaces

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. From Model-based to Model-driven Design of User Interfaces

  2. Agenda Introduction Model-based Design of User Interfaces (MBUID) Model-driven Engineering and MBUID CUP Current activities Conclusion

  3. Agenda • Introduction • Model-based Design of User Interfaces (MBUID) • Model-driven Engineering and MBUID • CUP • Current activities • Conclusion

  4. Introduction • Software engineering • Use models • Model driven Engineering (MDE) • User Interface • Prototyping • No or limited modeling • Problems • Multi-device / mobile user interfaces • Context-sensitive user interfaces

  5. Introduction • User interface (technology) is complex • Business applications • Mobile and embedded interfaces • Memory and processing constraints • Heterogeneous devices, environments • Cognitive constraints • Input and output constraints • Model-based design of user interfaces • On its own • Combine with MDE?

  6. Agenda • Introduction • Model-based Design of User Interfaces (MBUID) • Model-driven Engineering and MBUID • CUP • Current activities • Conclusion

  7. Model-based Design of User Interfaces • Reuse designs • Use different models for different aspects • Task model • Presentation model • Abstract (logical structure) • Concrete (“physical structure”) • Dialog model • Context model • User, Environment, Platform, Services

  8. Model-based Design of User Interfaces • Use multiples levels of abstraction • Tasks • Platform/modality independent (abstract) • Toolkit independent (concrete) • Code, xml, … (final) • Availability of tools: • Limited in scope • Research tools • Not always publicly available

  9. Agenda • Introduction • Model-based Design of User Interfaces (MBUID) • Model-driven Engineering and MBUID • CUP • Current activities • Conclusion

  10. Model-driven Engineering • Reuse of design: • Different levels of abstraction • Computation independent models • Platform independent models • Platform specific models • Transformations based upon • Marks • Platform information • Additional information • Code generation Abstract Concrete Context information

  11. Agenda • Introduction • Model-based Design of User Interfaces (MBUID) • Model-driven Engineering and MBUID • CUP • Current activities • Conclusion

  12. Context-Sensitive User Interface Profile • Goals • Integrate user interface models in • UML (2.0) • Software engineering (MDE) • Define platform independent / abstract layer • Tasks • Presentation • Integrate context • Broader than platform: environment, users, … • Context is more than information

  13. Context-Sensitive User Interface Profile • Usage of CUP • Platform independent models (CUP stereotypes) CUP (abstract) Patterns/CUP Specific models (concrete)

  14. Context-Sensitive User Interface Profile • UML Profile • Extend UML meta model • Enhance semantics • New notations • Extends UML 2.0 • Extensions for • Context • Abstract User Interfaces • Task specification

  15. CUP: Models • Activity model <> Task model: • Tasks • Temporal relations • Hierarchy • Presentation model • Abstract • Context model • Information • Gathering • Domain model

  16. CUP: Activity Model • Activity “flow” • Temporal relations between actions • Composed of activities • Stereotypes indicating kind of action • User • Interaction • System • Environment

  17. CUP: Activity model -- Example

  18. CUP: Activity model -- Presentation

  19. CUP: Presentation Model • Abstract model • Logical structure of deployed user interface • Omits platform specific information • Precedence specification • Stereotypes (user interface components) • Input component • Output component • Action component • Group component

  20. CUP: Presentation Model • Properties of user interface components • Datatype • Meta-data • Label • Explanation • Importance • … • Sequencing can be done through associations • Time • Space

  21. CUP: Presentation Model -- Example

  22. CUP: Activity model – Context

  23. CUP: Context model • Context information • Can be broad specification as in the context ontology • Gathering indicated by stereotypes • profiledContext - by humans • detectedContext - by system • Context processing • Indicate responsible components • contextCollector

  24. CUP: Context Model

  25. Agenda • Introduction • Model-based Design of User Interfaces (MBUID) • Model-driven Engineering and MBUID • CUP • Current activities • Conclusion

  26. Current activities – future work • Define transformations to platform specific models • Use patterns • Wizard • Each user interface component is a step • Add “buttons” for navigation • Form • Linear list of input components • Confirmation, cancellation at end

  27. Current Activities – future work • Define transformations to platform specific models • Use design knowledge • Integrate knowledge from prototyping • Integration with early prototyping tool (sketch-based) • Possibilities for consistency checks • XML-based: • XHTML (+ XForms) • UIML? • Use style • Directly to code?

  28. Agenda • Introduction • Model-based Design of User Interfaces (MBUID) • Model-driven Engineering and MBUID • CUP • Current activities • Conclusion

  29. Conclusions • Defined CUP • Platform independent models • Actions • Presentation • Context model • Information • Interaction • Working on • Transformations to platform specific models • Refinement of the profile

  30. Conclusions • Other contributions • Context-sensitive models • Decision nodes • Dialog model with transitions triggered by context • Integration “context toolkit” • Tool support • Distributed user interfaces • Adapting models for distributed user interfaces • Tool support

  31. Questions? ???

More Related