• IE interfaces
• /
• v.19 no.3
• /
• pp.181-189
• /
• 2006

This study introduces an overall framework for RFID applications in product lifecycle management(PLM). PLM is a new strategic approach to manage product related information efficiently over the whole product lifecycle. Recently, with emerging technologies such as radio frequency identification(RFID), global positioning system(GPS), and wireless communication, PLM provides a new environment that enables us to gather and analyze product lifecycle information, and make decisions on several issues without spatial and temporal constrains. However, a PLM system just provides us with new opportunities to gain the PLM system, first and foremost, it is necessary to look into its overall framework in the viewpoint of hardware, software, and business model. For this purpose, in this study, first, we introduce the technical framework of the new PLM environment with the concept of extended RFID system, called product embedded information device(PEID). Then, for each lifecycle phase such as beginning of life(BOL), middle of life(MOL), and end of life(EOL), we explore several research problems that become highlighted under the new PLM environment.

• Journal of Information Processing Systems
• /
• v.6 no.1
• /
• pp.91-106
• /
• 2010

The rapid growth of communication and globalization has changed the software engineering process. Security has become a crucial component of any software system. However, software developers often lack the knowledge and skills needed to develop secure software. Clearly, the creation of secure software requires more than simply mandating the use of a secure software development lifecycle; the components produced by each stage of the lifecycle must be correctly implemented for the resulting system to achieve its intended goals. This study demonstrates that a more effective approach to the development of secure software can result from the integration of carefully selected security patterns into appropriate stages of the software development lifecycle to ensure that security designs are correctly implemented. The goal of this study is to provide developers with an Integrated Security Development Framework (ISDF) that can assist them in building more secure software.

• Journal of the Korean Society of Systems Engineering
• /
• v.14 no.2
• /
• pp.49-57
• /
• 2018

The main objective of this paper is come up with methodology approach for FPGA-based system in verification and validation lifecycle regarding software reliability using system engineering approach. The steps of both reverse engineering and re-engineering are carried out to implement an FPGA-based of safety critical system in Nuclear Power Plant. The reverse engineering methodology is applied to elicit the requirements of the system as well as gain understanding of the current life cycle and V&V activities of FPGA based-system. The re-engineering method is carried out to get a new methodology approach of software reliability, particularly Software Reliability Growth Model. For measure the software reliability of a given FPGA-based system, the following steps are executed as; requirements definition and measurement, evaluation of candidate reliability model, and the validation of the selected system. As conclusion, a new methodology approach for software reliability measurement using software reliability growth model is developed.

• Journal of Internet Computing and Services
• /
• v.5 no.4
• /
• pp.95-113
• /
• 2004

RUP(Rational Unified Process) is a development process which is based on object-oriented, use case centric, architecture centric, and iterative approach. Public projects performed previously adopt waterfall lifecycle model for development of large scale software. However, recently various projects adopt an iterative approach to minimize risks of a project and to enhance quality of software. But few research result on practices of RUP as the subprocess of system development process is available. This paper presents a system development process which uses RUP as the subprocess for a subset of the system. Thus we introduce a tailored RUP for K-CIS(Korean Core Instrumentation System). Moreover, we assess the application result of K-CIS with typical waterfall lifecycle model and RUP. We believe that the results of our work are useful for tailoring a system development process with RUP, reducing risks of development, and enhancing the quality of a final product.

• Industrial Engineering and Management Systems
• /
• v.15 no.2
• /
• pp.181-195
• /
• 2016

In a product environment where various product-service systems (PSSs) are already being provided, the provision of a different type of PSS is difficult for second movers but necessary for their sustainability and differentiation. Despite the importance of providing distinguishing PSSs to market, prior PSS studies have not effectively considered the influence of existing PSSs in their methods. In response, we suggest an approach to generate new PSS concepts by employing general needs (GNs) and business system evolution patterns (BSEPs). Our approach 1) identifies customer GNs fulfilled by existing PSSs, 2) generates advanced PSS ideas from an evolutionary perspective by mapping the existing PSSs onto BSEPs, and 3) selects PSS ideas that can meet the unfulfilled or insufficiently considered GNs using a GN-PSS linking matrix, thereby generating new PSS concepts based on the selected ideas. The workings and practicability of this approach are illustrated using a PSS case study of furniture industry. This approach would provide PSS planners with an ability to generate the differentiated PSS concepts that handle the customer needs that have been untapped throughout a product's lifecycle. In addition, this approach as a module will have a synergetic effect when incorporated with other PSS methodologies.

• Journal of the Korea Concrete Institute
• /
• v.26 no.2
• /
• pp.201-210
• /
• 2014

The present study proposes a phased model to assess the lifecycle $CO_2$ amount of concrete structures. The considered system boundary is from cradle to recycling, which includes constituent material, transportation, batching and mixing in ready-mixed concrete plant, use and demolition of structure, and crushing and recycling of demolished concrete. The $CO_2$ uptake of concrete by carbonation during lifetime (40 years) of a structure and the recycling life (20 years) after demolition is estimated using a simple approach generalized to predict the carbonation depth from the surfaces of concrete element and recycled aggregates. Based on the proposed phased model, a performance evaluation table is realized to straightforwardly examine the lifecycle $CO_2$ amount of concrete structures. The proposed model demonstrates that the contribution of ordinary portland cement (OPC) to lifecycle $CO_2$ emission of the concrete structure occupies approximately 85%. Furthermore, the $CO_2$ uptake is estimated to be approximately 15~18% of the lifecycle $CO_2$ emissions of concrete structures, which corresponds to be 19~22% of the emissions from OPC production. Overall, the proposed $CO_2$ performance table is expected to be practically useful as a guideline to determine the $CO_2$ emission or uptake at each phase of concrete structures.

• The Journal of Information Systems
• /
• v.31 no.1
• /
• pp.239-269
• /
• 2022

Purpose This paper attempts to identify items for improving the usage of PLM(Product Lifecycle Management) systems and suggests ways to prioritize improvement items on the basis of importance. It also tries to find out differences in the importance of improvement items due to the company size, the industry, the job, or the PLM solution. Design/methodology/approach Through a survey from participants to a PLM System Conference, data were collected from a sample of 181 users who had the previous experience in using a PLM system. In order to figure out the differences in the importance among user groups, the F-test with the Scheffe test as a post-hoc analysis was used in case of equal variances and the Welch test with the Dunnett T3 test was used in case of unequal variances. Findings This study sorted out 25 improvement ideas according to their importance assessed by the PLM system users. The top five ideas are improving data consistency, error minimization, fast system response time, enhancing user recognition, and business process improvement. The support group puts higher importance than the general user group in data consistency, fast system response time, enhancing user recognition, business process improvement, dedicated team for data consistency, continuous support from management, hardware performance upgrade, output linkage to other systems, and shortening problem solving duration. The largest company group attaches significantly higher weights than the smallest company group to data consistency, error minimization, fast system response time, business process improvement, dedicated team for data consistency, security with proper access management, output linkage to other systems, and better user interface.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.13 no.5
• /
• pp.808-817
• /
• 2010

This paper proposes a novel appoach which can assess the system technical maturity for use in Defense R&D Program reviews. As the weapon systems become more complicated, the success and effectiveness of R&D outcome heavily depend on the application and tailoring of systems engineering process and methods. It is a difficult task to assess the system readiness level(SRL) of the system being developed. A system-focused approach for managing weapon systems development and making effective and efficient decisions during the development lifecycle is critical to ensure the success of the program. The proposed weighted average SRL can facilitate the system technical maturity assessment without expending heavy work load.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.18 no.11
• /
• pp.31-45
• /
• 2017

According to the railway accident statistics in recent years, the frequency of accidents has been significantly reduced, due to the advance of related technologies and the establishment of safety information management systems. Nonetheless, accidents due to errors in the operation and maintenance phase and faults in safety design continue to occur. Therefore, to prevent accidents, guidelines for the safety design and manufacture of railway vehicles were established, and a request for the independent safety evaluation of safety designs was made. To respond to this, rail system developers must prepare safety cases as a safety activity product. One of the main items of these safety cases is the safety-related application conditions (SRAC) and, thus, the question of how to develop these SRAC is an important one. The SRAC studies reported so far focused only on the simplicity of the derivation procedure and the specific safety activities in the design phase. This method seems to have the advantage of quickly deriving SRAC items. However, there is a risk that some important safety-related items may be missing. As such, this paper proposes an improved method of developing the SRAC based on the idea of performing both the safety design and safety evaluation activities throughout the whole system lifecycle. In this way, it is possible to develop and manage the SRAC more systematically. Especially, considering the SRAC from the initial stage of the design can allow the safety requirements to be reflected to a greater extent. Also, an application case study on railway signaling systems shows that the method presented herein can prevent the omission of important safety-related items, due to the consideration of the SRAC throughout the system lifecycle.

• Journal of the Korea Society of Computer and Information
• /
• v.21 no.12
• /
• pp.165-171
• /
• 2016

This study analyzes the relative importance of the introducing factors for the critical success factors in the implementation stage of the lifecycle of ERP system using Delphi technique and Analytic Hierarchy Process(AHP). In the 1st layer of the hierarchy, technical factor is evaluated as the most important factor among organizational, technical, and supplier factors. In the 2nd layer, choosing a proper ERP package is evaluated as the most important factor within 15 factors followed by process-oriented approach, technical suitability, minimized customization, integration and association of system with trading parter, association with legacy systems, and support and involvement of top management. As a result of this analysis enterprise should choose an ERP package that is suitable to its business environment, and make the best use of(take full advantage of) best practice that ERP package provides to optimize the existing business procedure or process(to approach the existing business procedure or process). This study also shows the range of customization of the features provided by the ERP package should be minimized.