C++ Code (c++ + code)

Distribution by Scientific Domains
Medical Sciences50%

Selected Abstracts

Novel software architecture for rapid development of magnetic resonance applications

CONCEPTS IN MAGNETIC RESONANCE, Issue 3 2002
Josef Debbins
Abstract As the pace of clinical magnetic resonance (MR) procedures grows, the need for an MR scanner software platform on which developers can rapidly prototype, validate, and produce product applications becomes paramount. A software architecture has been developed for a commercial MR scanner that employs state of the art software technologies including Java, C++, DICOM, XML, and so forth. This system permits graphical (drag and drop) assembly of applications built on simple processing building blocks, including pulse sequences, a user interface, reconstruction and postprocessing, and database control. The application developer (researcher or commercial) can assemble these building blocks to create custom applications. The developer can also write source code directly to create new building blocks and add these to the collection of components, which can be distributed worldwide over the internet. The application software and its components are developed in Java, which assures platform portability across any host computer that supports a Java Virtual Machine. The downloaded executable portion of the application is executed in compiled C++ code, which assures mission-critical real-time execution during fast MR acquisition and data processing on dedicated embedded hardware that supports C or C++. This combination permits flexible and rapid MR application development across virtually any combination of computer configurations and operating systems, and yet it allows for very high performance execution on actual scanner hardware. Applications, including prescan, are inherently real-time enabled and can be aggregated and customized to form "superapplications," wherein one or more applications work with another to accomplish the clinical objective with a very high transition speed between applications. © 2002 Wiley Periodicals, Inc. Concepts in Magnetic Resonance (Magn Reson Engineering) 15: 216,237, 2002 [source]

Selective Arterial Distribution of Cerebral Hyperperfusion in Fabry Disease

JOURNAL OF NEUROIMAGING, Issue 3 2001
David F. Moore MD
ABSTRACT Fabry disease is an X-linked recessive deficiency of lysosomal ,-galactosidase A associated with an increased risk of early onset cerebrovascular disease. The disorder is reported to affect the posterior circulation predominantly. This hypothesis was investigated directly by the measurement of regional cerebral blood flow with positron emission tomography (PET). Resting regional cerebral blood flow (rCBF) in 26 hemizygous patients with Fabry disease and 10 control participants was examined using H215O and PET. Statistical parametric mapping (SPM{t}, SPM99) and PET images of patients and controls were produced. Significantly increased SPM{t} clusters were then color coded and blended with a coregistered T1 magnetic resonance imaging (MRI) template. Cerebral arterial territory maps were digitized and rescaled. Custom OpenGL and ImageVision Library C++ code was written to allow a first-order affine transformation of the blended SPM{t} and MRI template onto the arterial territory map. The affine transformation was constrained by choosing corresponding cerebral landmark "tie points" between the SPM{t}, MRI template images and the cerebral arterial territory maps. The data demonstrated that the posterior circulation is the predominant arterial territory with a significantly increased rCBF in Fabry disease. No arterial distribution had a decreased rCBF. [source]

Experience report on using object-oriented design for software maintenance

JOURNAL OF SOFTWARE MAINTENANCE AND EVOLUTION: RESEARCH AND PRACTICE, Issue 3 2007
Norman F. Schneidewind
Abstract We experimented with modifying the existing object-oriented (OO) design and C++ code of a software reliability model. Our purpose was to assess the efficacy of OO methods for performing maintenance on mathematical software, using a real-world system (NASA Space Shuttle flight software) to illustrate the approach. In this process, we used variants of UML diagrams to modify our design. We found that although a top-down approach to software maintenance is normally a good idea, it was still necessary to modify the design once the realities of what could be accomplished in the C++ code came to light. As reliability and maintenance are intimately related, we developed reliability risk analysis to show how maintenance changes to our design and code could be used to measure risk. Another maintenance enhancement to the design and code is the use of reliability parameter analysis to assess, in the advance of prediction, the reliability of a set of software releases. We believe this is the first evaluation of software maintenance using OO methods. Copyright © 2007 John Wiley & Sons, Ltd. [source]

Latitudinal and longitudinal process diversity

JOURNAL OF SOFTWARE MAINTENANCE AND EVOLUTION: RESEARCH AND PRACTICE, Issue 1 2003
Nils T Siebel
Abstract Software processes vary across organizations and over time. Managing this process diversity is a delicate balancing act between creative, healthy diversity and chaos. In this paper, we examine a particular aspect of this issue, namely some relationships between diversity in software processes, software evolution and the quality of software products and processes. Our main contribution is to distinguish between two broad kinds of process diversity, which we call latitudinal and longitudinal process diversity. To illustrate the differences between these two, we examine the case of a medium-sized system (50,000 lines of C++ code) which has undergone major changes during its lifetime of 10 years. The software was originally developed by an individual academic using a research-oriented process to develop a standalone proof-of-concept system. In a current multi-team project, involving three industrial and three academic partners, the software has been adapted for integration as a subsystem of a near-market product. We suggest ways in which the observed process diversity seems to be linked to a change in the software's propensity for evolution, and we discuss the impact of this on both product and process quality. Copyright © 2003 John Wiley & Sons, Ltd. [source]