Topic
Corrective maintenance
About: Corrective maintenance is a research topic. Over the lifetime, 1638 publications have been published within this topic receiving 22667 citations.
Papers published on a yearly basis
Papers
More filters
IBM1
TL;DR: Studies and experiences are presented which enhance the use of the inspection process and improve its contribution to development of defect-free software on time and at lower cost.
Abstract: Software inspection is a method of static testing to verify that software meets its requirements. It engages the developers and others in a formal process of investigation that usually detects more defects in the product-and at lower cost-than does machine testing. Studies and experiences are presented which enhance the use of the inspection process and improve its contribution to development of defect-free software on time and at lower cost. Examples of benefits are cited followed by descriptions of the inspection process and some methods of obtaining the enhanced results. Users of the method report very significant improvements in quality that are accompanied by lower development costs and greatly reduced maintenance efforts. Excellent results have been obtained by small and large organizations in all aspects of new development as well as in maintenance. There is some evidence that developers who participate in the inspection of their own product actually create fewer defects in subsequent work. Because inspections formalize the development process, productivity-enhancing and quality-enhancing tools can be adopted more easily and rapidly.
735 citations
TL;DR: The fuzzy AHP method proposed in this paper is a simple and effective tool for tackling the uncertainty and imprecision associated with MCDM problems, which might prove beneficial for plant maintenance managers to define the optimum maintenance strategy for each piece of equipment.
468 citations
27 Oct 2008
TL;DR: This paper investigates whether the text of the issues posted in bug tracking systems is enough to classify them into corrective maintenance and other kinds of activities and shows that alternating decision trees, naive Bayes classifiers, and logistic regression can be used to accurately distinguish bugs from other kinds.
Abstract: Bug tracking systems are valuable assets for managing maintenance activities. They are widely used in open-source projects as well as in the software industry. They collect many different kinds of issues: requests for defect fixing, enhancements, refactoring/restructuring activities and organizational issues. These different kinds of issues are simply labeled as "bug" for lack of a better classification support or of knowledge about the possible kinds.This paper investigates whether the text of the issues posted in bug tracking systems is enough to classify them into corrective maintenance and other kinds of activities.We show that alternating decision trees, naive Bayes classifiers, and logistic regression can be used to accurately distinguish bugs from other kinds of issues. Results from empirical studies performed on issues for Mozilla, Eclipse, and JBoss indicate that issues can be classified with between 77% and 82% of correct decisions.
386 citations
TL;DR: This research aims to develop an integrated system to capture information and knowledge of building maintenance operations when/after maintenance is carried out to understand how a building is deteriorating and to support preventive/corrective maintenance decisions.
317 citations
TL;DR: In this article, the effects of machine breakdowns and corrective maintenance on the economic lot sizing decisions are investigated. But the authors focus on the effects on the effect of machine failure on the lot sizing decision.
Abstract: Economic lot sizing and batching models often assume reliable manufacturing facilities. In this research, we focus on the effects of machine breakdowns and corrective maintenance on the economic lot sizing decisions. Two production control policies are proposed for coping with these stochastic interferences. The first policy assumes that production of the interrupted lots is not resumed after a breakdown. Instead, the on-hand inventory is depleted before a new cycle is initiated. Under the second policy studied here, production is immediately resumed after a breakdown, if the current on-hand inventory is below a certain threshold level. It is shown that this control structure is optimal among all stationary policies. We show that under both policies the optimal lot sizes will always be bigger than the ones in a corresponding deterministic case, and that the optimal lot size increases with the failure rate. We also provide exact optimal and closed form approximate lot sizing formulas and derive tight bound...
288 citations