Separating Graphics from Application in the Design of User Interfaces

This paper discusses the design and applications of an object-oriented user interface management system (UIMS). Specifically, the Lockheed User Interface System (LUIS) is described. LUIS is based on a user interface model that includes declarative and procedural components. The package has been used by both non-programmers and programmers in several applications at Lockheed. Experiences derived from applications of the package are used to address several key issues in the UIMS field, such as procedural versus declarative specification, separation of the user interface from applications, UIMS flexibility, and UIMS support for design evaluation.

One of the most difficult aspects of creating graphical, direct manipulation user interfaces is managing the relationships between the graphical objects on the screen and the application data structures that they represent. Coral (Constraint-based Object-oriented Relations And Language) is a new user interface toolkit under development that uses efficiently-implemented constraints to support these relationships. Using Coral, user interface designers can construct interaction techniques such as menus and scroll bars. More importantly, Coral makes it easy to construct direct-manipulation user interfaces specialized to particular applications. Unlike previous constraint-based toolkits, Coral supports defining constraints in the abstract, and then applying them to different object instances. In addition, it provides iteration constructs where lists of items (such as those used in menus) can be constrained as a group. Coral has two interfaces: a declarative interface that provides a convenient way to specify the desired constraints, and a procedural interface that will allow a graphical user interface management system (UIMS) to automatically create Coral calls.

This article is focused on the system side of the multidisciplinary problem of building User Interface Management Systems (UIMS) for distributed and heterogeneous I/O devices. It presents a new architecture that decouples applications from their interfaces by using distributed synthetic file system interfaces (similar to /proc on UNIX) to export user interface elements and a new UIMS, O/live, following this approach. The UIMS has been in use for several years on a daily basis, in our laboratory and personal computers. It supports transparent distribution, replication, and migration of user interface elements among highly heterogeneous devices. Moreover, it is highly programmable without the need for special tools, which (a) facilitates experimentation and iteration for new human–computer interaction techniques and (b) enables the creation of orthogonal services to manipulate programmatically and independently the elements of the distributed UI. This article describes both the approach and the O/live UIMS and window system.

A user-interface management system (UIMS) is a system for developing and executing user interfaces. It provides design tools, human factors guidelines, definition languages, and run-time support for user-computer interfaces. The engineering information system (EIS) is the specification of a software framework providing services for accessing, controlling, managing, and exchanging design data and tools (into which organizations that use EIS place their own tools and databases). The authors describe the benefits of including a UIMS in a framework system such as EIS and present the EIS-UIMS concepts, model, and architecture. The two most important features of the UIMS are the separation of computational behavior from appearance and the provision of a script language that allows interface designers to represent the interface at a high level of abstraction, the user task level. The whole EIS program, including the UIMS activity, is currently in the design stage.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

The UofA* User Interface Management System (UIMS) generates graphical user interfaces based on a high-level description of semantic commands supported by the application. A main part of the UIMS, called Chisel, generates the presentation component of interfaces. Chisel selects interaction techniques, determines their attributes, and places them on the screen of the display device. While doing so it is capable of considering device properties, end user's preferences, and interface designer's guidelines. The aim of this paper is to discuss in detail the design and implementation of Chisel.

A UIMS (user interface management system) that is completely based on nonproprietary software has been developed. A central part of the UIMS are processes (mapper) that act as universal X-clients for each specified X-server. Mapper (graphic server) and applications (graphic clients) exchange requests by an event-driven interface. The communication protocol is free from any graphical information. The most powerful mapper client is a former interpreter that can be programmed to act as an equipment access server. The concept of a graphics server and a form interpreter allows the man-machine interface to be developed in a descriptive way. Appropriate to the level of abstraction in the UIMS, a specific UIDL (user interface definition language) had to be introduced.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

The so-called “User’s Conceptual Model” (UCM) now occupies a place of importance in the design of the user interface of interactive (computer graphics) systems. At the computer side of the interface there has been much excellent research done on (graphical) input tools, culminating in the ideas that now form the basis for the Graphical Kernel System (GKS) Version 7.2 input functions. On the user’s side of the interface there is still much to be done. It is envisaged that models of UCMs will form the basis of an Information/Knowledge/Data Base that is accessed by a “User Interface Management System” (UIMS), an integrated collection of software tools whose function it is to enable the specification, implementation and maintenance of a user-computer interface that is “user-oriented” and (self-)adaptive. The formal specification of such UCMs is a natural prerequisite for that of the user-computer dialogue. A formalism based on Minsky’s frame theory and an extension of the Vienna Development Method (VDM) is outlined in this paper. Taking “user” to mean “application programmer”, I present examples taken from a model of a UCM of GKS Version 7.2. Canonical encodings are presented in Ada 1 and canonical semantics in Anna, a language for annotating Ada programs.

An optical brain-machine interface (O-BMI) system using calcium imaging has various advantages such as high resolution, a comprehensive view of large neural populations, abilities such as long-term stable recording, and applicability to freely behaving animals in neuroscience research. The present study developed an ergonomic user interface (UI) design, based on a use scenario for an O-BMI system that can be used for the acquisition and processing of calcium imaging in freely behaving rodents. The UI design was developed in three steps: (1) identification of design and function requirements of users, (2) establishment of a use scenario, and (3) development of a UI prototype. The UI design requirements were identified by a literature review, a benchmark of existing systems, and a focus group interview with five neuroscience researchers. Then, the use scenario was developed for tasks of data acquisition, feature extraction, and neural decoding for offline and online processing by considering the sequences of operations and needs of users. Lastly, a digital prototype incorporating an information architecture, graphic user interfaces, and simulated functions was fabricated. A usability test was conducted with five neuroscientists (work experience = 3.4 ± 1.1 years) and five ergonomic experts (work experience = 3.6 ± 2.7 years) to compare the digital prototypes with four existing systems (Miniscope, nVista, Mosaic, and Suite2p). The usability testing results showed that the ergonomic UI design was significantly preferred to the UI designs of the existing systems by reducing the task completion time by 10.1% to 70.2% on average, the scan path length by 14.4% to 88.7%, and perceived workload by 12.2% to 37.9%, increasing satisfaction by 11.3% to 74.3% in data acquisition and signal-extraction tasks. The present study demonstrates the significance of the user-centered design approach in the development of a system for neuroscience research. Further research is needed to validate the usability test results of the UI prototype as a corresponding real system is implemented.

: Serpent (Software Engineering Rapid Prototyping Environment) is an example of the class of systems known as User Interface Management System (UIMS) . It uses the X window system to interact with the end user, and is useful both as a portion of a production system and as a separate prototyping tool. Serpent supports the development and execution of the user interface of a system. It provides an editor with which to specify the user interface and a run-time system which communicates with the application to get the data to display. The system then uses the specification previously output from the editor to decide how to display that data. This report provides a technical overview of Serpent, its components, the module used in specifying the user interface, and the editor used in constructing the user interface.

User interfaces are assuming an increasing importance within the design of a software product. This paper examines the various levels and components of window user interfaces and exposes their impact on software maintenance. It covers window systems, user interface toolkits, user interface management systems (UIMSs), dialogue separation and other user interface development concepts that will lead to more maintainable software. It also examines the research work on the testing of user interface software that is being pursued at the University of Durham.

Social Media platforms are increasing user engagements with their attractive User Interfaces (UI) design playing a crucial role in maintaining user involvement. Use of Emotional Intelligence (EI) into the UI transforming user interaction and engagement pattern significantly. With an emphasis on how design decisions affect user behaviour, this study explores the nuanced function of EIUIs (Emotionally Inteligence User Interfaces) in the context of social media. It specifically draws attention to the dangers of manipulative techniques like &amp;quot;dark patterns&amp;quot;-purposeful interface strategies intended to influence users to take actions they might not have otherwise taken-as well as the possibility of constructive involvement. By investigating these practices, the paper hopes to clarify the wider ethical consequences of interface design as well as the duty of platforms and designers to promote transparency, autonomy, and confidence in digital interactions. This paper aims to contribute to the discourse on user interface design by providing a comprehensive understanding of EIUIs&amp;apos; potential and pitfalls in the context of social media interactions. Additionally, this study focusses on finding information of the pattern of Emotionally Intelligent User Interfaces (EIUI) design to enhance user engagements emotionally and tend to take decisions and the impact of the design pattern in user experience.

: This document introduces current concepts and techniques relevant to the design and implementation of user interfaces. A user interface refers to those aspects of a system that the user refers to, perceives, knows and understands. A user interface is implemented by code that mediates between a user and a system. This document covers both aspects. The first chapter is an introduction to the psychology of human-computer interaction. It presents the theoretical models that have had a significant impact on the evolution of the field. These models offer a way to organize the design process and help understand the cognitive process involved in interacting with a computer. The rest of the document is concerned with the software design of user interfaces and shows how the principles established by the cognitive principles can be put into practice. Following a presentation on the abstractions involved in the organization of an interactive system, attention is then directed to the tools for constructing user interfaces: windowing systems, tool kits and user interface management systems.

An alternative solution for Indosport, considering the increasingly advanced smartphone development and also followed by the rapid growth of its users in Indonesia. The purpose of this study project is to produce a product in the form of a user interface (UI) and user experience (UX) design in helping to realize targeted mobile applications and not forgetting to apply the principles of visual communication design namely unity and variety, hierarchy, contrast, proportion and balance. The UI and UX design methods go through several stages of work in sequence: pre-production process, production process, and post-production. This design results in UI and UX designs that are equipped with user flow, interface designs, illustrations and prototypes. The main page of the Indosport mobile application is News, Activity, Calendar, and Profile which later on these pages there are several features that are different from the previous page. The making of this UI uses several visual languages such as medium close up, full shot, long shot, close up and medium long shot in the image section contained in the article as well as the depiction of field styles used to almost all visual UI elements. Using several principles in design, namely time to learn, speed of performance, rate of errors by users, retention over time, and subjective satisfaction. The resulting design forms will be distributed directly to the Research and Development division and the IT division from Indosport to be made a native.

PACE is an open system designed around a message-based communication protocol (Spook) and includes user interface (Ghost) and database management systems. Spook offers new and powerful mechanisms to implement different message-based protocol vocabularies in a vendor-independent way for interprocess communication and file storage. Ghost is a window system independent message-based server that uses Spook. It offers a full graphics editing process rather than an input-parsing utility. >

A User Interface Management System (UIMS) handles the dialogue between an application program and the end-user, and it provides tools for construction of the dialogue. Ideally, it should be possible to develop the dialogue part concurrently with the application part. This would speed up development and allow a user-centered dialogue design to be combined with a more formal application development. To what extent this is actually possible, depends on the interface between the UIMS and the application program.