Analyzing the researcher's work in generating data: The case of complaints

This article investigates the researcher's work in the coproduction (or not) of complaint sequences in research interviews. Using a conversation analytic approach, we show how the interviewer's management of complaint sequences in a research setting is consequential for subsequent talk and thus directly affects the data generated. In the examples shown here, researchers sharing cocategorial incumbency with respondents may well provide spaces for research participants to formulate complaints. This article examines sequences of talk surrounding complaints to show how researchers generate complaints (or not) and handle unsafe complaints. Researchers are able to provoke specific types of accounts from respondents, whereas their respondents may actively resist the researchers' direction. For researchers using the interview as a method of data generation, examination of complaint sequences and how these appear in interview data provides insight into how interview talk is coproduced and managed within a socially situated setting.

A critical appraisal of the intrinsic pancreatic angiotensin-generating system

The pancreas is a relative newcomer to the stable of tissues with an intrinsic angiotensin-generating system. The involvement of this system in pancreatic activity will be dependent on the angiotensin-generating paths present in the pancreas and their precise cellular location. Thus far, renin, angiotensin-converting enzyme (ACE), angiotensin II and AT1 and AT2 receptors have been found. These are components of the "classical" renin-angiotensin system. But there is uncertainty as to their location and site of action. Furthermore, it is not known which, if any, alternative enzymes to renin and ACE are present, which angiotensins in addition to angiotensin II are generated and whether or not there are receptors to angiotensin IV and angiotensin-(1-7). Future research should focus on these aspects in order to provide a mechanistic basis to pancreatic physiological functions and to pathological conditions of clinical relevance.

A critical role for the parabrachial nucleus in generating central nervous system responses elicited by a systemic immune challenge

Using Fos immunolabelling as a marker of neuronal activation, we investigated the role of the parabrachial nucleus in generating central neuronal responses to the systemic administration of the proinflarnmatory cytokine interleukin-1beta (1 mug/kg, i.a.). Relative to intact animals, parabrachial nucleus lesions significantly reduced the number of Fos-positive cells observed in the central amygdala (CeA), the bed nucleus of the stria terminalis (BNST), and the ventrolateral medulla (VLM) after systemic interleukin-1beta. In a subsequent experiment in which animals received parabrachial-directed deposits of a retrograde tracer, it was found that many neurons located in the nucleus tractus solitarius (NTS) and the VLM neurons were both retrogradely labelled and Fos-positive after interleukin-1beta administration. These results suggest that the parabrachial nucleus plays a critical role in interleukin-1beta-induced Fos expression in CeA, BNST and VLM neurons and that neurons of the NTS and VLM may serve to trigger or at least influence changes in parabrachial nucleus activity that follows systemic interleukin-1beta administration. (C) 2004 Elsevier B.V. All rights reserved.

Tool support for generating passive C++ test oracles from object-z specifications

A test oracle provides a means for determining whether an implementation behaves according to its specification. A passive test oracle checks that the correct behaviour has been implemented, but does not implement the behaviour itself. In previous work, we have presented a method that allows us to derive passive C++ test oracles from formal specifications written in Object-Z. We describe the "Warlock" prototype tool that supports the method. Warlock is built on top of an existing Object-Z type checker and generates oracle code for a substantial subset of the Object-Z language. We describe the architecture of Warlock and its application to a number of Object-Z specifications. We also discuss its current limitations.