Search

Ankle deficiencies occur quite often among poststroke patients and people working in physically demanding professions in general. Computerized telerehabilitation systems have emerged as promising assistive tools for effective diagnosis and rehabilitation interventions. Consequently, the process of recording and analyzing the medical data captured by such systems has become vital for the generation of efficient reports that can assist clinicians to assess their patient's health. In this paper, we present our telerehabilitation system called “Tele-Wobble” that consists of a modified version of a wobble board mounted with sensors and actuators, a software training game, and a web-service architecture that allows for remote monitoring of the patient's training progress. The system aims to provide clinicians with key performance measurements captured during the patient's training session. Our evaluations showed that Tele-Wobble may offer an efficient and cost-effective home-based rehabilitation for patients with ankle deficiencies. [ABSTRACT FROM PUBLISHER]

As a software engineer or client, how much of your budget should you spend on software security mitigation for the applications and networks on which you depend? The authors introduce a novel way to optimize a combination of security countermeasures under fixed resources. Software engineers and their customers continuously face a complex and frustrating decision: given a fixed budget, which combination of vulnerability mitigation actions produces optimal system security? In a world without budgetary or temporal constraints, engineers could invest in whatever tools or training they deemed necessary to safeguard applications and networks. Or they could spend arbitrary amounts of time and money patching existing code and take painstaking precaution in writing new software to ensure its security. Of course, the economic reality is that software engineers are pushed to get their product to market as fast as possible, and security is often a distant priority in the face of budgetary constraints. However, fixing any remaining security vulnerabilities postproduction can be both costly and wasteful. In this article, we describe a novel methodology for quantitatively optimizing the blend of architectural and policy recommendations that engineers can apply to their products to maximize security under a fixed budget. The results of our optimization are sometimes surprising and even counterintuitive: bigger budgets don't always produce greater security, and the optimal combination of corrective actions changes nonlinearly with increasing expenditures. These findings suggest that some form of formal decision support could augment traditional methods. [ABSTRACT FROM PUBLISHER]