Item validity of the physical demands from the Dictionary of Occupational Titles for the functional capacity evaluation of clients with chronic back pain

This study assessed the item validity of 15 of the physical demands from the Dictionary of Occupational Titles (DOT), as evaluated in a new approach to functional capacity evaluation (FCE) for clients with chronic back pain, the Gibson Approach to FCE (GAPP FCE). Fifty-two occupational therapists were sent the specifications of the items in the GAPP FCE procedures and were asked to rate the items in terms of item-objective congruence, relevance and difficulty. A response rate of 59.2% was obtained. The majority of the therapists agreed that most of the items were congruent with the objectives based on the definition of the physical demands from the DOT. The items evaluating Balancing and Pushing and Pulling had the lowest item-objective congruence. The evaluation of Balancing and the Lifting, Carrying and Pushing and Pulling of loads greater than light-medium weight (10–16 kg) were not considered significantly relevant. Concerns were raised about the difficulty and safety of the evaluation of Lifting, Carrying and Pushing and Pulling with clients with chronic back pain, particularly if the therapist evaluates the manual handling of medium to heavy loads. These results may have implications for other FCEs, particularly those which are based on the DOT, or when assessing clients with chronic back pain.

A reference architecture for instructional educational software

Our extensive research has indicated that high-school teachers are reluctant to make use of existing instructional educational software (Pollard, 2005). Even software developed in a partnership between a teacher and a software engineer is unlikely to be adopted by teachers outside the partnership (Pollard, 2005). In this paper we address these issues directly by adopting a reusable architectural design for instructional educational software which allows easy customisation of software to meet the specific needs of individual teachers. By doing this we will facilitate more teachers regularly using instructional technology within their classrooms. Our domain-specific software architecture, Interface-Activities-Model, was designed specifically to facilitate individual customisation by redefining and restructuring what constitutes an object so that they can be readily reused or extended as required. The key to this architecture is the way in which the software is broken into small generic encapsulated components with minimal domain specific behaviour. The domain specific behaviour is decoupled from the interface and encapsulated in objects which relate to the instructional material through tasks and activities. The domain model is also broken into two distinct models - Application State Model and Domainspecific Data Model. This decoupling and distribution of control gives the software designer enormous flexibility in modifying components without affecting other sections of the design. This paper sets the context of this architecture, describes it in detail, and applies it to an actual application developed to teach high-school mathematical concepts.