54,579 research outputs found
Menu-Based User Interface Systems: Theory and Practice
The thesis discusses the menu selection technique, which is one of the most commonly used interaction techniques in Human-Computer Interfaces, and continues to flourish because of its simple interaction format and its adaptability to the many diverse applications. The ease of use of the technique, particularly by novices, contributes significantly to the widespread acceptance of menu-based user interface systems, despite their inherent disadvantages and drawbacks. Chapter One surveys the issues concerning the design and use of menu-based interfaces, and addresses particularly the navigational problems encountered by users of menu selection systems, identifying various navigational aids which help overcome these problems. The chapter concludes with a comparison between menu-based interfaces and other interface styles (command language, natural language and form-filling). Chapter Two describes the practical work of the thesis which consists of implementing a particularly demanding menu-based interface example involving multiple menu selections using four different dialogue specification systems. The implementation is discussed mainly from a menu system designer's view. Strategies to solve or address the multiple selection mechanism problem as well as some the navigational concepts discussed in chapter one are devised and used within each the four target systems. Also, some other related user interface design issues are reported in chapter two. The principal aim of the work is to investigate the difficulties a dialogue designer may face in attempting to implement a common type of menu-based interface using various delivery systems, all of which claim in varying degrees to support menu-based interactive styles. In the final chapter conclusions are drawn from the practical work concerning desirable menu support features in user interface implementation systems, and issues requiring further investigation are identified
Data management study. Appendix P - Contractor data requirements related project interfaces /RP/ Final report
Technical, administrative, and managerial data documentation by contractors on interfaces between Voyager project and related space program
Opportunities in Software Engineering Research for Web API Consumption
Nowadays, invoking third party code increasingly involves calling web
services via their web APIs, as opposed to the more traditional scenario of
downloading a library and invoking the library's API. However, there are also
new challenges for developers calling these web APIs. In this paper, we
highlight a broad set of these challenges and argue for resulting opportunities
for software engineering research to support developers in consuming web APIs.
We outline two specific research threads in this context: (1) web API
specification curation, which enables us to know the signatures of web APIs,
and (2) static analysis that is capable of extracting URLs, HTTP methods etc.
of web API calls. Furthermore, we present new work on how we combine (1) and
(2) to provide IDE support for application developers consuming web APIs. As
web APIs are used broadly, research in supporting the consumption of web APIs
offers exciting opportunities.Comment: Erik Wittern and Annie Ying are both first author
Attempto - From Specifications in Controlled Natural Language towards Executable Specifications
Deriving formal specifications from informal requirements is difficult since
one has to take into account the disparate conceptual worlds of the application
domain and of software development. To bridge the conceptual gap we propose
controlled natural language as a textual view on formal specifications in
logic. The specification language Attempto Controlled English (ACE) is a subset
of natural language that can be accurately and efficiently processed by a
computer, but is expressive enough to allow natural usage. The Attempto system
translates specifications in ACE into discourse representation structures and
into Prolog. The resulting knowledge base can be queried in ACE for
verification, and it can be executed for simulation, prototyping and validation
of the specification.Comment: 15 pages, compressed, uuencoded Postscript, to be presented at EMISA
Workshop 'Naturlichsprachlicher Entwurf von Informationssystemen -
Grundlagen, Methoden, Werkzeuge, Anwendungen', May 28-30, 1996, Ev. Akademie
Tutzin
Specification of multiparty audio and video interaction based on the Reference Model of Open Distributed Processing
The Reference Model of Open Distributed Processing (RM-ODP) is an emerging ISO/ITU-T standard. It provides a framework of abstractions based on viewpoints, and it defines five viewpoint languages to model open distributed systems. This paper uses the viewpoint languages to specify multiparty audio/video exchange in distributed systems. To the designers of distributed systems, it shows how the concepts and rules of RM-ODP can be applied.\ud
\ud
The ODP ¿binding object¿ is an important concept to model continuous data flows in distributed systems. We take this concept as a basis for multiparty audio and video flow exchanges, and we provide five ODP viewpoint specifications, each emphasising a particular concern. To ensure overall correctness, special attention is paid to the mapping between the ODP viewpoint specifications
The Ubiquitous Interactor - Device Independent Access to Mobile Services
The Ubiquitous Interactor (UBI) addresses the problems of design and
development that arise around services that need to be accessed from many
different devices. In UBI, the same service can present itself with different
user interfaces on different devices. This is done by separating interaction
between users and services from presentation. The interaction is kept the same
for all devices, and different presentation information is provided for
different devices. This way, tailored user interfaces for many different
devices can be created without multiplying development and maintenance work. In
this paper we describe the system design of UBI, the system implementation, and
two services implemented for the system: a calendar service and a stockbroker
service
IVOA Recommendation: IVOA Support Interfaces
This document describes the minimum interface that a (SOAP- or REST-based)
web service requires to participate in the IVOA. Note that this is not required
of standard VO services developed prior to this specification, although uptake
is strongly encouraged on any subsequent revision. All new standard VO
services, however, must feature a VOSI-compliant interface.
This document has been produced by the Grid and Web Services Working Group.
It has been reviewed by IVOA Members and other interested parties, and has been
endorsed by the IVOA Executive Committee as an IVOA Recommendation. It is a
stable document and may be used as reference material or cited as a normative
reference from another document. IVOA's role in making the Recommendation is to
draw attention to the specification and to promote its widespread deployment.
This enhances the functionality and interoperability inside the Astronomical
Community
- …