Potential Disconnects Research Articles

A content analysis of auditors' reports on IT internal control weaknesses: The comparative advantages of an automated approach to control weakness identification

We employ an automated content analysis approach to provide a snapshot of the terminology auditors actually use to describe information technology weaknesses (ITWs). We develop and use a dictionary based on textual analysis of auditors' reports on internal control filed under Section 404 of the Sarbanes–Oxley Act from 2004 to 2009. Using the dictionary with content analysis software led to the identification of 14 categories of ITWs in order of decreasing frequency of occurrence: (1) access, (2) monitoring, (3) design issues, (4) change and development, (5) end-user computing, (6) segregation of incompatible functions, (7) policies, (8) documentation, (9) masterfiles, (10) backup, (11) staffing sufficiency and competency, (12) security (other than over access), (13) outsourcing and (14) operations. The use of automated content analysis methodology also helped us identify potential disconnects between terminology used in auditors' reports and that used in published frameworks and guidelines. We provide the dictionary and discuss the methodology used in creating and applying the dictionary to the analysis of the textual content of auditors' reports on internal control, including the advantages and limitations of automated ITW identification.

Four Potential Disconnects in the Community Planning Process

Although participatory planning has become a well-established emphasis in the planning field, planners often find that land-use outcomes conflict with community goals, resulting in a dissatisfied citizenry. I argue that these conflicts often result from disconnects between steps in the planning process, which tend to occur in instances where the “baton” of implementation passes from one document or one agency to the next. I identify four common areas of disconnect within the planning process, propose explanations for each of the disconnects, and suggest ways to overcome this tendency for the planning process to break down.

Initiation of therapy with a subcutaneously administered antiretroviral in treatment-experienced HIV-infected patients: understanding physician and patient perspectives1

Enfuvirtide (Fuzeon) is the first self-injectable antiretroviral (ARV) therapy approved for the treatment of HIV. This study was undertaken to explore the perceptions of injectable ARVs among physicians and treatment-experienced HIV-infected patients and identify potential motivators or barriers to the initiation of injectable ARV therapies. This empirical study was conducted based on qualitative field research conducted in multiple centres in five European countries and the US. A purposive sampling strategy was employed and structured interviews carried out with physicians and patients. Discussion guides for these interviews focused on attitudinal responses to a range of key areas. For physicians, these areas included HIV treatment, treatment-experienced patients and their relationships with them and injectable therapy usage, while for patients – some of whom were receiving enfuvirtide therapy – the focus included relationships with their physicians and attitudes towards injectable ARV therapy. Sixty-eight physicians and 43 patients were interviewed. Qualitative analysis of the interview responses revealed a number of recurring themes among physician and patient perceptions of HIV and its treatment. Physicians tended to view injectable ARVs as a last resort, with only limited suitability among treatment-experienced patients and a low level of patient acceptability. In contrast, patients generally perceived the potential value of effective injectable ARV therapy, if recommended to them by their physicians, indicating that its benefits could outweigh the drawbacks associated with its administration. This study identified some potential disconnects between physician and patient perceptions of injectable therapy. Our findings emphasize the need for patients to discuss their treatment goals with their physicians so that they can work together to find the regimen that is most likely to achieve these goals.

Theoretical framework for the continuous early validation (CEaVa) method

AbstractSystems being developed today make extensive and complex use of advanced technology. Many, if not most, of these systems are being produced but are not used or useful on delivery because the wrong problem was solved. A major cause for this shortfall in system development is due to changes in the operational environment of the intended system while the development process is ongoing. Significant sections of the literature discuss the need to get stakeholders involved earlier in the development process to correct this problem. However, no one has developed a detailed framework that accomplishes this intent. This paper defines a method involving a four‐step sequence that validates the entire system design process early and continuously to ensure that the right problem is being solved. The method is called Continuous Early Validation (CEaVa). It is a method that increases the likelihood of producing the correct system. The method develops visibility of potential disconnects among stakeholders' needs, original written requirements, organizational policy, and derived requirements. The CEaVa method validates the external and internal consistency of the problem statement. Additionally, CEaVa facilitates consensus on trade offs and priorities, resolving the potential disconnects with decision analytical reasoning for trade‐off analysis. The CEaVa method improves the development process and ultimately the system itself by increasing the likelihood of building the right system within budget and schedule. © 2002 Wiley Periodicals, Inc. Syst Eng 5: 223–241, 2002