|SVG-based Knowledge Visualization (for Digital Pen Interaction) 2012, graduate student, Miloš Kaláb|
|Interaction study: Haptic Mobile Interfaces, 2008, graduate student (Dipl., HBK Saar): Mikhail Blinov|
Graph-Based Visualization of RDF Soccer
Data and Interaction
Possibilities on a Handheld, 2007, graduate student (Msc., University Koblenz-Landau): Philipp Heim
Usability Guidelines for Use Case Applications serves as an introduction to the general topic of usability, i.e., how user-friendly and efficient a THESEUS prototype is. In these guidelines, we emphasize the importance of usability testing, particularly during the development of a given THESEUS prototype. We discuss the many advantages of testing prototypes and products in terms of costs, product quality, and customer satisfaction. Usability testing can improve development productivity through more efficient design and fewer code revisions. It can help to eliminate over-design by emphasizing the functionality required to meet the needs of real users. Design problems can be detected earlier in the development process, saving both time and money. In these Guidelines we provide a brief overview of testing options, ranging from a cognitive walkthrough to interviews to eye tracking. Different techniques are used at different stages of a product’s development. There are many techniques that can be applied to ensure the usability of prototypes, which no single technique alone can ensure, however. Usability is a process with iterative steps, meaning the cycle is repeated but in a cumulative fashion, similar to software development.
In order to test, a prototype must be available and we devote some time in the Guidelines to an overview of different tools and ways of building the necessary prototypes. We also describe some options such as paper prototyping, prototypes from Visio, PowerPoint, HTML, Flash and others, and working prototypes (Java, C++, etc.) before addressing the issue of the actual tests as such. Before any testing is conducted, the purpose of the test should be clarified. This will have considerable impact on the kind of testing to be done. A test plan should also be written before the start of the test and consider several different aspects including, for instance, the duration of the test, where it will take place, or who the experimenter will be. A pilot test is also recommended to avoid misunderstandings and other problems during the actual test. In this context, the Guidelines also discuss other important aspects such as the budget, room set-up, time, and limitations of the experimenter and test subjects themselves.
an overview of some of the projects THESEUS is concerned
with in the
usability, we supply explicit recommendations that
result in proposed
for use cases in the Guidelines.
THESEUS program consists of six use
cases: ALEXANDRIA, CONTENTUS, MEDICO, ORDO, PROCESSUS,
and TEXO. In
come up with the different testing scenarios, each of
and testing recommendations, we first extracted some
from the different use cases in different user settings:
those who will use the system, where they will use the
system, and what
will do with the system. After considering the results,
THESEUS program works with seven different scenarios. We
tree that leads to specific recommendations for
designing and testing
prototypes for each of the different scenarios and user
recommendations concerning various input methods, the
design, and the
itself have also been included in the Guidelines.
emphasize what we find important for the design and
testing of each of
seven testing scenarios. We address, for instance, the
(keyboard, mouse, speech, etc.), according to the type
of test subject
administrator or mobile user), or also which prototype
could be used
usability test. The Guidelines
with an extensive list of
recommended further information sources.
Guidelines, we implemented an abstract container
Semantic Interface Elements (SIEs)
for the representation and activation of multimedia elements visible on the touchscreen. More information about the design and implementation of this combined mobile and touchscreen-based multimodal Web 3.0 interface can be found in Sonntag, Deru and Bergweiler (2009) or visit Comet.
for mobile business applications: A multimodal dialogue system
business expert to intuitively search and browse for services in
real-world production pipeline. We implemented a distributed
client-server dialogue application for natural language speech
input and speech output generation (Porta, Sonntag and Neßelrath, 2009).