User interface specification with sequence diagrams: an application to the AIRBUS A380 Datalink system

The development of user interfaces for safety critical systems is driven by requirements specifications. Because user interface specifications are typically embedded within complex systems requirements specifications, they can be intractable to manage. Proprietary requirements specification tools do not support the user interface designer in modelling and specifying the user interface. In this paper, a new way of working with embedded user interface specifications is proposed, exploiting sequence diagrams with a hypertext structure for representing and retrieving use cases. This new tool concept is assessed through an application to the requirements specification for the Airbus A380 air traffic control Datalink system; engineers involved in the development of the Airbus cockpit used a prototype of the tool concept to resolve a set of user interface design anomalies in the requirements specification. The results of the study are positive and indicate the user interface to requirements specification tools which user interface designers themselves need.     

A service creation environment based on scenarios

Scenarios are often constructed for illustrating example runs through reactive system. Scenarios that describe possible interactions between a system and its environment are widely used in requirement engineering, as a means for users to communicate their functional requirements. Various software development methods use scenarios to define user requirements, but often lack tool support. Existing tools are graphical editors rather than tool support for design. This paper presents a service creation environment for elicitation, integration, verification and validation of scenarios. A semi-formal language is defined for user oriented scenario representation, and a prototype tool implementing an algorithm that integrates them for formal specification generation. This specification is then used to automatically find and report inconsistencies in the scenarios.     

Open graphical framework for interactive TV

Multimedia end-user terminals are expected to perform advanced user interface related tasks. These tasks are carried out by user interface runtime tools and include, among others, the visualization of complex graphics and the efficient handling of user input. In addition, the terminal’s graphical system is expected, for example, to be able to synchronize audio and video, and control different contexts on the same screen. Finally, the availability of high-level tools to simplify the user interface implementation and the adaptiveness of the user interfaces for a diversity of configurations are, as well, desirable features. This paper presents a layered model that meets the just mentioned requirements. The architecture is divided into five different layers: hardware abstraction layer, multimedia cross platform libraries, graphical environment, GUI toolkit and high-level languages. Moreover, this paper presents the experiences of developing a prototype system based on the architecture, targeted to digital television receivers. In order to evaluate the prototype, some already developed DVB-MHP compliant digital television applications were tested. Finally, the prototype was extended with a high-level profile (i.e., SMIL support) and a low-level one (i.e., access to the framebuffer memory).

A methodology for supporting requirement management tools (RMt) design in the PLM scenario: An user-based strategy

In the current “mass customization” scenario, product complexity is increasing significantly due to the necessity to answer as quickly and effectively as possible to many different costumer needs but maintaining costs under control. In this scenario, requirements management becomes a fundamental features for the entire product lifecycle, as enterprises need to have a complete and clear idea of the market for succeeding in developing and supporting the right and innovative product. Moreover, considering that product lifecycle is characterized by many “trade-off”, so that product features are often negotiated in order to fulfil to conflicting requirements, it is important to support the “traceability” of the entire lifecycle “negotiation” process. For this reason, PLM platform has to provide suitable methodologies and tools able to efficiently support the design and management of large set of complex requirements. Requirements Management Tools (RMt) embedded in PLM solutions help keeping specifications consistent, up-to-date, and accessible. At present, there are different possible solutions, but a shared PLM integrated seems not to be available. In order to fill this gap, this paper has developed an user-based strategy, based on Kano methodology, so on “user satisfaction”, in order to define a structured set of guidelines to support the design of the features of an integrated PLM requirement management tool.     

Requirements for graphical user interface development environments for groupware

Most user interface designers are conversant with graphical user interface (GUI) tools such as Motif¹ and Presentation Manager² which provide ‘widgets’ and other facilities for building user interfaces. Such GUI tools were developed primarily for building interfaces to single-user systems. The purpose of the paper is to present the result of research into the requirements for GUI tools for multi-user systems. Many of the requirements of single and multi-user GUIs are the same, for example, usability and flexibility. A number of new widgets are needed for multi-user GUIs, for example, shared scroll-bars and multi-user telepointers. The requirements are divided into three groups based on three sources of requirements: literature, user survey and widgets.     

Intrigue: Personalized recommendation of tourist attractions for desktop and hand held devices

This paper presents INTRIGUE, a prototype tourist-information server that presents information about the area around Turin City, Italy, on desktop and hand held devices.This system recommends sightseeing destinations and itineraries by taking into account the preferences of heterogeneous tourist groups (such as families with children or the elderly) and explains the recommendations by addressing the group members' requirements. Moreover, the system provides an interactive agenda for scheduling the tour. The services offered by INTRIGUE rely on user modeling and adaptive hypermedia techniques; furthermore, XML-based technologies support the generation of the user interface and its adaptation to Web browsers and WAP minibrowsers.     

Multigroup decision-support systems in CSCW

Research in computer-supported cooperative work (CSCW) has concentrated on developing techniques and support systems for groups of tightly coupled individuals focused on activities such as group writing and design development. A natural extension involves group decision-support systems (GDSS) that can assist multiple groups working in different places at different times. Our work extends the GDSS approach to a multigroup decision-support system (MGDSS) and uses the advanced integrated requirements engineering system (AIRES) for support. Two case studies, including data from user questionnaires, indicate a high level of user satisfaction with the support the system provides. The MGDSS process and AIRES software support idea elicitation to solve complex problems. The system automatically organizes and assesses these ideas to help large groups build consensus     

SCRAM–CK: applying a collaborative requirements engineering process for designing a web based e-science toolkit

This paper presents SCRAM–CK, a method to elicit requirements by means of strong user involvement supported by prototyping activities. The method integrates two existing approaches, SCRAM and CK theory. SCRAM provides the framework for requirements management, while CK theory provides a framework for reasoning about design and its evolution. The method is demonstrated with the definition and refining of requirements for the BioVeL web toolkit. The objective of BioVeL is to allow scientists to understand, run, modify and construct workflows for data analysis with minimal training using a web-based interface. The proposed method is supported by prototyping activities for gathering user feedback, and refining requirements and design proposals. Using this method, the prototypes evolved from simple workflow execution enablers to include more complex functionalities for reviewing, modifying and building workflows in later versions. This paper presents a contribution to the application of techniques for requirements engineering. SCRAM–CK is an amalgamated method that combines a user-centred continuous refinement approach with support for design evolution through prototyping. The paper also shows the influence of the requirements engineering process in the evolution of design proposals.     

基于QFD—PUGH的人机界面评价方法研究

人机界面的设计优化包括用户需求转化为设计需求的准确性和设计需求形成最优方案2部分,设计评价是界面设计优化的重要手段.在当前的评价方法中,上述两者是分阶段进行,数据共享性差.针对该问题,提出一种基于质量功能展开(QFD)和PUGH决策矩阵融合的人机界面评价方法.首先运用层次分析法确定人机界面的用户需求权重,结合界面产品特...     

A Method for Extracting and Stating Software Requirements that a User Interface Prototype Contains

User interface and requirements prototyping is a requirements elicitation technique. A user interface and requirements prototype is built during the requirements engineering phase of a software system development. Along with the user interface prototype are produced various documents such as the system requirement specification. When a prototype and other documents exist, they may not describe the same functionality, particularly because there may be behaviour of the prototype, artefacts of prototyping, that may not be intended. The problem is that in later development stages, when there is a prototype and other documents, it is often difficult to reconcile the difference between the prototype and the other documents. This paper presents an approach for avoiding this difficulty. It demonstrates the approach by showing its application to parts of a real software development.     

环流式旋风除尘器设计软件的开发

对于旋风除尘器的设计主要依靠手工计算进行，其过程繁琐且难以保证其准确性。针对旋风除尘器设计的特点，利用Visual Basic 6．0及AutoCAD工具开发了一个环流式旋风除尘器设计软件CycloneDraw。通过该软件用户只需输入操作条件，即可得到旋风除尘器的结构简图。该软件具有设计计算、数据库查询、生成设备图等功能。用户界面友好、操作方便、运行可靠稳定。     

From user interface design to the support of intelligent and adaptive interfaces: an overhaul of user interface software infrastracture

Research on adaptive interfaces in the past has lacked support from user interface tools which allow interfaces to be easily created and modified. Also, current user interface tools provide no support for user models which can collect task-oriented information about users. Developing an adaptive interface requires a user model and an adaptation strategy. It also, however, requires a user interface which can be adapted. The latter task is often time-consuming, especially in relation to more sophisticated user interfaces.

The paper presents a user interface design environment, UIDE, which has a different software infrastracture. Designers use high-level specifications to create a model of an application and links from the application to various interface components. The model is the heart of all the design and run-time support in UIDE, including automatic dialog sequencing and help generation. UIDE provides automatic support for collecting task-oriented information about users, by the use of its high-level specifications in its application model as a basic construct for a user model. Some examples of adaptive interfaces and adaptive help are presented that use the information that is collectable in UIDE.     

Situated cognitive engineering for crew support in space

Space crews are in need for excellent cognitive support to perform nominal and off-nominal actions. This paper presents a coherent cognitive engineering methodology for the design of such support, which may be used to establish adequate usability, context-specific support that is integrated into astronaut’s task performance and/or electronic partners who enhance human–machine team’s resilience. It comprises (a) usability guidelines, measures and methods, (b) a general process guide that integrates task procedure design into user interface design and a software framework to implement such support and (c) theories, methods and tools to analyse, model and test future human–machine collaborations in space. In empirical studies, the knowledge base and tools for crew support are continuously being extended, refined and maintained.     

Embarking on Spoken-Language NL Interface Design

Natural language (NL) user interfaces are growing in popularity. Unfortunately, the complexity of NL interaction makes these interfaces difficult to design. For NL interfaces to become successful, universal tools are needed to help support the NL design process. What work practice should these tools explicitly support? Interviews with NL designers and our own experiments have identified a specific work practice that designers should consider as they begin to incorporate NL into user interface designs. The work practice study highlights the value of using Wizard of Oz prototyping in NL design. We describe a tool that we have built, called SUEDE, to explicitly support the first stage of NL design for spoken-language user interfaces. Our tools and tools like it will help make NL in human-computer interaction (HCI) more commonplace.     

Building Consensus in Human-Computer Interaction Design: Integrated Activity-Oriented Design Environments

This article proposes and describes activity-oriented design environments (AODEs) as an integrated design platform for building consensus in the context of human-computer interaction (HCI) design activities. Principles and architectural properties of AODEs are illustrated by means of a reference scenario from the domain of accessibility. To this effect, a research prototype of an AODE is presented as a means to validate the proposition made. The research prototype integrates alternative design perspectives (e.g., user modeling, analytical HCI design, argumentation and critiquing) into an extensible design platform of interoperable computational modules to implement a method toward accessibility, which is best suited to specification-oriented user interface development practices. Using the reference scenario, this article describes how the prototype AODE facilitates a seamless bridge between design and development activities through articulating shared representations of design knowledge and compiling recommendations, which can be directly interpreted and applied by a user interface development environment.     

Round-Trip Prototyping Based on Integrated Functional and User Interface Requirements Specifications

Requirements engineering in the new millennium is facing an increasing diversity of computerised devices comprising an increasing diversity of interaction styles for an increasing diversity of user groups. Thus the incorporation of user interface requirements into software requirements specifications becomes more and more mandatory. Validating these requirements specifications with hand-made, throw-away prototypes is not only expensive, but also bears the danger that validation results are not accurately fed back into the requirements specification. In this paper, we propose an enhancement of the requirements specification method SCORES for an explicit capturing of user interface requirements. The advantages of the approach are threefold. First, the user interface requirements specification is UML-compliant and integrated into the functional requirements specification. Second, prototypes for validation purposes can semi-automatically be generated. Third, the model-based generation of prototypes allows for ‘round-trip prototyping’ such that manual changes of the prototype during the validation process are automatically fed back into the requirements specification.     

A home-page overhaul using other Web sites

The best prototype for designing a new user interface is your old user interface. The second best prototype is a competing product. Your competitors have invested significant resources in designing and implementing what they believe to be good user interfaces. You can glean much of what you need to create a new interface by examining products designed to solve similar problems. As with your own old user interface, you can analyze competing interfaces to see what works and what doesn't. You can also watch how users interact with competing products, and thus learn how they approach tasks. This, in essence, is competitive usability analysis. I recommend performing it very early in the usability engineering life-cycle-after you have visited the customer, gathered requirements, and defined the product vision, but before you design and prototype your new user interface