Name : K.

Surya Prakash
Reg.no :191611075
subject name : Human Computer Interaction-Rudiments
Subject code : CSE0105
 UIMS

User Interface Management Systems (UIMS)

Also referred to as User Interface Development Systems (UIDS).

Our notion of UIMS entails:

• Architecture: a conceptual architecture for the structure of an interactive
system with a separation between application semantics and presentation.
• Implementation: techniques for implementing an application separated from
the presentation and supporting communication between them.
• Follow-up: techniques for managing, implementing and evaluating a run-time
interactive environment.
 UIMS

User Interface Management Systems (UIMS)

Three components of an interactive system:

• presentation
• application
• dialog control (for handling/regulating communication between the application
and the presentation)

Recall the two basic ways to program the flow of control within an application
in a client-server architecture: a) Read-evaluation loop. b) Notification based.

Note that in b) the dialog control is external to the application.

Since UIMS often promote the separation between the application and the
presentation, most of them fall into b). They do not, however, all use
callbacks (see client-server architecture).
 User Interface Management Systems
(UIMS)
• The set of programming and design techniques which provide
more development support for interactive system design beyond
the toolkits.
• Examples of UIMS are Serpent & Picasso
• The UIMS should support:
• Conceptual Architecture:
• for the structure of an interactive system which concentrates on a separation
between application semantics/logics and presentation;
• Techniques:
• for implementing a separated application and presentation and preserving the
intended connection between them;
• Support techniques:
• For managing, implementing and evaluating a run-time interactive environment
 Main UIMS Conceptual Architectures

The Main UIMS Models

Seeheim Model:
• Presentation (has both input and output).
• Application interface (the view of the application semantics).
• Dialog control (for communication between the above two).

Model-View-Controller (MVC) framework (e.g. within Smalltalk, Java Swing)

• Controller handles input.
• View handles output.
• Model represents application semantics.

Presentation-Abstraction-Control (PAC) model:

• Presentation (has both input and output).
• Abstraction represents application semantics.
• Control handles communication and maintains consistency between
Presentation and Abstraction.
 Main UIMS Conceptual Architectures

Seeheim Model

• Presentation (for the appearance of the user interface – handles both input
and output for the user).
• Application interface (the view of the application semantics).
• Dialog control (for communication between the above two).
 UIMS: Conceptual Architecture

lexical syntactic semantic

Functionality
Dialogue
USER
USER Presentation (application APPLICATION
Control
interface)

switch

Seeheim Model
UIMS: Conceptual Architecture

view

model

controller

MVC: model - view - controller

UIMS: Conceptual Architecture

Multi-Agent Architecture

PAC
presentation - abstraction - control
 HCI
Development Support

Main UIMS Conceptual Architectures

Seeheim Model

Some concerns with the Seeheim model:

• It did not provide any real directions for how future UIMS should be built. The
upper component (bypasser) was intended to show that for efficiency
reasons, an explicit dialog control could be bypassed. The bypasser has to
do with implementation concerns and thus should not appear in the
conceptual architecture (i.e. the figure).
• It cannot readily take advantage of an oo (architectural) approach.
Main UIMS Conceptual Architectures