• 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 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 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.

• Journal of Korean Institute of Industrial Engineers
• /
• v.33 no.4
• /
• pp.487-493
• /
• 2007

In this paper, we deal with an optimal software-release problem of determining the time to stop testing and release the software system to the user. The optimal release time problem is considered from maintenance like the periodic distribution of service packs and the unpredictable distribution of patches after the release. Moreover, the environment of software error-detection during operation differs from the environment during testing. This paper proposes the software reliability growth model which incorporates periodic service packs, unpredictable patches and operational environment. Based on the proposed model, we derive optimal release time to minimize total cost composed of fixing an error, testing and maintenance. Using numerical examples, optimal release time is determined and illustrated.

• 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 KIISE:Software and Applications
• /
• v.36 no.9
• /
• pp.718-731
• /
• 2009

Software Maintenance needs to continually improve from corrective maintenance to operational management and service improvement. In this study, we propose a software maintenance maturity model and its evaluation criteria based on 4 maintenance projects of K organization. For the proposal, we derive 13 process areas and 64 evaluation criteria based on some references such as SMMM, ITSMM, ITIL. We evaluate the criteria using 5-point scale, and then establish the maturity model of K organization classified by levels of the maturity model based on the evaluation result. And, to verify and improve the maturity model of K organization, we propose improvements for evaluation criteria. In addition, we apply the maturity model to the 4 projects, evaluate the projects, and propose improvements for the projects based on the evaluation result to identify how the model shows software maintenance improvement.

• Journal of the Korea Society of Computer and Information
• /
• v.22 no.9
• /
• pp.25-32
• /
• 2017

In this paper, we propose the softwareization of broadcasting system. Recently, the topic of industry is the fourth industrial revolution. The fourth industrial revolution is evolving from physical to virtualization. The Industrial Revolution is based on IT technology. Artificial Intelligence (AI), Big Data, and the Internet of Things, which are famous for Alpha Go, are based on software. Among IT, software is the main driver of industrial terrain change. The systemization of software on the basis of cloud environment is proceeding rapidly. System development through softwarization can reduce time to market lead time, hardware cost reduction and manual operation compared to existing hardware system. By developing and implementing broadcasting system such as IPTV based on cloud, lead time for opening service compared to existing hardware system can be shortened by more than 90% and investment cost can be saved by about 40%. In addition, the area of the system can be reduced by 50%. In addition, efficiency can be improved between infrastructures, shortening of trouble handling and ease of maintenance. Finally, we can improve customer experience through rapid service opening.

• Journal of Information Technology Services
• /
• v.16 no.2
• /
• pp.45-60
• /
• 2017

The study suggests a contract model of application operation through case study of A bank's IT outsourcing application contract based on workload. The IT outsourcing order form has a problem in that the scope of work is ambiguous due to the integration of operation and maintenance. In this study, application operation and maintenance were separated by referring to application operation history provided in ISO/IEC15504-5 standard. The scope of the IT outsourcing service was clarified by organizing the definition and detail activities of the application operation business. Application operation contract method has generally applied estimation method by the number of input manpower and period by agreement between buyer and client. As there is no activity to calculate the number of input manpower based on the operational work history and based on the standard workload per activity. In this case is not guaranteed due to the simple agreement between the contractors. In this paper, we propose an application operating cost estimation model that measures the size of the operating software using function point analysis that is the basis of application operation tasks. In order to verify the validity of the application operation cost model, we verified the correlation between the application size and the labor cost through regression analysis using SPSS.

• The Transactions of the Korea Information Processing Society
• /
• v.2 no.2
• /
• pp.168-175
• /
• 1995

It has been commonly accepted for a while that a successful tool environment must provide for smooth interfaces between its tools. Recent integrated CASE environment must be-based on well-integrated data repository which supports a tightly coupled, consistent environment. For the maintenance tool, it requires a careful design of the maintenance chest's database. Information about a program exists in many different forms after analyses have been performed. It must be possible to associate and select objects for data repository from this information as necessary. This paper suggests a new integrated scheme for the data repository in building software maintenancec environment. The scheme provides many basic services, including storage and management of objects/entities and links/ relations; version and configuration control, query service, data interchange service.

• Proceedings of the Korean Society for Noise and Vibration Engineering Conference
• /
• 2003.11a
• /
• pp.602-607
• /
• 2003

Sensors based bridge monitoring system (SBBMS) is designed to perform real-time monitoring and to store the performance history of in-service bridges. In general, visual inspections play a major role in maintenance of in-service bridges; however, they are not adequate to document the behavior of a bridge. Therefore, visual inspections and sensor based monitoring systems complement each other. Sensor based bridge monitoring systems consist of hardware and software systems. The hardware system contains the sensors and data-loggers to measure the behavior of a structure, the communicational equipment to transmit the measured data from the site to the monitoring center, and the computers to arrange and analyze the data. The software system controls data-loggers, arranges and analyzes the measured data, makes real-time display, stores the performance history.