• Proceedings of the KIEE Conference
• /
• 2008.04c
• /
• pp.193-195
• /
• 2008

Safety is important factor in railway system. Now most of the electric and electronic system which is applied in railway system is the embedded system which software is used. The constitution rate of software which is involved in railway system is gradually increasing. Most of the software which is used in railway system is implemented by the software developer. Thus the implemented code has different features according to the developer and this may cause the bad effect on the software's maintenance. International standard IEC 62279 requires an adoption the coding standard to developing the railway software. And it is plan to recommend complying with the coding standard in safety criteria for railway software which is noticed as the regulation of the Korean railway safety law. In this paper, we review the requirement of coding standards which is present in the software criteria for railway software and international standard. Also it investigates the coding standard which is in other safety related industry and presents the effective way to apply the software coding standard to domestic railway industry.

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

Software architecture, as a blueprint for the system, should provide a robust foundation for design, implementation, and maintenance, for communication and documentation, and for reasoning about important system properties. Software architecture plays a central role during the whole software life-cycle. There are so diverse definitions of the software architecture, however, and there is no common agreement about what software architecture is. Examining 27 'published' definitions of software architecture, we synthesize an extensive model on the essential elements of software architecture, which consists of components, interaction among components, well-formed structure, reasons, and various perspectives. Further, we explore the possibility of unifying diverse software architecture definitions into a software architecture life-cycle model.

• The KIPS Transactions:PartD
• /
• v.11D no.2
• /
• pp.423-434
• /
• 2004

This paper presents the software system that protects illegal installation and use of the commercial software. The server computer in this system stores the compressed versions for all software, while client computers install all software by downloading them from the server. Also the client computers periodically report to the server whether they have illegally installed software. This system introduces authentication and encryption/decryption using the session key under Windows Operating System to prevent interception of the software package from outside world and malicious modification of the transfer message between the server and the client. The proposed system in this Paper has several advantages such as providing real-time control of license and easy maintenance of the software as well as protecting illegal use of the software.

• Journal of Information Technology Applications and Management
• /
• v.20 no.2
• /
• pp.69-87
• /
• 2013

The expanded spiral model in this paper consists of five processes of architecture design, architectural construction, architectural maintenance, operation, and architectural management. The former four processes are executed alternatively, while the latter architectural management process is executed continuously interacting with the other processes during the whole life cycle of the system. The expanded spiral model provides a conceptual framework to sort discussions of architectural degeneration into those of product-oriented processes and those of management processes, making it possible to incorporate the models and body of knowledge about project and program management especially those of Project Management Institute, into discussions of architectural degeneration. A good architecture decomposes the software-intensive system into components mutually interacting in a well-formed structure. The architecture design process and the architectural construction process together create the object system with well-designed architecture. The architectural maintenance process prevents the implemented architecture deviate from the designed architecture. The architectural management process monitors the changes of requirements including architecturally significant requirements, supports the other processes to be executed reflecting various perspectives of stake-holders, and creates and documents the reasons of architectural decisions, which is considered as a key element of the architecture.

• Journal of Information Processing Systems
• /
• v.17 no.3
• /
• pp.473-488
• /
• 2021

The enterprise resource planning (ERP) system is a standardized and advanced business process that many companies are implementing now-a-days through customization. However, it affects the efficiency of operations as these customizations are based on uniqueness. In this study, we analyzed the impact of customized modules and processing time on customer service request (CSR), by utilizing the stacked CSR data during the construction and operation of ERP, focusing on small and medium-sized enterprises (SMEs). As a result, a positive correlation was found between unit companies and the length of ERP implementation; ERP modules and the length of ERP implementation; ERP modules and unit companies; and the type of ERP implementation and ERP module. In terms of CSR, a comparison of CSR processing time of CBO (customized business object) module and STD (standard) module revealed that while the five modules did not display statistically significant differences, one module demonstrated a statistically very significant difference. In sum, the analysis indicates that the CBO-type CSR and its processing cost are higher than those of STD-type CSR. These results indicate that companies planning to implement an ERP system should consider the ERP module and their customization ratio and level. It not only gives the theoretical validity that should be considered as an indicator for decision making when ERP is constructed, but also its implications on the impact of processing time suggesting that the maintenance costs and project scheduling of ERP software must also be considered. This study is the first to present the degree of impact on the operation and maintenance of customized modules based on actual data and can provide a theoretical basis for applying SW change ratio in the cost estimation of ERP system maintenance.

• Transactions of the Korean Society of Mechanical Engineers A
• /
• v.39 no.11
• /
• pp.1169-1174
• /
• 2015

Risk-Risk-based inspection (RBI) has been developed in order to identify risky equipments that can cause major accidents or damages in large-scale plants. This assessment evaluates the equipment's risk, categorizes their priorities based on risk level, and then determines the urgency of their maintenance or allocates maintenance resources. An earlier version of the risk-based assessment software is already installed within the equipment management system; however, the assessment is based on examination by an inspector, and the results can be influenced by his subjective judgment, rather than assessment being based on failure probability. Moreover, the system is housed within a server, which limits the inspector's work space and time, and such a system can be used only on site. In this paper, the development of independent risk-based assessment software is introduced; this software calculates the failure probability by an analytical method, and analyzes the field inspection results, as well as inspection effectiveness. It can also operate on site, since it can be installed on an independent platform, and has the ability to generate an I/O function for the field inspection results regarding the period for an optimum maintenance cycle. This program will provide useful information not only to the field users who are participating in maintenance, but also to the engineers who need to decide whether to extend the lifecycle of the power machinery or replace only specific components.

• Proceedings of the KSR Conference
• /
• 2000.05a
• /
• pp.284-291
• /
• 2000

Interlocking software used in the electronic interlocking has been implemented through the structured approach until now. But there was the demerit that interlocking software has some problem in the standardization and the maintenance because of the limit in structured approach. Object-Oriented method overcoming this demerit was specified in the design step and the analysis step. There were object model, dynamic model and functional model in the analysis step and there were also two steps which were system design and object design in the design step. In this paper, Interlocking software was designed using Object-Oriented method to improve the standardization and the maintenance of the electronic interlocking. The electronic interlocking was analyzed with object modeling, dynamic modeling and functional modeling.

• Annual Conference of KIPS
• /
• 2009.04a
• /
• pp.50-52
• /
• 2009

Ontology maintenance is a time consuming and costly process which requires special skill and knowledge. It requires joint effort of both ontology engineer and domain specialist to properly maintain ontology and update knowledge in it. This is specially true for medical domain which is highly specialized domain. This paper proposes a novel approach for maintenance and update of existing ontologies in a medical domain. The proposed approach is based on modified Ontology Maturing Process which was originally developed for web domain. The proposed approach provides way to populate medical ontology with new knowledge obtained from medical documents. This is achieved through use of natural language processing techniques and highly specialized medical knowledge bases such as Unified Medical Language System.

• Journal of the Korea Society of Computer and Information
• /
• v.21 no.10
• /
• pp.115-123
• /
• 2016

In this paper, we propose a Model Driven Development using UML(Unified Modeling Language) in an efficient Combat System Software development methods. UML is managed by the OMG (Object Management Group) as a Unified Modeling Language. Recently, In developing the software for the system, development time is contrary to a short, while it must meet a number of requirements of our customers. If you develop a non-efficient software early, the structure of the software become more complex in proportion to the number of requirements. As a result, a serious problem in the system, such as an increase in defective products due to the lowering of the reliability and communication problems between the developer has occurred. To overcome those problems, the aim of this paper is to develop a reusable high efficient Combat System Software by applying Model-Centric Development (Not Code-Centric Development). If Combat System Software development method using the UML proposed in this paper is used, easy communication among developers can help reduce the serious errors in systems. Also, it has the advantage that the future needs of software maintenance/repair become easy by using high readability object Model.

• Journal of KSNVE
• /
• v.4 no.4
• /
• pp.459-467
• /
• 1994

Various maintenance programs and techniques have been implemented for roating machineries, since machines were invented for commerical use. The earliest type of maintenance was run-to-failure, where the machine was run until a fault caused to fail in service. It was obviously an expensive approach due to the unpredictability of the machine condition. Another type is the periodic maintenance, where machines are disassembled and overhauled on regular schedules. With the advent of reliable data collectors including FFT analyzer and developing of versatile supporting software such as ExpertALERT system, the predictive maintenance is known to be the most feasible maintenance type these days. The vibration analysis enables for a maintenance crew to find the exact cause of fault on a machine and to make a proper maintenance schedule with a trend analysis. The predicitive maintenance is considered to be the most important part of pro-active maintenance.