Two new tools for assessing patients' knowledge and beliefs about obstructive sleep apnea and continuous positive airway pressure therapy

Background and purpose: Patients' knowledge and beliefs about their illnesses are known to influence a range of health related variables, including treatment compliance. It may, therefore, be important to quantify these variables to assess their impact on compliance, particularly in chronic illnesses such as Obstructive Sleep Apnea (OSA) that rely on self-administered treatments. The aim of this study was to develop two new tools, the Apnea Knowledge Test (AKT) and the Apnea Beliefs Scale (ABS), to assess illness knowledge and beliefs in OSA patients. Patients and methods: The systematic test construction process followed to develop the AKT and the ABS included consultation with sleep experts and OSA patients. The psychometric properties of the AKT and ABS were then investigated in a clinical sample of 81 OSA patients and 33 healthy, non-sleep disordered adults. Results: Results suggest both measures are easily understood by OSA patients, have adequate internal consistency, and are readily accepted by patients. A preliminary investigation of the validity of these tools, conducted by comparing patient data to that of the 33 healthy adults, revealed that apnea patients knew more about OSA, had more positive attitudes towards continuous positive airway pressure (CPAP) treatment, and attributed more importance to treating sleep disturbances than non-clinical groups. Conclusions: Overall, the results of psychometric analyses of these tests suggest these measures will be useful clinical tools with numerous beneficial applications, particularly in CPAP compliance studies and apnea education program evaluations. (C) 2004 Elsevier B.V. All rights reserved.

How do practitioners use conceptual modeling in practice?

Much research has been devoted over the years to investigating and advancing the techniques and tools used by analysts when they model. As opposed to what academics, software providers and their resellers promote as should be happening, the aim of this research was to determine whether practitioners still embraced conceptual modeling seriously. In addition, what are the most popular techniques and tools used for conceptual modeling? What are the major purposes for which conceptual modeling is used? The study found that the top six most frequently used modeling techniques and methods were ER diagramming, data flow diagramming, systems flowcharting, workflow modeling, UML, and structured charts. Modeling technique use was found to decrease significantly from smaller to medium-sized organizations, but then to increase significantly in larger organizations (proxying for large, complex projects). Technique use was also found to significantly follow an inverted U-shaped curve, contrary to some prior explanations. Additionally, an important contribution of this study was the identification of the factors that uniquely influence the decision of analysts to continue to use modeling, viz., communication (using diagrams) to/from stakeholders, internal knowledge (lack of) of techniques, user expectations management, understanding models' integration into the business, and tool/software deficiencies. The highest ranked purposes for which modeling was undertaken were database design and management, business process documentation, business process improvement, and software development. (c) 2005 Elsevier B.V. All rights reserved.

Using measurement data in a TSPSM project

One of the challenges for software engineering is collecting meaningful data from industrial projects. Software process improvement depends on measurement to provide baseline status and confirming evidence of the effect of process changes. Without data, any conclusions rely on intuition and guessing. The Team Software ProcessSM (TSPSM) provides a powerful framework for data collection and analysis, in addition to its primary goal as a basis for highly effective software development. In this paper, we describe the experiences of, and benefits realized by, a team using the TSP for the first time. By reviewing how this particular team collected and used data, we show features of the TSP that make it a powerful foundation for software process improvement.