bluuebunny/crossref_metadata_2025_split huggingface dataset:
Parthenium hysterophorus induced changes in neurotransmitter levels in mouse brain
Authors: Verma Sabita , Shrivastava Renu , Prasad P. K. , Shrivastava Vinoy K. 
Published: November 2006

AbstractParthenium hysterophorus (10 mg/0.1 ml/kg body weight) was administered daily to 20 adult male mice and levels of 5‐hydroxytryptamine, noradrenaline and dopamine in total brain were quantified on days 31 and 61 after administration. All neurotransmitter levels were decreased significantly, with the effects more prominent in the later part of the experiment. The results suggest that Parthenium hysterophorus interferes in the functioning of the hypothalamo–hypophyseal axis by impairing the biogenic amine levels which may in turn affect the physiology of the peripheral endocrine glands. Copyright © 2006 John Wiley & Sons, Ltd.
The water extract of Omija protects H9c2 cardiomyoblast cells from hydrogen peroxide through prevention of mitochondrial dysfunction and activation of caspases pathway
Authors: Park Channy , So Hong‐Seob , Shin Sun‐Ho , Choi Jin‐Young , Lee In , Kim Jin‐Kyung , Chung Sang‐Young , Park Raekil 
Published: November 2006

AbstractThe water extract of Omija (Omija) has been used traditionally in the treatment of ischemic damage of the heart and brain tissues. However, little is known about the mechanism by which it rescues myocardial cells from oxidative stress. This study was designed to investigate the protective mechanisms of Omija on H2O2‐induced cytotoxicity in H9c2 cardiomyoblast cells. Treatment with H2O2 resulted in the death of H9c2 cells, characterized by apparent apoptotic features, including fragmentation of the nucleus and an increase in the sub‐G0/G1 fraction of the cell cycle. However, Omija markedly suppressed the apoptotic characteristics of H9c2 cells induced by H2O2. In addition, Omija suppressed the features of mitochondrial dysfunction, including changes in the mitochondrial membrane potential and cytosolic release of cytochrome c in H2O2‐treated cells. Treatment with Omija further inhibited the catalytic activation of caspase‐9 and caspase‐3 and induction of Fas by H2O2. Taken together, these data indicate that the water extract of Omija protects H9c2 cardiomyoblast cells from oxidative stress of H2O2 through inhibition of mitochondrial dysfunction and activation of intrinsic caspase cascades, including caspase‐3 and caspase‐9. Copyright © 2006 John Wiley & Sons, Ltd.
A new approach to determine method detection limits for compound‐specific isotope analysis of volatile organic compounds
Authors: Jochmann Maik A. , Blessing Michaela , Haderlein Stefan B. , Schmidt Torsten C. 
Published: November 2006

AbstractCompound‐specific isotope analysis (CSIA) has been established as a useful tool in the field of environmental science, in particular in the assessment of contaminated sites. What limits the use of gas chromatography/isotope ratio mass spectrometry (GC/IRMS) is the low sensitivity of the method compared with GC/MS analysis; however, the development of suitable extraction and enrichment techniques for important groundwater contaminants will extend the fields of application for GC/IRMS. So far, purge and trap (P&T) is the most effective, known preconcentration technique for on‐line CSIA with the lowest reported method detection limits (MDLs in the low µg/L range). With the goal of improving the sensitivity of a fully automated GC/IRMS analysis method, a commercially available P&T system was modified. The method was evaluated for ten monoaromatic compounds (benzene, toluene, para‐xylene, ethylbenzene, propylbenzene, isopropylbenzene, 1,2,3‐trimethylbenzene, 1,2,4‐trimethylbenzene, 1,3,5‐trimethylbenzene, fluorobenzene) and ten halogenated volatile organic compounds (VOCs) (dichloromethane, cis‐1,2‐dichloroethene, trans‐1,2‐dichloroethene, carbon tetrachloride, chloroform, 1,2‐dichloroethane, trichloroethene, tetrachlorethene, 1,2‐dibromoethane, bromoform). The influence of method parameters, including purge gas flow rates and purge times, on δ13C values of target compounds was evaluated. The P&T method showed good reproducibility, high linearity and small isotopic fractionation. MDLs were determined by consecutive calculation of the δ13C mean values. The last concentration for which the δ13C value was within this iterative interval and for which the standard deviation was lower than ±0.5‰ for triplicate measurements was defined as the MDL. MDLs for monoaromatic compounds between 0.07 and 0.35 µg/L are the lowest values reported so far for continuous‐flow isotope ratio measurements using an automated system. MDLs for halogenated hydrocarbons were between 0.76 and 27 µg/L. The environmental applicability of the P&T‐GC/IRMS method in the low‐µg/L range was demonstrated in a case study on groundwater samples from a former military air field contaminated with VOCs. Copyright © 2006 John Wiley & Sons, Ltd.
The contribution of six developing countries' industry to sustainable development
Authors: Luken Ralph A. , Hesp Paul 
Published: November 2006

AbstractThe extent to which recent changes in industrial development and environmental policies in six countries (Chile, China, Pakistan, Tunisia, Turkey and Zimbabwe) have more closely aligned the objectives of industrial development with those of sustainable development are assessed in this article. The six countries did not make great advances in policy integration in support of sustainable development in the 1990s in terms of policy coordination, cooperation or coherence, but some did better than others. The countries showed considerable variation in the effectiveness with which they implemented their industrial development and environmental policy regimes. Lastly, the impact of industry on sustainable development also varied considerably, depending on which economic, social and environmental parameters were used to assess their contribution. Copyright © 2006 John Wiley & Sons, Ltd and ERP Environment.
SOFTM: A software maintenance expert system in Prolog
Authors: Pau L. F. , Kristinsson J. B. 
Published: November 2006

AbstractThis paper describes a software maintenance knowledge‐based system called SOFTM, which serves the three following purposes: (1) assisting a software programmer or analyst in application code maintenance tasks and reverse engineering, (2) generating and updating automatically software correction documentation, (3) helping the end user register, and possibly interpret, observed errors on the successive application code versions. The knowledge‐based system SOFTM is written in Prolog II, and is largely applicable to application codes written in different programming languages, provided that a description of the application code can be retrieved. SOFTM does not address any of the syntactic, input‐output, or procedural errors normally detected by the syntactic analyser, the compiler, or the operating system environment, although some of these extensions are possible. SOFTM is relying on a unique augmented transition network‐based code description, on diagnostic inference procedures based on context‐based pattern classification, on maintenance log report generators, and on interfacing capabilities of Prolog II to a variety of other languages. It also incorporates features whereby application code specific facts can be retrieved by the operating system (VMS) using a command procedure and asserted directly in the SOFTM knowledge bases. An application case is given for FORTRAN code.
On the benefits and difficulties of a maintainability via metrics methodology
Authors: Lewis John A. , Henry Sallie M. 
Published: November 2006

AbstractA metrics methodology can dramatically reduce the problems associated with software maintenance. However, several issues must be addressed in order to develop and use these techniques successfully. This paper defines a metrics methodology which is designed to deliberately integrate maintainability into software as it is being developed. The benefits of using this approach are discussed. Then several issues which complicate the development and use of the methodology are examined. Previous maintenance studies which incorporate the methodology into two different commercial environments are used to demonstrate the difficulties in implementation and contrast the differences in approach.
Cognitive approach to systems engineering and re‐engineering: Integrating new designs with old systems
Authors: Scandura Joseph M. 
Published: November 2006

AbstractMost MIS expense goes into the maintenance of existing software. Estimates vary from 50% to 60% at the low end up to 90%, even 95%, depending on responsibilities and the type of software. Coming up with better ways to maintain (i.e. understand, modify and update) existing software is unquestionably the most important challenge facing the software industry today.Saddled with obsolete but essential software, a growing number of organizations are faced with a series of unpalatable choices. One option is to simply continue with the same old software, patching it where possible to meet the most pressing needs. This approach has a number of limitations not the least of which are lost opportunity and reduced competitiveness. Moreover, owing to unforeseen and increasing interactions, time per unit of change (especially structural change) tends to increase exponentially throughout the maintenance life cycle.Eventually, old systems must either undergo a major overhaul or be replaced with new ones. Properly done, and implemented, either approach can add a measure of efficiency previously impossible—and cost recovery can often be accomplished over a reasonable period of time. The initial costs involved in such renewal, on the other hand, are often prohibitive.Faced with this dilemma, what are decision makers to do? In this paper, I propose a new approach to system maintenance which can both dramatically improve systems and minimize renewal costs. In turn, I describe a typical maintenance scenario, and consider the use of CASE restructuring tools. Then I show how the human or cognitive factor impinges on the maintenance issue, and how this implies the need for abstraction. Next, we note limitations of standard “bubble chart” and other notational schemes and introduce the FLOWform representation as a means of overcoming these limitations.Finally, with this background, I describe the Cognitive Approach to Systems Engineering and Re‐Engineering (CogApp). In this context, I summarize capabilities of the PRODOC re/NuSys WorkbenchTM which has been used to implement the CogApp. I close with a short case history describing application of this approach, and the results obtained therefrom.
Software maintenance management: Changes in the last decade
Authors: Nosek John T. , Palvia Prashant 
Published: November 2006

AbstractCompared to a decade ago, when the first comprehensive study was done in software maintenance, many changes have occurred in the practice of system development. Longitudinal data were obtained by using the same survey instrument, updated to reflect current practices, and sampling the same population. Comparing the current with 1977 results has helped to identify the persistent problems and issues as well as the emerging problems and issues.One of the important, but somewhat disturbing, conclusions is that maintenance problems are pretty much the same as during the 1970s (except for minor changes), despite advances made in structured methodologies and techniques. In terms of specific problems, personnel problems of maintenance programmers, i.e. turnover and availability, and programmer effectiveness problems, i.e. skills, motivation and productivity, have shown a rise, while problems associated with users' knowledge of computer systems have declined.
European special interest group in software maintenance
Authors: Bennett Keith H. 
Published: November 2006

AbstractA new Special Interest Group in Software Maintenance has been formed in Europe. The idea was initially proposed by the European Commission, which is funding two maintenance projects through the ESPRIT II collaborative programme of Information Technology Research.Membership is open to anyone (European or otherwise) interested in software maintenance. This short article summarizes the objectives and operation of the Special Interest Group.The two ESPRIT software maintenance projects are called MACS and REDO. Between them, these projects bring together researchers and practitioners across the whole of Europe. The belief was (and is) that with this as a basis, there would be many people and organisations who are not yet directly involved, but who would wish to participate in a maintenance‐oriented organisation.
A specification‐based approach to maintenance
Authors: Lano K. , Haughton H. 
Published: November 2006

AbstractIn this paper we define a language, Z++, and a method based upon this language, to support the use of formal methods in software maintenance. Formal methods have been proposed several times as the solution to the growing problem of software maintenance, and we base our approach on the more successful of the attempts made to apply these methods.Our approach is to use a conceptually simple framework, based on an object‐oriented extension to the specification language Z (Spivey, 1989), for dealing with requests for changes to software for which some formal documentation and record of development already exists.The method is centered on the maintenance of the specifications and the development record, not upon source code or Structured Methodology documentation. It is proposed as a practical approach for software in the medium‐term future, allowing the mass of programming detail that makes the code maintenance problem so expensive to be ignored. Therefore changes and extensions to application systems can be made more rapidly. We describe the language and give details of the specification and refinement system, together with a description of the current state of the implementation of this system.
Intelligent search and acquisition of business knowledge from programs
Authors: Karakostas V. 
Published: November 2006

AbstractThis paper discusses the prototype system IRENE which employs concept acquisition techniques in order to retrieve business knowledge from COBOL programs. In contrast with the mainstream of reverse‐engineering techniques, IRENE relies on the availability of semantic (rather than syntactic knowledge), expressed as dependencies and derivations amongst the business entities represented in the program, derived by a process known as domain engineering.
Application of automatic decomposition schemes in proof maintenance for evolving programs
Authors: Gopal R. , Schach S. R. 
Published: November 2006

AbstractThe application of formal verification in software engineering is limited because programs continue to evolve during the maintenance phase, thus rendering the original verification obsolete. Program decomposition schemes can be used to identify the parts of the modified program that need verification. The original program verification can be reused and combined with the verification of the parts of the modified program. Automatic decomposition of programs into independent computational threads called projections can be performed by utilizing program‐dependence relations. These relations represent dependence information among the variables and statements of a program. The individual proofs of each projection can be combined to produce the verification of the entire program. After a modification, many of the original projections may still be present in the new program and they are not re‐verified. Only new projections need verification which is usually easier than re‐verifying the entire program.
Capturing design and maintenance decisions with MACS
Authors: Desclaux Christine 
Published: November 2006

AbstractMACS1 is a research and development project of the European ESPRIT II programme, whose objective is the definition and implementation of a software maintenance assistance system. The basic premise of MACS is to do maintenance through understanding. MACS offers to view the application from several points of view in specific ‘worlds’. One of them is the ‘Reasoning World’, the central subject of the present paper; it captures by means of a simple formalism, the Problem‐Solution‐Decision formalism, the rationale underlying the design and maintenance process. MACS data integration is provided by a central base called the Interconnection World. Moreover, MACS proposes to guide the maintainer in applying a strategy, and in fully exploiting the possibilities of the MACS tools themselves by means of AI techniques and knowledge‐based support; throughout, however, the maintainer remains the master of maintenance actions.
Total quality management for maintenance process improvement
Authors: Schatzberg Doreen R. 
Published: November 2006

AbstractThe acquisition of a new system's operations and maintenance responsibility offered an opportunity to apply different methods in the University of Wisconsin—Extension maintenance organization. Total Quality Management (TQM) methods were chosen because they support broader objectives deemed beneficial to maintenance operations. TQM methods focus on the customer, are implemented through teams, and use data to make decisions rather than relying on inferences or assumptions. The team analyses, assesses, and continually improves the process of maintenance to ensure the product meets customer needs and answers root causes of problems. This paper describes the team's planning, implementation, and validation efforts accomplished, and the findings from the pilot project.In addition to this report on the pilot project, this paper includes several reasons why TQM methods may be particularly amenable to software maintenance functions. They are: (1) the inherent customer‐focus of maintenance activities; (2) the advantages of team work for gaining consensus on improvements, thereby potentially limiting re‐work; and (3) the data‐based, task‐sequenced, structured, analytic techniques used in TQM. Unresolved issues in applying TQM in maintenance organizations include the definition of customer versus user, the need to manage customer expectations, and the application for use in service organizations of techniques honed in manufacturing organizations. This paper is a first step in addressing some of these issues. It provides a preliminary model for applying TQM methods in maintenance organizations.
A semantics‐based method for revalidating modified programs
Authors: Chung In Sang , Kwon Yong Rae 
Published: November 2006

AbstractSoftware revalidation through retesting during the maintenance phase is essential for establishing confidence in the reliability of the modified programs. In this paper, we present a testing criterion and techniques for revalidating modified programs as well as the conditions to determine the necessity for revalidation of the modified program. By comparing programs and identifying the textual and semantic changes between them, it is shown that the number of test cases to be rerun can be reduced compared to the current revalidation methods. Our method is applicable to programs with different control structures from the original program with a little effort by treating the test case reuse problem as a constraint satisfaction problem. In addition, application of an zero‐one integer programming model to select the minimal set of paths to be retested is explored.
A software maintenance management model based on queueing networks
Authors: Papapanagiotakis Giorgos , Breuer Peter 
Published: November 2006

AbstractA model of the software maintenance process within a medium‐sized organization is described. We set out both the abstract model and its implementation as part of a management tool, the Intelligent Software Maintenance Management System (ISMMS) prototype.The ISMMS provides a simulation environment for two sorts of management activities. In interactive mode, the characteristics of a particular set of maintenance tasks can be fed into the simulation, and decisions on the allocation of real personnel, tools and resources tested. In automatic mode, a spectrum of tasks is generated and different automatic allocation strategies are statistically evaluated against these. In both modes, the simulation draws on a database which is customized to accurately reflect the particular resources and characteristics of the organization using the model.The detailed abstract maintenance process underlying the prototype is described in terms of queues arranged in a topological network. This provides a clean conceptual model which has been successfully implemented using a three‐layer software architecture in the ISMMS prototype; the abstract queueing model is implemented as a synchronized predicate‐net which in turn is implemented in Prolog, and we describe the implementation here, as well as its behaviour from the user's point of view.
A decision model to choose between software maintenance and software redevelopment
Authors: Sakthivel Sachidanandam 
Published: November 2006

AbstractStudies show that the maintenance stage of the software life cycle consumes a large proportion of software development resources. They also show that the maintenance cost of a software product increases with age and that it costs less to maintain the redeveloped software product. Thus, it may be worthwhile to redevelop software to reduce the maintenance costs but the redevelopment costs may prohibit this. This paper discusses the nature and behaviour of software maintenance costs and software development costs. In order to minimize the sum of maintenance and development costs for a software product, it recommends and illustrates the use of replacement theory. The replacement model suggested in this paper will be useful for choosing between redeveloping the software and maintaining the existing software. This paper provides a worked example consistent with replacement theory. Since capital is in short supply, replacement projects have to vie with new software and maintenance projects for funding. This paper also describes building a software project portfolio of new software development, software maintenance, and software redevelopment projects.
A road map for migrating legacy systems to client/server
Authors: Mittra Sitansu S. 
Published: November 2006

AbstractApplications developed during the 1970s in a centralized computing environment have become legacy applications in today's decentralized world, increasingly expensive to maintain. One way to improve their use and maintainability in the present environment is to migrate them to the client/server (C/S) world while salvaging as much as possible during that process. This paper, a road map for that migration, examines how legacy applications differ from C/S applications and prescribes a course of action to remove the non‐C/S characteristics from legacy applications and to replace them with C/S characteristics. In this process we need to address a variety of technical issues involving databases, network and configuration management as well as organizational issues such as data and process models used by different parts of the organization, and user/customer training in the new C/S paradigm. The goal of the migration process is to implement an application environment consisting of heterogeneous, distributed, multi‐DBMS applications dynamically linking legacy systems and relational or object‐oriented databases in real time, without the coding costs or challenges of twophase commit. Middleware tools are used widely to re‐engineer legacy applications to fit a C/S environment. A variety of CASE tools are available to support modifying such functions as query and reporting, and cross‐platform development. The paper discusses these issues and concludes with a brief description of resources and tools that can help in travelling the migration road.