Interface Development Process Research Articles

ЗНАХОДЖЕННЯ КОМПОНЕНТІВ КОРИСТУВАЦЬКОГО ІНТЕРФЕЙСУ ЗА ДОПОМОГОЮ МАШИННОГО НАВЧАННЯ

Modern technologies and products are becoming more complex and multi-component, which requires the creation of a convenient and intuitive user interface. One way to ease the interface development process is to use machine learning techniques to find user interface components and generate ready-made templates for subsequent software development. There are several approaches and methods that can be used to detect UI components on a finished design using machine learning: - Image segmentation; - Layout Analysis; - Component Recognition Libraries; - Neural networks; This mechanism will allow in the future to be used in various areas related to the development and design of the user interface.

Students' Experiences and Usability Evaluation in Interactive Digital Interface Development Process

In this research, it was aimed to determine student experiences in the design process of interactive digital interfaces developed with Figma and to evaluate students’ works developed within the scope of the “Digital Interface Design” course by students and lecturer. The case study design was used in the research. While determining the participant group of the study conducted with 57 students, convenient sampling method, which is one of the non-random sampling types was used. Implementation activities lasted eight weeks. At the end of the implementation process, each of the student was expected to develop interactive mobile application or website interfaces. The qualitative data of the study were analyzed by content analysis method, while the quantitative data were analyzed descriptively. According to findings, most of the mobile application and website interfaces designed by students were evaluated as good usable, and a certain part as excellent usable.

A method for defining rule elements based on civil aircraft interface development process

In the process of civil aircraft design and development, interface definition is a very important and complex process element. In this paper, a rule element definition method based on civil aircraft interface development process is proposed, and the rule element definition to support the interface development process is given. Rule elements provide useful input on structure and content for civil aircraft interface definition activities, especially for low-level interface definition activities. All levels of an interface definition can be related to rule elements, but lower-level interface definitions have the greatest amount of data, and most of the definitions are done in lower-level interfaces. For the design activities of the stakeholders in the low-level interface development process, these rule elements are equivalent to the formulation of multi-dimensiona and unified standards and requirements, so that the stakeholders of interface definition (main manufacturer and suppliers at all levels) can carry out coordinated interface development activities under such standards and requirements.

A Context-Aware Approach for Generating User Interfaces Based on Usability Requirements

The advent of mobile devices has raised new challenges. One main challenge concerns the quality of the dialogue between human beings and interactive systems. This dialogue pertains principally to the user interface since it is the visible part of the systems to humans. Developing a usable interface is crucial for the success or failure in the actual use of mobile applications. One of the important research issues for the effective use of user interfaces is regarding how to conduct usability requirements in ubiquitous environments. The present article addresses this issue taking into account context-awareness. The authors propose a methodology in this direction that considers the human factors while designing user interfaces. Particularly, the approach focuses on how to select consistent usability requirements and how to incorporate them into user interface development process considering the context of use. An illustrative case study is presented. Finally, an experimental platform for interface evaluation is proposed.

Database semantic model application in natural language user interface development process

Database semantic model application in natural language user interface development process

Usability Evaluation of Electronic Health Record System around Clinical Notes Usage-An Ethnographic Study.

Background A substantial gap exists between current Electronic Health Record (EHR) usability and potential optimal usability. One of the fundamental reasons for this discrepancy is poor incorporation of a User-Centered Design (UCD) approach during the Graphical User Interface (GUI) development process. Objective To evaluate usability strengths and weaknesses of two widely implemented EHR GUIs for critical clinical notes usage tasks. Methods Twelve Internal Medicine resident physicians interacting with one of the two EHR systems (System-1 at Location-A and System-2 at Location-B) were observed by two usability evaluators employing an ethnographic approach. User comments and observer findings were analyzed for two critical tasks: (1) clinical notes entry and (2) related information-seeking tasks. Data were analyzed from two standpoints: (1) usability references categorized by usability evaluators as positive, negative, or equivocal and (2) usability impact of each feature measured through a 7-point severity rating scale. Findings were also validated by user responses to a post observation questionnaire. Results For clinical notes entry, System-1 surpassed System-2 with more positive (26% vs. 12%) than negative (12% vs. 34%) usability references. Greatest impact features on EHR usability (severity score pertaining to each feature) for clinical notes entry were: autopopulation (6), screen options (5.5), communication (5), copy pasting (4.5), error prevention (4.5), edit ability (4), and dictation and transcription (3.5). Both systems performed equally well on information-seeking tasks and features with greatest impacts on EHR usability were navigation for notes (7) and others (e.g., looking for ancillary data; 5.5). Ethnographic observations were supported by follow-up questionnaire responses. Conclusion This study provides usability-specific insights to inform future, improved, EHR interface that is better aligned with UCD approach.

Evaluation of a surgical interface for robotic cryoablation task using an eye-tracking system

Computer-assisted navigation systems coupled with surgical interfaces (SIs) are providing doctors with tools that are safer for patients compared to traditional methods. Usability analysis of the SIs that guides their development is hence important. In this study, we record the eye movements of doctors and other people with no medical expertise during interaction with an SI that directs a simulated cryoablation task. There are two different arrangements for the layout of the same SI, and the goal is to evaluate whether one of these arrangements is ergonomically better than the other. We use several gaze related statistics some of which are employed in an SI design context for the first time. Even though the performance and gaze related analysis reveals that the two arrangements are comparable in many respects, there are also differences. Specifically, one arrangement leads to more saccades along the vertical and horizontal directions, lower saccade amplitudes in the crucial phase of the task, more locally clustered and yet globally spread viewing. Accordingly, that arrangement is selected for future use. The present study provides a proof of concept for the integration of novel gaze analysis tools developed for scene perception studies into the interface development process. Two arrangements for a surgical interface (SI) are developed using design principles.Doctors & laypeople perform SI-guided simulated cryoablation while gaze is recorded.Saccades in cardinal directions are more likely with one arrangement.Spatial fixation distributions at different temporal scales support the same arrangement.Design and evaluation with eye movements measures produce better SIs.

Identifying common activities in the graphical user interface development process and their integration into the software-system development life cycle

We identify a suite of activities in the development process of Graphical User Interfaces (GUI) and include them as part of an approach to a generic model for the GUI Development Process (GDP). This work contributes with: (1) the identification of common activities of previous GDPs, (2) the definition of an approach to a generic GDP limited to its phases and activities, and (3) the integration of such a generic GDP with any software-system development life cycle (SDLC), illustrated with the Spiral SDLC. We show this work is useful by a) highlighting the advantages of our proposal over other methodologies for GDP in Human-Computer Interaction (HCI), b) showing one example of the integration of the GDP into a SDLC, and c) showing the usefulness of our approach in a case example.

Interface Design and Development of ETL in the Telecommunications Business Data Warehouse Plat Form

. This paper describes the design of the telecommunications data warehouse interface part and development process of the ETL. Use of the data warehouse organization and storage method, carry on data analysis and business decisions effectively for the telecommunications services.The interface mainly undertakes the tasks is standardizing transfer mode of data among the various production systems. ETL's process is the key of the whole data warehouse. In the Text, described in detail for Its function framework and software deployment, and according to the data interface specification to describe the Interface environment configuration. Through the establishment of this platform, the data of the Production systems can be harmonized. And provide a strong background support for development and display of the front, benefit the policy-making level more accurate grasp development situation of the enterprise.

Towards analytical evaluation of human machine interfaces developed in the context of smart homes

Designing human machine interfaces that respect the ergonomic norms and following rigorous approaches constitutes a major concern for computer systems designers. The increased need on easily accessible and usable interfaces leads researchers in this domain to create methods and models that make it possible to evaluate these interfaces in terms of utility and usability. Two different approaches are currently used to evaluate human machine interfaces, empirical approaches that require user involvement in the interface development process, and analytical approaches that do not associate the user during the interface development process. This paper presents a study of user performance on two principal tasks of the contextual assistant’s interface, developed in the context of smart homes, to assist persons with cognitive disabilities. We use three different methods to analyze and evaluate this interface, focusing basically on time of execution. Two of the models developed are based on cognitive models, which are ACT-R and GOMS and the third one is based on the Fitts’ Law model. The results show that, all models give a good prediction of user performance, even if the cognitive models show better accuracy of the user performance. Furthermore, they provide a better insight into cognitive abilities required to interact with the interface.

A methodological approach for user interface development of collaborative applications: A case study

In the last few years, the production of systems which support learning and group work has been high. However, the design and development of these types of systems are difficult, mainly due to the multidisciplinarity involved. Furthermore, the Graphic User Interface (GUI) of an application is receiving greater attention, since it can be decisive in determining if the application is accepted or rejected by users. Model-based design is a widespread technique in the user interface development process. While reviewing approaches that deal with the modeling and design of user interfaces supporting collaborative tasks, we have detected that there is no proposal that links interactive and collaborative issues. We have introduced a methodological approach to solve this shortcoming. This approach is called CIAM ( Collaborative Interactive Application Methodology) and it is composed of several stages in which conceptual models are created using CIAN ( Collaborative Interactive Application Notation). These models start by modeling the organization in which the application will be used, as well as the tasks that must be supported. In the initial stages, the organization and the collaborative tasks are modeled using high-level specifications. In the following stages, the level of detail increases and, finally, the interaction between the individual users and the application is modeled using ConcurTaskTrees (CTT) notation. The interaction model acts as a bridge between the design and the implementation of the Graphic User Interface. In this paper we present our methodological approach and an example of applying this method for user interface design of collaborative and interactive applications.

USER-CENTRED DEVELOPMENT OF AN USER INTERFACE FOR MOBILE DEVICES IN AUTOMATION

Mobile devices become more and more powerful. But the advantages of such devices can only be used if the interface between the user and the technical functions is designed well. This paper describes the iterative and user-centered user interface development process for such a user interface for two different user groups (technician and manager) in the domain of service and maintenance in industrial automation. At the end of the iterations a usability test showed that a user interface on the basis of this concept is a useful support for the service- and maintenance personnel during their daily work.

Unified user interface development: the software engineering of universally accessible interactions

In the information society, the notion of “computing-platform” encompasses, apart from traditional desktop computers, a wide range of devices, such as public-use terminals, phones, TVs, car consoles, and a variety of home appliances. Today, such computing platforms are mainly delivered with embedded operating systems (such as Windows CE, Embedded/ Personal Java, and Psion Symbian), while their operational capabilities and supplied services are controlled through software. The broad use of such computing platforms in everyday life puts virtually anyone in the position of using interactive software applications in order to carry out a variety of tasks in a variety of contexts of use. Therefore, traditional development processes, targeted towards the elusive “average case”, become clearly inappropriate for the purposes of addressing the new demands for user- and usage-context diversity and for ensuring accessible and high-quality interactions. This paper will introduce the concept of unified user interfaces, which constitutes our theoretical platform for universally accessible interactions, characterized by the capability to self-adapt at run-time, according to the requirements of the individual user and the particular context of use. Then, the unified user interface development process for constructing unified user interfaces will be described, elaborating on the interactive-software engineering strategy to accomplish the run-time self-adaptation behaviour.

Designing the PDA of the future

In this article, Aaron Marcus and Associates (AM+A) describes a project with Samsung Electronics to design user-interface concepts for the future of wireless devices. AM+A conducted extensive research, including contextual observation, then designed a suite of product ideas that Samsung could incorporate into specific products over the next few years. Samsung also acquired knowledge about the user-interface development process. AM+A sought to design usable as well as useful mobile devices that could overcome extreme input and output challenges and become true personal companions.

7.8. An Integrated Methodology for Developing Interface Documentation (A Method to Maximize Information Reuse)

ABSTRACTThis paper addresses the complexity of updating and maintaining interface documentation in a document driven world. This process integrates all activities both vertically and horizontally in order to produce a low maintenance cost set of consistent documentation. The process uses a peel the onion methodology or cookbook approach to interface development. Start with an interface and what comprises it and work down.What are the “Peel the Onion” Interface Development process benefits? Maximizes the reuse of information Optimizes time spent in interface development A logical process flow for the development of an interface Ensures consistency throughout the interface specifications and Interface Control Documents Integrates behavior with requirements Full traceability of behavior to requirements Provides a mechanism for simulation development Behavioral information becomes integral part of specification.Using this methodology as the basis of behavioral, simulation and documentation saves time, reduces cost and shortens schedule. The results of this methodology are that significant cost savings can be realized by maximizing information reuse for all interfaces.

Customer responsibility for ensuring usability: Requirements on the user interface development process

An organization developing an interactive system will often find usability a compelling, but elusive, goal. The goal of ensuring usability becomes even more difficult to attain when the system is contracted to an outside developer, and control of both process and product becomes remote. Without a clear statement of requirements for the user interface of the system, this control may be lost from the beginning. Further, the cost of interactive system usage is especially significant in the case of contracted-out development, because the customer—the organization that lets a contract for interactive system development—bears the costs of training and poor user productivity. In spite of the good publicity that usability has received lately, most customers still do not state requirements for the user interface of an interactive system. Although it has been shown that the process by which a user interface is developed has an overwhelmingly large effect on usability of the product, almost never are requirements for the interface development process included in the overall system requirements. How, then, can a customer hope to ensure usability in an interactive system that the customer is contracting out for development? We propose a solution: The customer establishes requirements for the user interface development process, even as early as a Request for Proposal (RFP). To successfully write and enforce such requirements, the customer (or a knowledgeable representative of the customer) must be well informed about human-computer interaction, usability, and existing user interface development techniques. As a case study, we describe how one customer organization, the Bureau of Land Management, produced user interface development process requirements and included them in an RFP. We also discuss how a customer can use product requirements in an RFP to describe the desired general interface style without constraining the developer to a specific design.

HIFI: hypertext interface for information: multimedia and relational databases

HIFI (ESPRIT Project 6532) creates a set of tools to allow a reader to access a large body of heterogeneous information, managed by external databases created beforehand, through a hypertext interface. Information currently found in information systems is based on different media and is usually managed by different tools, like relational databases and a variety of multimedia database systems. Sometimes the need arises to ‘browse’ through the information using an interactive and intuitive interface. Hypertext is probably the best current means for interactive (and possibly intuitive) navigation through a heterogeneous body of information. Available hypertext tools, however, are usually seen as being for managing their own information rather than being an interface for accessing external databases. The HIFI approach is based on a model‐based description of the hypertext application, as it appears to the reader. A declarative and/or operational mapping translates hypertext operations (search, queries and navigation) into operations on the underlying information base and also ‘materialises’ hypertext objects, using objects of the underlying databases. The system also implements methodologies to support the hypertext interface development process. Real‐life applications will be developed to show the validity of the approach, with the cooperation of important end‐users who will cooperate with the project directly, either as partners or sponsors.

SX/Tools - An Open Design Environment for Adaptable Multimedia User Interfaces

In this paper a brief review of user interface management systems (UIMSs) and their advantages is given. Shortcomings of current UIMSs and open requirements imposed by industrial application areas are outlined. Among the most important requirements are uniform design mechanisms independent of interaction media, techniques, and styles as well as a straight forward end-user adaptability of user interfaces. A new approach to interactive interface construction, called “direct composition”, is introduced. In this approach all interface objects contain the means for their own modification and design and therefore offer consistent interaction techniques for both the construction and usage of user interfaces. Moreover, end-user adaptability is an inherent feature of direct composition interfaces. The user interface design environment SX/Tools is described to exemplify specific properties of user interface management systems following the principle of direct composition. The impacts of direct composition on user interface design include a uniform interface development process covering tool development, interface development, and “on-usage” interface adaptation. It is argued that the direct composition approach can overcome many of the problems with traditional UIMSs.