• Journal of the Korea Society of Computer and Information
• /
• v.27 no.1
• /
• pp.51-59
• /
• 2022

As the weapon system's dependence on software functions increased, software became a key factor in controlling the weapon system. In addition, as software development becomes more important domestically and internationally, software verification becomes an issue. The recent defense market has recognized this point and is demanding a plan for weapon system software maintenance. In this paper, we propose a weapon system software maintenance plan using Automatic Test Equipment. The specific method is to use a simulator to check the software function and identify failure cases. This is an effective way for developers to reduce the Total Corrective Maintenance Time(TCM) of the weapon system by reducing the time it takes to identify failure cases. It has been proven that the proposed Automatic Test Equipment can achieve software maintenance and excellent Maintainability and Operational Availability compared to the existing ones.

• Journal of Information Technology Applications and Management
• /
• v.22 no.3
• /
• pp.143-167
• /
• 2015

This paper addresses the issue how the total life cycle cost may be minimized and how the cost should be allocated to the acquirer and developer. This paper differentiates post life cycle change (PLCC) endeavors from PLCC activities, rigorously classifies PLCC endeavors according to the result of PLCC endeavors, and rigorously defines the life cycle cost of a software product. This paper reviews classical definitions of software 'maintenance' types and proposes a new typology of PLCC activities too. The proposed classification schemes are exhaustive and mutually exclusive, and provide a new paradigm to review existing literatures regarding software cost estimation, software 'maintenance,' software evolution, and software architecture from a new perspective. This paper argues that the long-term interest of the acquirer is not protected properly because warranty period is typically too short and because the main concern of warranty service is given to removing the defects detected easily. Based on the observation that defects are caused solely by errors the developer has committed for software while defects are often induced by using for hardware (so, this paper cautiously proposes not to use the term 'maintenance' at all for software), this paper argues that the cost to remove defects should not be borne by the acquirer for software.

• Journal of Digital Contents Society
• /
• v.11 no.4
• /
• pp.537-543
• /
• 2010

According to software growth, also software maintenance has been continuously improving. In addition, the existing concept of correct maintenance demands operational management and improvement of service. However, we have various limitation matters to reflect the requirements of service base for maintenance accomplishment. Therefore, we need the study of the service based process for solving such a problem. In this paper, we propose a Service based Software Maintenance Process. Proposed process based on ISO12207 standard for software development and maintenance and compares it with the service based representative standards. In a related works, we study activity of $SM^{MM}$, ITSCMM, ITIL and find out activities to be concerned with and compare it with activity of ISO 12207 and distinguish the maintenance process activity of the service base from maintenance activities. And then, we propose a service management stage. It define four activities and eight artifacts. Finally, we validate the result by comparing the proposed process with a general service operational process.

• Journal of the Korea Society of Computer and Information
• /
• v.23 no.4
• /
• pp.97-106
• /
• 2018

Software maintenance activities have always been important issues in many domains of the software industry. In order to help to resolve this issue, software modularization approaches have been studied to build adequate modules with high cohesion and low coupling; such modular structures can help the comprehension and maintenance of complex systems. In this paper, we propose a GUI-based automated approach for software modularization based on GUI structure analysis. GUI is a principal manner to allow users to access the overall functionalities of a software system; in particular, GUI is closely related to software functionalities, which makes it a promising tool to identify and understand the entire software system. We also implement a software tool to support our approach and evaluate it with a case study using an open source software.

• International Journal of Computer Science & Network Security
• /
• v.22 no.3
• /
• pp.229-235
• /
• 2022

The process of correcting, upgrading, and improving software products after they have been handed over to the consumer is known as software maintenance. Offshore software maintenance outsourcing (OSMO) clients benefit from cost savings, time savings, and improved quality software through OSMO. In most circumstances, the OSMO vendor makes a lot of money but not in all the cases. Especially, when the OSMO project offer is not properly assessed. An efficient outsourcing contract might yield successful outcomes for outsourced projects. But before sending a detailed proposal to bid on the OSMO project the vendor must have to assess the client's project (business offer) requirements. The purpose of this study is to find out common trends within the assessment of a OSMO project. A case study approach along with semi-structured interviews from eight companies concluded ten common practices and several roles. Among these practices, four (code structure, requirements, communication barriers and required infrastructure) were consistent amongst the responses .The findings, limitations and future work are discussed.

• The KIPS Transactions:PartD
• /
• v.15D no.1
• /
• pp.107-112
• /
• 2008

The maintenance of legacy software systems is very important in the field of a software engineering. In the maintenance, a regression test confirms the behavior preserving of the software which has been changed but most of regression tests are done in a system level and rarely done in a unit test level because there is no test case. This paper proposes how to modify legacy software systems and make unit test cases as an asset. It uses a technique with a specific module of a real software development project and analyzes test coverage results. After this, if a study about automatic restructuring techniques and a test case generation proceeds continuously, we can expect the big advance of legacy software systems maintenance.

• Journal of KIISE:Software and Applications
• /
• v.31 no.5
• /
• pp.555-562
• /
• 2004

Software industry has put more emphasis on maintenance and enhancement work than on the new development. The existing effort estimation models can still be applied to maintenance projects, though modifications are needed. This paper suggests a way to estimate the size of a maintenance project from the regression analysis of ISBSG's benchmarking data. First of all, among the 3 elements(addition, modification and deletion of the program) which influences the software cost, we selected and classified 4 groups from a total of 8 which shows actual maintenance cost from ISBSG's data. Moreover, we developed statistical model and a model which uses RBF(Radial Basis Function) Network and after evaluating each functions we concluded that the RBF Network is superior to the statistical model.

• Journal of Information Technology Services
• /
• v.8 no.1
• /
• pp.99-111
• /
• 2009

Rapid growth of Management Information System (MIS) and evolution of software system enlarge maintenance necessity and it needs a process to implement information system service in business. This paper proposes service-oriented maintenance process of component software based on service design and implementation provided by existing processes for maintenance, MaRMI-RE and ITIL. The proposed process derives activities and tasks of the process by identifying services according to service guidelines. Service-oriented maintenance process is produced by analyzing correlation between the derived activities and tasks and MaRMI-RE's and adding the tasks to MaRMI-RE. To verify availability of the proposed service-oriented maintenance process, correlation between artifacts is proved.

• International Journal of Internet, Broadcasting and Communication
• /
• v.15 no.2
• /
• pp.168-174
• /
• 2023

In the current world, with the massive scale of SOC construction, it is difficult to diagnose and check all of a bridge's abnormal states with even the experts' eyes for maintenance. It is because we should spend huge costs and time on maintenance. Still, there are not many alternative ways to inspect bridges remotely regarding accuracy or reality. Therefore, we remark on the advantages and disadvantages of previous methods through practices in SOC maintenance. To inspect the abnormal state of the Bridge, we suggest inspecting bridges with an Augmented Reality (AR) mechanism to reduce cost, human resource consumption, and the risk of work. Through the proposed approach, we expect that it provides ways to solve massive construction problems with software-based technologies.

• Journal of the Korea Society of Computer and Information
• /
• v.4 no.2
• /
• pp.61-69
• /
• 1999

In this study, the productivity factors of software maintenance are categorized into the three areas such as maintainer characteristics, software technical characteristics and maintenance environment characteristics. And the various regression analyses are performed for searching the most significant model by using actual project's data. At conclusion, an linear model including new variables derived from factor analysis to estimate the effort for software maintenance project is suggested.