Water requirements as a bottleneck in the reintroduction of European roe deer to the southern edge of its range

Success rates of reintroduction programs are low, often owing to a lack of knowledge of site-specific ecological requirements. A reintroduction program of European roe deer (Capreolus capreolus (L., 1758)) in a dry Mediterranean region in Israel provides an opportunity to study the bottleneck effect of water requirements on a mesic-adapted species. Four does were hand-reared and released in a 10 ha site consisting of an early succession scrubland and a mature oak forest. We measured daily energy expenditure (DEE) and water turnover (WTO) using the doubly labeled water technique during summer and winter. DEE was similar in the summer and winter, but there was a significant difference in WTO and in the source of gained water. In winter, WTO was 3.3 L/day, of which 67% was obtained from vegetation. In summer, WTO dropped to 2.1 L/day, of which only 20% was obtained from the diet and 76% was gained from drinking. When the water source was moved to a nonpreferred habitat, drinking frequency dropped significantly, but water consumption remained constant. In a dry Mediterranean environment, availability of free water is both a physiological contraint and a behavioral constraint for roe deer. This study demonstrates the importance of physiological and behavioral feasibility studies for reintroduction programs.

Influence of ABCB1 polymorphisms and haplotypes on tacrolimus nephrotoxicity and dosage requirements in children with liver transplant

AIMS
The aim of this study was to investigate the in?uence of genetic polymorphisms in ABCB1 on the incidence of nephrotoxicity and tacrolimus dosage-requirements in paediatric patients following liver transplantation.
METHODS
Fifty-one paediatric liver transplant recipients receiving tacrolimus were genotyped for ABCB1 C1236>T, G2677>T and C3435>T polymorphisms. Dose-adjusted tacrolimus trough concentrations and estimated glomerular ?ltration rates (EGFR) indicative of renal toxicity were determined and correlated with the corresponding genotypes.
RESULTS
The present study revealed a higher incidence of the ABCB1 variant-alleles examined among patients with renal dysfunction (30% reduction in EGFR) at 6 months post-transplantation (1236T allele: 63.3% vs 37.5% in controls,P = 0.019; 2677T allele: 63.3% vs. 35.9%, p = 0.012; 3435T allele: 60% vs. 39.1%,P = 0.057). Carriers of the G2677->T variant allele also had a signi?cant reduction (%) in EGFR at 12 months post-transplant (mean difference = 22.6%; P = 0.031). Haplotype analysis showed a signi?cant association between T-T-T haplotypes and an increased incidence of nephrotoxicity at 6 months post-transplantation (haplotype-frequency = 52.9% in nephrotoxic patients vs 29.4% in controls; P = 0.029). Furthermore, G2677->T and C3435->T polymorphisms and T-T-T haplotypes were signi?cantly correlated with higher tacrolimus dose-adjusted pre-dose concentrations at various time points examined long after drug initiation.
CONCLUSIONS
These ?ndings suggest that ABCB1 polymorphisms in the native intestine signi?cantly in?uence tacrolimus dosage-requirement in the stable phase after transplantation. In addition, ABCB1 polymorphisms in paediatric liver transplant recipients may predispose them to nephrotoxicity over the ?rst year posttransplantation. Genotyping future transplant recipients for ABCB1 polymorphisms, therefore, could have the potential to individualize better tacrolimus immunosuppressive therapy and enhance drug safety

Sources of Software Requirements Change from the Perspectives of Development and Maintenance

Changes to software requirements occur during initial development and subsequent to delivery, posing a risk to cost and quality while at the same time providing an opportunity to add value. Provision of a generic change source taxonomy will support requirements change risk visibility, and also facilitate richer recording of both pre- and post-delivery change data. In this paper we present a collaborative study to investigate and classify sources of requirements change, drawing comparison between those pertaining to software development and maintenance. We begin by combining evolution, maintenance and software lifecycle research to derive a definition of software maintenance, which provides the foundation for empirical context and comparison. Previously published change ‘causes’ pertaining to development are elicited from the literature, consolidated using expert knowledge and classified using card sorting. A second study incorporating causes of requirements change during software maintenance results in a taxonomy which accounts for the entire evolutionary progress of applications software. We conclude that the distinction between the terms maintenance and development is imprecise, and that changes to requirements in both scenarios arise due to a combination of factors contributing to requirements uncertainty and events that trigger change. The change trigger taxonomy constructs were initially validated using a small set of requirements change data, and deemed sufficient and practical as a means to collect common requirements change statistics across multiple projects.