Automated specification-based testing of graphical user interfaces

Tese de doutoramento. Engenharia Electrónica e de Computadores. 2006. Faculdade de Engenharia. Universidade do Porto, Departamento de Informática, Escola de Engenharia. Universidade do Minh

Bringing LTL Model Checking to Biologists

The BioModelAnalyzer (BMA) is a web based tool for the development of discrete models of biological systems. Through a graphical user interface, it allows rapid development of complex models of gene and protein interaction networks and stability analysis without requiring users to be proficient computer programmers. Whilst stability is a useful specification for testing many systems, testing temporal specifications in BMA presently requires the user to perform simulations. Here we describe the LTL module, which includes a graphical and natural language interfaces to testing LTL queries. The graphical interface allows for graphical construction of the queries and presents results visually in keeping with the current style of BMA. The Natural language interface complements the graphical interface by allowing a gentler introduction to formal logic and exposing educational resources

Tool for Informal Specification for Mobile Devices

Tato práce se zabývá návrhem efektivního řešení podpory oblasti neformální specifikace formou aplikace pro mobilní zařízení s dotykovým displejem, Apple iPad. Návrh doprovází studie několika oblastí a to zejména neformální specifikace, jako součásti softwarového inženýrství, také studie tvorby uživatelských rozhraní a možnosti jejich implementace a následného testování uživatelské způsobilosti. Práce definuje funkční požadavky vyvíjeného nástroje, doprovázené návrhem a implementací celkem tří odlišných konceptů grafického uživatelského rozhraní. Důležitou součástí je vyhodnocení uživatelských testů, kterým byla aplikace podrobena. Dosažené výsledky slouží především k definici dalšího vývoje nástroje.This thesis aims to design an effective solution of supportive tool in field of the informal specification. Solution is based on the application for mobile devices with touch screens, Apple iPad. Design of the final product is supported by many studies, in particular those analyzing field of the informal specification, technical features, user interfaces, implementation methods and user experience testing. Thesis defines functional requirements for application development accompanied by design and the implementation of three different graphical user interfaces. Important in this thesis is the evaluation of the user experience testing, which defines future development.

Using formal models to design user interfaces a case study

The use of formal models for user interface design can provide a number of benefits. It can help to ensure consistency across designs for multiple platforms, prove properties such as reachability and completeness and, perhaps most importantly, can help incorporate the user interface design process into a larger, formally-based, software development process. Often, descriptions of such models and examples are presented in isolation from real-world practice in order to focus on particular benefits, small focused examples or the general methodology. This paper presents a case study of developing the user interface to a new software application using a particular pair of formal models, presentation models and presentation interaction models. The aim of this study was to practically apply the use of formal models to the design process of a UI for a new software application. We wanted to determine how easy it would be to integrate such models into our usual development process and to find out what the benefits, and difficulties, of using such models were. We will show how we used the formal models within a user-centred design process, discuss what effect they had on this process and explain what benefits we perceived from their use

Experiments towards model-based testing using Plan 9: Labelled transition file systems, stacking file systems, on-the-fly coverage measuring

We report on experiments that we did on Plan 9/Inferno to gain more experience with the file-system-as-tool-interface approach. We reimplemented functionality that we earlier worked on in Unix, trying to use Plan 9 file system interfaces. The application domain for those experiments was model-based testing.\ud \ud The idea we wanted to experiment with consists of building small, reusable pieces of functionality which are then composed to achieve the intended functionality. In particular we want to experiment with the idea of 'stacking' file servers (fs) on top of each other, where the upper fs acts as a 'filter' on the data and structure provided by the lower fs.\ud \ud For this experiment we designed a file system interface (ltsfs) that gives fine-grained access to a labelled transition system, and made two implementations of it.\ud We developed a small fs that, when 'stacked' on top of the ltsfs, extends it with additional files, and an application that uses the resulting file system.\ud \ud The hope was that an interface like the one offered by ltsfs could be used as a general interface between (specification language specific) programs that give access to state spaces and (specification language independent) programs that use (walk) those state spaces like simulators, model checkers, or test derivation programs.\ud \ud Initial results (obtained on a less-than-modern machine) suggest that, although the approach by itself is definitely feasible in principle, in practice the fine-grained access offered by ltsfs may involve many file (9p) transactions which may seriously affect performance. In Unix we used a more conservative approach where the access was less fine-grained which likely explains why there we did not suffer from this problem.\ud \ud In addition we report on experiments to use acid to obtain coverage information that is updated on-the-fly while the program is running. This worked quite well. The main observation from those experiments is that the basic block notion of this approach, which has a more 'semantical' nature, differs from the more 'syntactical' nature of the basic block notion in Unix coverage measurement tools\ud like tcov or gcov

Goal Driven Interaction (GDI) vs. Direct Manipulation (MD), an empirical comparison

Interacción'15, September 07-09, 2015, Vilanova i la Geltrú, Spain ACM 978-1-4503-3463-1/15/09. http://dx.doi.org/10.1145/2829875.2829892This paper presents a work in process about Goal Driven Interaction (GDI), a style of interaction intended for inexperienced, infrequent and occasional users, whose main priorities are to use a system and achieve their goals without cost in terms of time or effort. GDI basic philosophy is to guide the user about the "what" to do and the "how" to do it in each moment of the interaction process, without requiring from the user a previous knowledge to use the interface. This interaction style was introduced in previous work, where a description of its characteristics and the most appropriate user interface for it, were described. Those works included a methodology for the analysis and synthesis of the whole interactive process through a language of specification. This paper presents partial results we are collecting in real user testing, with the main aim of comparing GDI with direct manipulation interfaces (MD), nevertheless the most extended and commonly regarded as the most suitable for novice and experienced users.Universidad de Málaga. Campus de Excelencia Internacional Andalucía Tech

A tool for test automation with support for remote tests

This paper presents an interactive MS-Windows ®-based tool for high-level specification and analysis of tests on printed circuit boards, using the IEEE 1149.1 standard, and also on integrated circuits using scan design like the LSSD testing methodology. As novel contributions we provide an object-oriented tool for Boundary Scan and LSSD test automation with support for remote tests, including interfaces to circuit description, chip interconnection, test vector analysis and test vector generation. The system is a reasona'.Jly complete CAE test system that includes features like remote testing (using client- server technology), project management computer-aided learning support, menu-based command entry, user-defined configuration and a comprehensive set of commands. Thus, by using this system, a test engineer or a circuit designer are able to specify and verify tests for printed circuit boards or for integrated circuits, either ocally or remotely

Extending snBench to Support a Graphical Programming Interface for a Sensor Network Tasking Language (STEP)

The purpose of this project is the creation of a graphical "programming" interface for a sensor network tasking language called STEP. The graphical interface allows the user to specify a program execution graphically from an extensible pallet of functionalities and save the results as a properly formatted STEP file. Moreover, the software is able to load a file in STEP format and convert it into the corresponding graphical representation. During both phases a type-checker is running on the background to ensure that both the graphical representation and the STEP file are syntactically correct. This project has been motivated by the Sensorium project at Boston University. In this technical report we present the basic features of the software, the process that has been followed during the design and implementation. Finally, we describe the approach used to test and validate our software