Professional Documents
Culture Documents
HCI 2017 Regular
HCI 2017 Regular
As you’ll make UX and UI decisions relatively early, this process will help
you to define precisely how you need to satisfy the expectations of your
audience. It will also clarify who you are and what you want to do,
ultimately helping you to communicate exactly what makes you stand out
from your competition.
----------------------------------------------------------------------------------------------------
3. Rapid Prototyping
(A) Try out new ideas very early,
(B) test, revise, test, revise,...,
(C) engage end-users, managers and customers
4. Software Support
(A) Increase productivity,
(B) offer constraint and consistency checks,
(C) facilitate team approach,
(D) ease maintenance
Software-engineering tools
Main Purpose: Build the final product
In earlier days, general purpose languages (e.g., Java, C++) were used
to build UIs from scratch
Today, this is supported through software tools, APIs and Frameworks,
etc.
A classification of UI building tools:
Layer 1: Windowing Toolkit
Layer 2: GUI Toolkit
Layer 3: Application Framework/Specialized Languages
Layer 4: Application Level
General Trend:
Lack of modifiability led to building architectures that separate the UI
from the application logic (e.g., MVC-Pattern), also supports cross
platform development
Windowing-system layer
≈ no widgets available, need to “draw” manually, no event support
encapsulated in objects
Low-level work required
Especially useful/important for new platforms or if resources are
expensive/limited
Build the basis for higher-level layers
Pros: Performance, very flexible
Cons: Requires extensive programming, long learning time, offers little
support for interactive tools, no visualization tools
GUI-toolkit layer
≈ provides software libraries and widgets (e.g., frames, dialog boxes,
scrollbars) including event encapsulation as building blocks
Pros: Abstraction, shorter development times, great flexibility, often
based on general-purpose languages (makes it easier to combine UI with
application logic)
Cons: Possibly high learning times, building and maintenance time is still
high, no support for consistency, experienced programmer needed
Example for Toolkits: ILOG Views, Gtk, Qt, Java (AWT, Swing, SWT),
.Net GUI toolkit)
Application layer
≈ Interface Generators, also called: Model-Based Systems or UI
Management Systems
Visual tools, that allow for most parts of an application to be built with
one tool and without coding
Only available for a small class of applications (e.g., DB front-ends) or
research prototypes
----------------------------------------------------------------------------------------------------