Presentation is loading. Please wait.

Presentation is loading. Please wait.

University of Rostock 1 CADUI'96 - 5-7 June 1996 - FUNDP Namur Automatic user interface generation from declarative models Egbert Schlungbaum & Thomas.

Similar presentations


Presentation on theme: "University of Rostock 1 CADUI'96 - 5-7 June 1996 - FUNDP Namur Automatic user interface generation from declarative models Egbert Schlungbaum & Thomas."— Presentation transcript:

1 University of Rostock 1 CADUI' June FUNDP Namur Automatic user interface generation from declarative models Egbert Schlungbaum & Thomas Elwert Department of Computer Science University of Rostock Rostock, Germany

2 University of Rostock 2 CADUI' June FUNDP Namur Introduction 1 Overview on recent research works –model-based approach 2 The TADEUS approach –a small example to demonstrate some features 3 Conclusion

3 University of Rostock 3 CADUI' June FUNDP Namur Introduction (2) CAGUI - Computer Automated Generation of UI –Declarative models –Automatic user interface generation CADUI - Computer Aided Design of UI –model-based approach and UI development Support of UI-Designer or UI-Constructor ?

4 University of Rostock 4 CADUI' June FUNDP Namur Model-based tools (some) UIDE, HUMANOID, MECANO (I), ITS, GENIUS, JANUS ADEPT, TRIDENT MASTERMIND, MECANO (II), AME, FUSE, TADEUS EXPOSE, IDA

5 University of Rostock 5 CADUI' June FUNDP Namur Model-based approach

6 University of Rostock 6 CADUI' June FUNDP Namur Declarative models in model-based tools Task model Application model Dialogue model Presentation model Behaviour model Platform model User model Workplace model

7 University of Rostock 7 CADUI' June FUNDP Namur Use of declarative models UIDE UIDE application model ( application & interface actions, interaction techn. ) pre- and post-conditions are assigned to each action HUMANOID HUMANOID declarative modelling language with 5 parts: application semantics, presentation, behaviour, dialogue sequencing, side effects MECANO MECANO domain model TRIDENT TRIDENT task model, application model, presentation model GENIUS GENIUS existing application model, dialogue model JANUS JANUS OOA - application model

8 University of Rostock 8 CADUI' June FUNDP Namur Classification ( small ) classification on notation of central model systems with their own notation e.g., UIDE, HUMANOID, TRIDENT systems with notations well-known from software- engineering e.g., JANUS, GENIUS UI-ESE Interactive systems development  one possibility of integration: UI-E and SE for Interactive systems development

9 University of Rostock 9 CADUI' June FUNDP Namur Use of declarative models MASTERMIND MASTERMIND task model, presentation model, application model MECANO II MECANO II user-task model, domain model, presentation model, dialogue model, user model, design model AME AME application systems objects (all-purpose OO-model) FUSE FUSE task model, problem domain model, user model, dialogue and layout models

10 University of Rostock 10 CADUI' June FUNDP Namur Different architectures  UIDE, HUMANOID, MECANO, MASTERMIND  AME: OI, C++ GENIUS: ISA DM JANUS: ISA DM, OI TADEUS: ISA DM ISA DM:ISA Dialogue Manager, ISA GmbH OI:Open Interface, Neuron Data

11 University of Rostock 11 CADUI' June FUNDP Namur Automatic generation from models UIDEGENIUS presentation: data model of application - UIDE, GENIUS UIDE dynamic behaviour: application model extended with pre- & postconditions - UIDE JANUSMECANOAME presentation and dynamic behaviour: object or domain models - JANUS, MECANO, AME ADEPTTRIDENTMASTERMINDFUSE TADEUS presentation and dynamic behaviour: multiple models - ADEPT, TRIDENT, MASTERMIND, FUSE, TADEUS

12 University of Rostock 12 CADUI' June FUNDP Namur TADEUS TAsk-based DEvelopment of USer interface software task-oriented and model-based approach to User Interface development of interactive systems methodology supports continuous development process declarative models: task, user, problem-domain, dialogue integration of UI and Software engineering by means of tool integration

13 University of Rostock 13 CADUI' June FUNDP Namur Modelling steps in TADEUS Requirements of Interactive system: Task, Problem-domain, and User m. Dialogue design: Dialogue model 1. Dialogue view identification 2. Navigation dialogue between views 3. Processing dialogue inside views Automatic generation

14 University of Rostock 14 CADUI' June FUNDP Namur Declarative models and automatic generation in TADEUS Dialogue model: Dialogue graph + Interaction tables problem-domain model Interaction tables presentation: problem-domain model (object model) and refinements in dialogue model: Interaction tables task model Dialogue graph dynamic behaviour: task model and refinements in dialogue model: Dialogue graph

15 University of Rostock 15 CADUI' June FUNDP Namur Example: Task and Problem-domain m.

16 University of Rostock 16 CADUI' June FUNDP Namur

17 University of Rostock 17 CADUI' June FUNDP Namur Example: Identification of dialogue views

18 University of Rostock 18 CADUI' June FUNDP Namur Example: Dialogue model Dialogue graph and Interaction table

19 University of Rostock 19 CADUI' June FUNDP Namur Generation of UI code in TADEUS Steps of the automatic process: 1 Default layout description 2 Selection of AIO’s for each dialogue form 3 Mapping from AIO’s to CIO’s 4 Layout of CIO’s using defaults 5 Placing CIO’s inside the dialogue view 6 Creation the dynamics from Dialogue graph 7 User interface description file for Existing UIMS

20 University of Rostock 20 CADUI' June FUNDP Namur Step 1: Default layout description example: push-button, some attributes default_layout PushButton {.background_colourDark_Grey;.foreground_colourBlack;.fontButtonFont;.cursortypeActionCursor; }

21 University of Rostock 21 CADUI' June FUNDP Namur Step 2: Selection of AIO’s automatic, rule-based selection ( Dialogue designer only specifies dialogue form, type ) ifDialogueForm is ‘data input’ andtype is ‘1:n’ then set AIO ‘single selector’

22 University of Rostock 22 CADUI' June FUNDP Namur Step 3: Mapping from AIO’s to CIO’s automatic, rule-based mapping ifAIO is ‘multiple selector’ andnumber_of_items is ‘const’ andnumber_of_items less 7 then set CIO ‘group of check boxes’

23 University of Rostock 23 CADUI' June FUNDP Namur Step 4: Layout of CIO’s presentation values are assigned to CIO’s using: 1Dialogue designer’s specification in the Interaction table ( if there is one ) 2Default layout description

24 University of Rostock 24 CADUI' June FUNDP Namur Step 5: Placing CIO’s placing procedure is executed for each view it uses information on groups specified in the interaction tables identification of CIO’s to place: outside-in computation of position and size:inside-out defaults for orientation –of groups in a view:{vertical, horizontal} –of CIO’s in a group:{vertical, horizontal}

25 University of Rostock 25 CADUI' June FUNDP Namur Step 6: Creation of dynamics Generation pattern of Dialogue graph transitions

26 University of Rostock 26 CADUI' June FUNDP Namur View User model Interaction table and generation result

27 University of Rostock 27 CADUI' June FUNDP Namur View User model ( modified ) Interaction table and generation result

28 University of Rostock 28 CADUI' June FUNDP Namur Conclusion: Some questions to open discussion Support of UI-Designer or UI-Constructor ? –What kind of user interface does we have to the modelling languages ? (UI for dialogue designer) –What range of applications does the modelling languages support ? TADEUS’ answer: –graphical tools under development –application area: information systems (business application), TADEUS itself

29 University of Rostock 29 CADUI' June FUNDP Namur Conclusion: Some questions to open discussion Automatic generation - Does it really support ? –What is the relation between modelling effort and quality of automatic generation result ? –Which steps of user interface generation can be done in a fully automatic way ? TADEUS’ answer: –quality of generation result is good, but modelling effort is high (in the restricted application area)

30 University of Rostock 30 CADUI' June FUNDP Namur Conclusion: Some questions to open discussion Automatic generation - Does it really support ? –How to properly integrate the generated User Interface and the functional core ? –How to to update the declarative models, if the dialogue designer improves the generated UI by hand ? TADEUS’ answer: –the destination UIMS allows the independent development of the user interface and functional core –generation of different solutions from which the designer can select the best one

31 University of Rostock 31 CADUI' June FUNDP Namur Conclusion: Some questions to open discussion How to perform a re-generation of a User Interface when requirements change ? How to reverse engineer an existing User Interface to do a generation ?

32 University of Rostock 32 CADUI' June FUNDP Namur Thank you for your attention!


Download ppt "University of Rostock 1 CADUI'96 - 5-7 June 1996 - FUNDP Namur Automatic user interface generation from declarative models Egbert Schlungbaum & Thomas."

Similar presentations


Ads by Google