• Tribology and Lubricants
• /
• v.30 no.3
• /
• pp.168-176
• /
• 2014

This paper presents an engine oil change warning algorithm based on the test results of a small dip-stick-gage-type engine-oil-deterioration-detection sensor, software to realize the algorithm and a display device to apply the software. The algorithm determines the engine oil deterioration condition from the rate of change in the dielectric constant based on the average measured capacitance at $80^{\circ}C$ after the engine stops. The rate of change in the dielectric constant at the time for oil change correlates with the time that one of recommended warning limits for engine oil physical properties such as TAN (Total Acid Number), TBN (Total Base Number) and viscosity is first reached. At this point, a warning signal for oil change appears on the display device like a smart-phone or individual display device. The frames of smartphone app have three stages. The user can directly input all of the thresholds into the frame of the smartphone app. The screen of the display device comprises one frame for each warning signature with the related message. The user can input the thresholds to the device through a USB cable connected to a personal computer.

• Proceedings of the KSR Conference
• /
• 2008.06a
• /
• pp.952-963
• /
• 2008

The collection of KTX trainset fault code is made by DEP software. We can improve software function and update data after understanding DEP software function and software structure. For the improvement of trainset function and its performance, the same improvement of performance and structure change as DEP software, which collects and analyzes train's fault information, are required. Accordingly, we made a research for functional strucfure of KTX fault code collection software, STR3F, variable declaration through Script.rxr file and code analysis method and proceeded research for realizing more improved user environment of DEL software and fault analysis method.

• Journal of Software Assessment and Valuation
• /
• v.16 no.1
• /
• pp.21-26
• /
• 2020

The completeness appraisal of software is performed in various forms, such as assessing the completion level in the development process, calculating the defect rate, estimating the development cost, and calculating the redevelopment cost. Along with this, the problem that is often dealt with is estimation of the development time. Even in a dispute over completeness due to delays in software development, issues of calculating an appropriate development time required to develop a delivery software or a development time required for change requests are often included in the appraisal request. In this paper, we introduce the procedure and method for estimating the appropriate project time of software development so that the appraiser can be applied to the appraisal work for determining the completeness. The method is based on the manual for calculating the appropriate project period of software development project.

• Journal of Information Technology Services
• /
• v.7 no.2
• /
• pp.41-57
• /
• 2008

The development of service-based software and web-based application aims for providing user-demand service. On-demand software is emerging for same reason. Software delivery models like on-demand software is expected to change the software industry as an important technical revolution with the firm's strategy. Few research, however, has been done on the on-demand software. While much research on ASP and SaaS focused on firm' use, this study intends to examine the intention of using on-demand software targeting personal user. The intention to use of on-demand software was empirically examined in terms of quality, user characteristics, usefulness, easy of use, and security. Results shows that usefulness and easy of use are most significantly related to the intention of using on-demand software. Other factors are also found to affect the intention to use of on-demand software. This study contributes to improve the understanding and interest in on-demand software and it is expected to spread widely for individual user.

• Information Systems Review
• /
• v.11 no.3
• /
• pp.125-146
• /
• 2009

The emergence of open source software(OSS) with its most prominent advantages creates a vast interest among practitioners. A study on Linux, the most well-known OSS, estimated that it would cost as 5.4 billion Euros taking over 73,000 person-years if it had been developed by conventional means. However, Linux has achieved only 0.65 percent of the operating system market for individual users while Microsoft windows family counts for nearly 90 percent of the market. Much of the effort being spent in the development of OSS is going to waste and potential value that OSS can bring to users is not being realized. Adoption of OSS is often accompanied by the discontinuance of existing software that is already in place. If users resist changing, they may not adopt OSS. Using the case of Linux, this study examines user resistance to change from the commercial operating software to the free operating system. This study identifies six sub-types of switching costs (uncertainty, emotional, setup, learning, lost benefit, and sunk costs) and tests their effects on user resistance to change based on a survey of 201 users. The results show that user resistance to change has a negative impact on the adoption of OSS. Further, this study shows that uncertainty and emotional costs have significant effects on user resistance to change. Beyond previous research on technology adoption, this research contributes towards an understanding of the switching costs leading to user resistance to change and offers suggestions to OSS practitioners for developing strategies to improve the adoption of OSS.

• Journal of Digital Convergence
• /
• v.10 no.1
• /
• pp.335-339
• /
• 2012

Software configuration management is a field of managing sets of large scale software outputs to be the basis of the software products. Configuration management has significantly improved for the past few years, yet new system is still required. Instead of using previous methods or researching about configuration management, professional management of developing project is needed. Therefore, techniques such as storage model for configuration management, management program for change procedure and management of program interface is needed. In this paper, we provide storage for configuration management and implement decision-making system to manage divided program and interface. Thus, we propose a new access method by the configuration management dependency. This paper provides configuration management for developing software to verify and classify using decision-making system for the change and combination of independent components with high dependency.

• The Korean Journal of Applied Statistics
• /
• v.21 no.5
• /
• pp.813-823
• /
• 2008

The non-homogeneous Poisson process(NHPP) based software reliability growth models are proved quite successful in practical software reliability engineering. The fault detection rate is usually assumed to be the continuous and monotonic function. However, the fault detection rate can be affected by many factors such as the testing strategy, running environment and resource allocation. This paper describes a parameter estimation of software reliability growth model with change-point problem. We obtain the maximum likelihood estimate(MLE) and least square estimate(LSE), and compare goodness-of-fit.

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

• Communications for Statistical Applications and Methods
• /
• v.10 no.2
• /
• pp.353-359
• /
• 2003

This paper deals with the problem of testing mean change with one change-point with the normal random variables. We propose a test with the mean difference for change in a location parameter. A power comparison study of various change-point test statistics is performed via Monte Carlo simulation with S-plus software.

• The Journal of Society for e-Business Studies
• /
• v.12 no.3
• /
• pp.33-47
• /
• 2007

The requirements have been changed during development progresses, since it is impossible to define all of software requirements. These requirements change leads to mistakes because the developers cannot completely understand the software's structure and behavior, or they cannot discover all parts affected by a change. Requirement changes have to be managed and assessed to ensure that they are feasible, make economic sense and contribute to the business needs of the customer organization. We propose a feature-oriented requirements change management method to manage requirements change with value analysis and feature-oriented traceability links including intermediate catalysis using features. Our approach offers two contributions to the study of requirements change: (1) We define requirements change tree to make user requirements change request generalize by feature level. (2) We provide overall process such as change request normalization, change impact analysis, solution dealing with change request, change request implementation, change request evaluation. In addition, we especially present the results of a case study which is carried out in asset management portal system in details.