• Proceedings of the KSR Conference
• /
• 2007.11a
• /
• pp.777-783
• /
• 2007

Life cycle costing is one of the most effective cost approaches when we choose a solution from series of alternative so the least long-term cost ownership is achieved. Life cycle costing in railway industry has been focused on the prediction of investment for railway vehicles. But in today, the life cycle cost, LCC, prediction on the aspect of operation and maintenance cost through whole life cycle is highly necessary. In this paper, we present a strategy for the development of life cycle cost estimation software on the aspect of maintenance strategies of railway vehicle. For this purpose, we suggested a structure of LCC software based on the UNIFE LCC model. And we developed a pilot version of software to evaluate the LCC model that we suggested for railway vehicle. We performed LCC analysis on the brake module of metro vehicle in case study and concluded that the software and model developed in this research could enough to support engineers in choosing better cost effective solutions from many alternatives.

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

• International Journal of Safety
• /
• v.3 no.1
• /
• pp.38-46
• /
• 2004

This paper introduces the software life-cycle V&V (verification and validation) tasks for the KNICS (Korea nuclear instrumentation and control system) project. The objectives of the V&V tasks are mainly to develop a programmable logic controller (PLC) for safety critical instrumentation and control (I&C) systems, and then to apply the PLC to developing the prototype of an engineered safety features-component control system (ESF-CCS) in nuclear power plants. As preparative works for the software V&V, various kinds of software plans and V&V task procedures have been developed according to the software life-cycle management. A number of software V&V tools have been adopted or developed to efficiently support the V&V tasks. The V&V techniques employed in this work include a checklist-based review and inspection, a requirement traceability analysis, formal verification, and life-cycle based software testing.

• Proceedings of the Safety Management and Science Conference
• /
• 2007.04a
• /
• pp.425-435
• /
• 2007

This paper presents various information technologies of software product evaluation such as process for evaluators, process for developers, and process for acquirers. This study also introduces system life cycle processes and its application guide.

• Journal of Aerospace System Engineering
• /
• v.6 no.3
• /
• pp.1-6
• /
• 2012

It is booming to use computer owing to the information society, and embedded software application have grown in airborne systems and equipment. So this introduces airborne software, RTCA DO-178B, life cycle and its data, and software development pitfalls in design and certification.

• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.12
• /
• pp.543-548
• /
• 2017

In recent years, the importance of the safety of medical device software has been emphasized because of the function and role of the software among components of the medical device, and because the operation of the medical device software is directly related to the life and safety of the user. To this end, various standards have been set up that provide activities that can effectively ensure the safety of medical devices and provide their respective requirements. The activities that standards provide to ensure the safety of medical device software are largely divided into the development life cycle of medical device software and the risk management process. These two activities should be concurrent with the development process, but there is a limitation that the risk management requirements to be performed at each stage of the medical device software development life cycle are not classified. As a result, developers must analyze the association of standards directly to develop risk management activities during the development of medical devices. Therefore, in this paper, we analyze the relationship between medical device software development life cycle and risk management process, and extract risk management requirement items. It enables efficient and systematic risk management during the development of medical device software by mapping the extracted risk management requirement items to the development life cycle based on the analyzed associations.

• Transactions of the Korean Society of Mechanical Engineers
• /
• v.12 no.6
• /
• pp.1350-1357
• /
• 1988

A computer software was developed for predictions of fatigue crack initiation life of notched members under variable loadings. The software was constructed based on a new fatigue life prediction method utilizing modified .epsilon.-N curves, which can account for the stress interaction effect. The effect of mean plastic strain on low-cycle fatigue life was also incorporated in the software. The software can be utilized for the first step approximation when fundamental data of material fatigue properties are not available.

• Proceedings of the KSR Conference
• /
• 2005.11a
• /
• pp.1033-1038
• /
• 2005

As a global effort to conservate the environment, life cycle assessment(LCA) which considers the environmental impact through the life cycle of a product, from acquiring of resources to scrapping, has been actively applied. The LCA is a tool to calculate quantitatively the environmental impacts caused by products or services through their life cycles. The list of numerous data should be analyzed, stored and conducted in order to assess the environmental impacts. Therefore, it is necessary to develop a software for LCA, which can perform the interpretation as well as the environment impact assessment to execute the analysis of such a large number of data effectively. At this time, for the existing some kinds of general LCA softwares, the information about all of input and output should be fed directly and the conclusion is deduced by linking to the database from the public authorized organizations. That makes it possible to evaluate the environmental grades accurately, but it is too slow and difficult for general users to operate and applied it into an electric motor unit(EMU). Therefore, in this research, the basic model was designed, which is based on construction of database structure of the software and organization of architecture, to develop an advanced software for EMU according to user and purpose of it by benchmarking of domestic and international softwares. The result of this study would be applied to develop the LCA software in the future.

• The Korean Journal of Applied Statistics
• /
• v.23 no.3
• /
• pp.573-584
• /
• 2010

This paper considers the differences in the software execution environments in the testing phase and the operational phase to determine the optimal release time and warranty period of software systems. We formulate equations for the total expected software cost until the end of the software life cycle based on the NHPP. In addition, we derive the optimal release time that minimizes the total expected software cost for an imperfect debugging software reliability model. Finally, we analyze the sensitivity of the optimal testing and maintenance design related to variation of the cost model parameters based on the fault data observed in the actual testing process, and discuss the quantitative properties of the proposed model.