1 / 23

Intro til TDT12, basert på kapittel 3 i avhandlingen «Model-based User Interface Design»

Intro til TDT12, basert på kapittel 3 i avhandlingen «Model-based User Interface Design». Information. Actions. People. Tools. The world is complex. Information. Actions. People. Tools. Differentiation and fragmentation. Semantic data modelling. Sociology, Psychology.

alka
Download Presentation

Intro til TDT12, basert på kapittel 3 i avhandlingen «Model-based 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. Intro til TDT12,basert på kapittel 3 i avhandlingen «Model-based User Interface Design»

  2. Information Actions People Tools The world is complex

  3. Information Actions People Tools Differentiation and fragmentation Semantic data modelling Sociology, Psychology Functional analysis BPR Workflow CSCW Task-basedUI design Systems engineering

  4. Designrepresentations • Usages • generating ideas • documentation • communication • analysis • execution: It is a pipe! • Engineering and designer traditions are different • bottom-up vs. top-down processes • human vs. machine understanding • Representations must be tailored for their use • Multiple representations are needed • Transitions between different representations must be supported

  5. Design representationclassification framework formality change formality perspective problem vs. solution abstract vs. concrete change detail granularity

  6. Task vs. dialogue/interaction

  7. High- vs. low-level

  8. Informal vs. formal

  9. Perspective and granularity dimensions

  10. Moving in the design representation space formality change formality perspective problem vs. solution abstract vs. concrete change detail granularity

  11. Domain modelling with RML persons = actor are part of the domain • Concepts andrelations • Set-based • Basis fortasks and actors • Natural translationto UML

  12. conceptual model Task modelling withTaskMODL • Hierarchical • Pre- and post-conditions • Sequence constraints • Control and dataflow • Actor structure • Integrated with domain model task structure

  13. Sequence relations • constraints for the super-/subtask part-of relation • a, b, c • a, b, d • c, a, b • d, a, b • Aggregation (RML) • Order • Sequence • Choice (RML) c or d canin addition occur in between a and b • cardinality (RML) provides additional constrains

  14. Specialisation • Generalisation/specialisation • Natural intepretation ofRML specialisation construct • Several usages: • (deterministic) choice • different observed practices • context dependent • generic structure

  15. Dialog modelling with DiaMODL • Based on Pisainteractors andHarel’s Statecharts • interactors, gates and connections • hierarchical states • transitions, events/actions, conditions • Composition in terms of • interactor structure • state hierarchy (and, or) • Parameters

  16. Parameterisation • Captures generic interactor structures • Reuse through instantiation of templates • Tailoring

  17. Abstract vs. concrete • Define function • Mapping fromabstract to concrete

  18. DiaMODL and JavaBeans • Definition of abstract function of JavaBean • Properties as parameters • Hybrid model editor and GUI-builder?

  19. Interactor-basedGUI-builder

  20. Model-based design patterns • Tool for moving from problem towards solution • Captures generic solution to reoccurring problem • Model fragments represents problem and solution • design pattern =template + design rationale?

  21. User vs. System ”plane”

  22. SE and UI model relations What is done? • Process/dataflow/workflow • STM/Petri Nets • Concepts/objects/data • Task • Dialog • Presentation How is it performed? How is information represented?

  23. Contributions revisited formality perspective Task-MODL Dia-MODL granularity

More Related