• Journal of Information Technology Applications and Management
• /
• v.19 no.2
• /
• pp.181-196
• /
• 2012

The cost of software maintenance occupies about two thirds in the software lifecycle. However, it is not easy to estimate the cost of software maintenance because of various viewpoints about software maintenance, unclear estimation methods, and complex procedures. Until now, the cost estimation model has used compensation factors for software characteristic and environment on the basis of program size. Especially, most of existing models use maintenance rate of total software cost as a main variable. This paper suggests the software maintenance cost estimation model that uses the result of calculating real maintenance efforts. In this paper, we classify functional maintenance and non-functional maintenance as software maintenance activity type. For functional maintenance, present function point of target software is needed to evaluate. The suggested maintenance cost evaluation model is applied to a software case in public sector. This paper discusses some differences between our model and other modes.

• Journal of Information Technology Services
• /
• v.9 no.4
• /
• pp.169-185
• /
• 2010

According to software growth, also software maintenance has been continuously improving. In addition, the existing concept of software maintenance process demands operational management and improvement of service task. However, when we perform maintenance task, we have several constraints about applying service based requirement to system. Therefore, in order to solve these problems, we need a study of task of process for service based maintenance. In this paper, we propose a Service based Software Maintenance Process. Proposed process based on MaRMI-RE standard for software development and maintenance and compares it with the service based representative standards. In a related works, we study activity of ITIL and identify activities and tasks for maintenance. After this, identified activities and tasks compare with activities of MaRMI-RE. And then, we derive activities and tasks of a Service based Software Maintenance Process. Finally, we validate a result by comparing the proposed process with a general service operational process.

• Journal of Information Technology Services
• /
• v.14 no.3
• /
• pp.67-84
• /
• 2015

Software is more diverse and complex and the level of importance for the maintenance of application software to securely operate software is also gradually increasing in proportion. The calculation method for maintenance cost of application software applied in Korea public enterprises is involved in the range of 10 to 15% of development cost, depending on the Software Project Cost Estimation Guide. Moreover, as most software maintenance cost estimation procedures do not take into consideration of the risk factors related of maintenance, it can be seen as a main cause for the occurrence of maintenance related accidents. This study proposes a maintenance cost estimate model that takes into consideration of the risks related to the software maintenance activities to improve and resolve issues arising from the estimation of maintenance cost. In doing so, maintenance risk factors are analyzed and a risk index is derived through the analysis of risk levels based on the risk factors. Based on such analysis, a maintenance cost estimate method which reflects the maintenance risk index was established.

• IE interfaces
• /
• v.17 no.spc
• /
• pp.122-130
• /
• 2004

Since the cost of software maintenance occupies about 50~75% in a general successful organization, the software maintenance plays an important role in software life cycle. In particular, if the managed system needs to be operated in a long term or the system is very large and complex, then the maintenance is especially more important. Software maintenance is defined as software modification activities after customer delivery, such as improvement of performance or functionality, error correction, adaptation to environmental changes, etc. In this paper, software cost estimation models are proposed, that is based on productivity of manpower in maintenance projects. In order to do this, the activities of maintenance are classified into function change, non-function change, user support and application operation. The proposed models are constructed and verified based on the real size and cost information of projects in the real world. The approach in this paper is to discriminate the heterogeneous activities in maintenance projects, and then to calculate the respective cost of each discriminated activity. By using the proposed models, the total cost of maintenance project is summed from the costs of four activities. In addition the number of conflicts between owner and order receiver about the amount of cost will be reduced and the reasonable cost estimation system will be established.

• Industrial Engineering and Management Systems
• /
• v.7 no.1
• /
• pp.51-56
• /
• 2008

With growing demand for zero defects, predicting reliability of software systems is gaining importance. Software reliability models are used to estimate the reliability or the number of latent defects in a software product. Most reliability models to estimate the reliability of software in the literature are based on the development lifecycle stages. However, in the maintenance phase, the software needs to be corrected for errors and to be enhanced for the requests from users. These decrease the reliability of software. Software Reliability Growth Models (SRGMs) have been applied successfully to model software reliability in development phase. The software reliability in maintenance phase exhibits many types of systematic or irregular behaviors. These may include cyclic behavior as well as long-term evolutionary trends. The cyclic behavior may involve multiple periodicities and may be asymmetric in nature. In this paper, SGRM has been adapted to develop a reliability prediction model for the software in maintenance phase. The model is established using maintenance data from a commercial shop floor control system. The model is accepted to be used for resource planning and assuring the quality of the maintenance work to the user.

• The Transactions of the Korea Information Processing Society
• /
• v.3 no.4
• /
• pp.846-854
• /
• 1996

In this paper, we propose a solution to the software maintenance problem that is a primary factor of software crisis. We surveyed and analyzed the current software maintenance problems through questionnaires and interviews. As a result, we defined the software maintenance management life cycle and established a fundamental strategies to solve the software maintenance problems efficiently. We also designed a software maintenance management support systems to construct an automated software maintenance management tool. Furthermore, tp improve the formalization and reliability of the software maintenance management procedure, we defined acost predictive model using a fixed-single parameter based on comprehensive program size for the source code and delivered effort(person/month). We elaborated the model by considering an experience level of maintainer, a skill- level defined by the manager, and a reliability level required by the model of maintenance management.

• Journal of Korean Institute of Industrial Engineers
• /
• v.30 no.4
• /
• pp.261-266
• /
• 2004

In this paper, the software reliability growth model which incorporates the periodic maintenance after the release is proposed. Using the proposed model, the debugging and periodic maintenance cost subject to the required level of the software reliability are investigated. An optimal software release time is derived for a fixed interval of periodic maintenance. To validate the proposed model, release times obtained in this study are compared with examples. The proposed investigation is expected to be served as one of factors in determining the release time of the software where periodic maintenance is considered.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.18 no.35
• /
• pp.115-122
• /
• 1995

This paper is developed with software system for the construction of periodic maintenance. The system includes records of equipment, maintenance work, failure mode analysis and work standards of maintenability, inspection & repair to establish periodic maintenance system. And the software program is designed with user-oriented to analyze maintenance data and maintenance system of periodic interval times. Also machine operator can easily apply maintenance management system in production & manufacturing field. Visual Basic in the environment of Window system is used as computer program language for graphics and data base management in IBM PC.

• Journal of Software Engineering Society
• /
• v.26 no.1
• /
• pp.17-29
• /
• 2013

Software System Evolution is more planned and systematic maintenance process as well as a type of maintenance. The research of software evolution provides basis of decisions for maintenance value through cost-benefit analysis of legacy system and architecture-based software evolution enables engineers to reduce maintenance cost by automation of repetitive evolution tasks. This paper proposes a framework for software system evolution using architectural transformation pattern.

• The KIPS Transactions:PartD
• /
• v.16D no.3
• /
• pp.353-360
• /
• 2009

Most information systems are component-based and developed by outsourcing, and developed software is maintained integrative. However, studies on cost measurement indicators and cost estimation model have not been performed sufficiently, which are foundational to enhance the productivity and efficiency of maintenance. This study suggests indicators to measure maintenance cost for component-based software and examines maintenance cost estimation model of component software by the measurement indicators suggested. In order to generate the indicators to measure the component-based maintenance cost, the previously proposed indicators are summarized comparatively. To estimate the measurement indicators of component-based software, it makes a comparison of the previously proposed indicators and arranges them. We classify the measurement indicators by how to apply according to maintenance types of component software and then we propose the cost measurement indicators. Moreover, we propose the cost estimation model according to the maintenance types of component software using the suggested measurement indicators suggested. With the suggested estimation model, a case study is performed and its validity is verified.