System: Mecano

1
Model-Based Automated Generation of User
Interfaces Angel R. Puerta, Henrik Eriksson, John
H. Gennari, and Mark A. Musen Seattle, August
1994 Medical Computer Science Group Knowledge
Systems Laboratory Department of Medicine and
Computer Science Stanford University Stanford,
CA, 94305-5479
System Mecano Presenters Baolinh Le, Bryce
Carder Course Knowledge-based User
Interfaces Date April 29, 2003
2
Presentation Overview

• Introduction
• Mecanos approach
• Related works
• Overview of Mecano
• Domain models
• Generation of dialog specification from domain
  models
• Generation of domain-specific graphical editors
• Participatory layout design and design revision
• Analysis Conclusions

3
Introduction

• Current tools are able to generate the static
  layout of an interface from the application's
  data model
• Data model is shared between the interface
  design and the target application design.

4
Mecano Approach

• Use domain models instead of data models to
  generate both the static layout and the dynamic
  behavior of an interface.
• A domain model is a high-level knowledge
  representation that captures all the definitions
  and relationships of a given application domain.
• Dynamic interface behavior can be generated, and
  that are sharable across a range of applications.
  
• Does not require any dialog specification editing
  and can generate complete dynamic behavior
  specifications even for large interfaces with
  hundreds of components.

5
Related Work

• There are three types of systems related closely
  to Mecano approach
• Systems that use textual specifications to
  generate dialogs Ex ITS 89
• Systems that combine the use of data models and
  high-level dialog specifications Ex UIDE 92
• Systems that directly manipulate an interface
  model to produce an interface Ex HUMANOID 93

6
Mecano Overview
7
Domain Models
8
Generation of dialog specification from domain
models
9
Generation of dialog specification from domain
models
10
Generation of dialog specification from domain
models

• High-level dialog defines all interface windows,
  assigns interface objects to windows, and
  specifies the navigation schema among windows in
  the interface.
• Low-level dialog defines specific dialog elements
  (widgets) to each interface object created at the
  high level and specifies how the standard
  behavior of the dialog element is modified for
  the given domain.
• The dialog for window navigation is established
  during high-level dialog design but it can be
  refined, or augmented, at low-level design time.

11
High-Level Dialog Generation

• The procedure to generate a high-level dialog
  design is as follows
• Each class in the hierarchy is assigned a window
• Window navigation is established by searching
  the class hierarchy for links indicated by the
  allowed classes facet in the domain model.
• Each window is assigned one interface object per
  slot in the class. After generation, the
  developer has the option of customizing the
  interface by splitting windows multiple objects
  into two or more windows.

12
Low-Level Dialog Generation

• Elements are generated by examining the facets
  (properties) defined for each slot in the domain
  model.
• The process is as follows
• Each interface object defined at high-level
  design time is assigned a dialog element (widget)
  by examining the facets of the corresponding slot
  in the domain model.
• Ex type string text field type Boolean
  check-box stringcardinality multiple-list
  browser.
• Each dialog element may be assigned actions
  beyond the standard behavior of the dialog
  element by examining the facets of the
  corresponding slot in the domain model.
• Ex disabling editing in other dialog elements
  updating values in other dialog elements after a
  user input action.

13
Generation of domain-specific graphical editors

• Mecano can generate flow charts from a domain
  models
• Consider the below slot information for the
  class Protocol

• When intelligent dialog designer examines this
  slot during low-level dialog design, it assigned
  a graphical editor as the dialog element for that
  slot due to the type procedure defined for that
  slot. It also defines three graphical objects to
  be used during editing (as xrt, chemo, drug)

14
Participatory layout design and design revision

• In Mecano, there are two types of revisions
  layout and dialog.
• The intelligent designer tool uses a layout
  algorithm to produce a preliminary layout of the
  interface objects.
• Mecano is able to involve the end user in the
  process of custom-tailoring a layout.
• Custom-tailoring information is kept on a
  database so that if the interface needs to be
  regenerated, the customization can be reapplied
  to the newly generated interface.
• Substantial revisions of the domain model
  invalidate the information on the customization
  database.
• Dialog design customizations can be made by
  editing directly the interface model.
• Regeneration of the interface is not required.
• Changes for additional dialog elements must be
  made to the domain model to define needed slots
  and classes.
• Regeneration of the interface is required.

15
Analysis Conclusions

• Mecano allows generation of both static layout
  and dynamic behavior of domain-specific, form-
  and graph- based interfaces
• Ex medical treatment, elevator configuration
• Mecano uses the applications domain model, which
  includes the applications data model
• Allow automation capabilities over systems
  utilizing only data model
• Support of participatory layout design involving
  end users of the applications and support for the
  iterative design without duplication of work.

16
Future Work

• Concern with how to generate complex sequences of
  actions at low-level dialog design time
• Working on the run-time system of Mecano to
  implement new types of widgets
• Working on developing task models as components
  of generic interface model.
• Overall, Mecano provides a framework for
  assisting the development of interfaces and for
  the study of interface models and the
  relationships between domain characteristics and
  user interface presentation and dialog.