Effective affective user interface design in games

It is proposed that games, which are designed to generate positive affect, are most successful when they facilitate flow (Csikszentmihalyi 1992). Flow is a state of concentration, deep enjoyment, and total absorption in an activity. The study of games, and a resulting understanding of flow in games can inform the design of non-leisure software for positive affect. The paper considers the ways in which computer games contravene Nielsen's guidelines for heuristic evaluation ( Nielsen and Molich 1990) and how these contraventions impact on flow. The paper also explores the implications for research that stem from the differences between games played on a personal computer and games played on a dedicated console. This research takes important initial steps towards de. ning how flow in computer games can inform affective design.

A feasibility study of email communication between the patient's family and the specialist burns team

We investigated whether the parents of burns patients could capture suitable clinical images with a digital camera and add the necessary text information to enable the paediatric burns team to provide follow-up care via email. Four families were involved in the study, each of whom sent regular email consultations for six months. The results were very encouraging. The burns team felt confident that the clinical information in 30 of the 32 email messages (94%) they received was accurate, although in I I of these 30 cases (37%) they stated that there was room for improvement (the quality was nonetheless adequate for clinical decision making). The study also showed that low-resolution images (average size 37 kByte) were satisfactory for diagnosis. Families were able to participate in the service without intensive training and support. The user survey showed that all four families found it easy and convenient to take the digital photographs and to participate in the study. The results suggest that the technique has potential as a low-cost telemedicine service in burns follow-up, and that it requires only modest investment in equipment, training and support.

User dyads in software testing: bypassing the need for expert observers

This paper arises out of a research study into the online help facilities provided in popular software applications such as word processors. Its particular focus is on experimental methods of evaluating the effectiveness and usability of those facilities. Focus groups, questionnaires, and online surveys had already been used in other phases of the study, but it was judged that these approaches would be unsuitable for measuring effectiveness and usability because they are susceptible to respondents' subjectivity. Direct observation of people working on set word-processing tasks was ruled out initially because of a lack of trained observers; it would have taken too long for the investigator to observe a large enough sample by himself. Automatic recording of users' actions was also rejected, as it would have demanded equipment and/or software that was not available and seemed too expensive to acquire. The approach and techniques described here were an attempt to overcome these difficulties by using observers drawn from the same population of students that provided the test subjects; as a by-product, this may also have enhanced the acceptability (and hence possibly the validity) of the experiments by reducing the exam pressure perceived by participants.

Using a clinical pathway and education to reduce inappropriate prescribing of enoxaparin in patients with acute coronary syndromes: a controlled study

Aims: To evaluate efficacy of a pathway-based quality improvement intervention on appropriate prescribing of the low molecular weight heparin, enoxaparin, in patients with varying risk categories of acute coronary syndrome (ACS). Methods: Rates of enoxaparin use retrospectively evaluated before and after pathway implementation at an intervention hospital were compared to concurrent control patients at a control hospital; both were community hospitals in south-east Queensland. The study population was a group of randomly selected patients (n = 439) admitted to study hospitals with a discharge diagnosis of chest pain, angina, or myocardial infarction, and stratified into high, intermediate, low-risk ACS or non-cardiac chest pain: 146 intervention patients (September-November 2003), 147 historical controls (August-December 2001) at the intervention hospital; 146 concurrent controls (September-November 2003) at the control hospital. Interventions were active implementation of a user-modified clinical pathway coupled with an iterative education programme to medical staff versus passive distribution of a similar pathway without user modification or targeted education. Outcome measures were rates of appropriate enoxaparin use in high-risk ACS patients and rates of inappropriate use in intermediate and low-risk patients. Results: Appropriate use of enoxaparin in high-risk ACS patients was above 90% in all patient groups. Inappropriate use of enoxaparin was significantly reduced as a result of pathway use in intermediate risk (9% intervention patients vs 75% historical controls vs 45% concurrent controls) and low-risk patients (9% vs 62% vs 41%; P < 0.001 for all comparisons). Pathway use was associated with a 3.5-fold (95% CI: 1.3-9.1; P = 0.012) increase in appropriate use of enoxaparin across all patient groups. Conclusion: Active implementation of an acute chest pain pathway combined with continuous education reduced inappropriate use of enoxaparin in patients presenting with intermediate or low-risk ACS.

A case study in specification and implementation testing

Achieving consistency between a specification and its implementation is an important part of software development In previous work, we have presented a method and tool support for testing a formal specification using animation and then verifying an implementation of that specification. The method is based on a testgraph, which provides a partial model of the application under test. The testgraph is used in combination with an animator to generate test sequences for testing the formal specification. The same testgraph is used during testing to execute those same sequences on the implementation and to ensure that the implementation conforms to the specification. So far, the method and its tool support have been applied to software components that can be accessed through an application programmer interface (API). In this paper, we use an industrially-based case study to discuss the problems associated with applying the method to a software system with a graphical user interface (GUI). In particular, the lack of a standardised interface, as well as controllability and observability problems, make it difficult to automate the testing of the implementation. The method can still be applied, but the amount of testing that can be carried on the implementation is limited by the manual effort involved.