No abstract

No abstract

No abstract

Receptors for atrial natriuretic peptide (ANP) are known to be present in many organs, e.g. brain, liver and kidney. The aim of this study was to optimize the labelling method for ANP analogues with iodine-123 and to describe their pharmakokinetics. ANP 99-126, atriopeptin III, Tyr-atriopeptin II and urodilatin were labelled by the Iodogen method. Of the various labelling conditions tested, the Iodogen procedure with 10 micrograms Iodogen, 10 micrograms peptides in 100 microliters phosphate buffer (pH 7.2) and a reaction time of 60 min proved to be optimal. Separation was performed using a Sep-pak reversed-phase extraction cartridge. In all cases quality control by thin-layer chromatography resulted in a radiochemical purity higher than 98%. After intravenous administration of 15 MBq/kg kinetic profiles of various organs in rabbits were investigated by whole-body scintigraphy with a gamma camera. Organ kinetics showed accumulation and excretion via the kidney. No bowel accumulation was observed. Interestingly, increasing tracer uptake in the head region was registered with three of the four tested tracers. Liver accumulation decreased rapidly during the first 40 min. No tracer degradation was registered over the whole time period, as shown by the low thyroid accumulation with a maximum of only 1%. Thus, labelling of ANF and its analogues is possible. These compounds seem to be of interest for further experiments and perhaps clinical studies because of their potential for brain receptor imaging.

Requirements engineering is a discipline within software engineering where model based approaches are still not widespread. Generally requirements are regarded as less or more structured text fragments that are interpreted by stakeholders and developers, who manually manage the requirement interrelationships.In this paper we give an overview over the basic concepts of a model-based requirements engineering approach that is currently developed by the project KOGITO. The focus of this paper is on the presentation of the underlying conceptual model and its relationship to different kinds of requirements specification documents. We present an overview over a domain specific conceptual model that is targeted at the requirements engineering for web-enabled B2B systems. The presented model is capable to manage requirements stemming from various kinds of documents, including B2B standard specifications. Finally we show how these requirements are integrated and related into our conceptual model. Thereby general guidelines for the structure of conceptual models for the requirements engineering are identified.