• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.155-168
• /
• 2006

Software product line is a software product or a set of software system, which has common functions. We can develop a specific software product, which satisfies requirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed software architecture through the software product line. Software development methodology based on the software product line can develop a software more easily and fast by reusing the developed software core asset. Developed countries of software technology select software product line as a core field of software production technology, and support technology development. In case of USA, CMU/SEI(Carnegie Mellon University/Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Department of Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. However, industries in our country understand the necessity of software production technology based on product line concept for the purpose of increasing productivity, it is not sufficient to invest for this technology development. In this paper, we aim to construct the common architecture of software product line for production of the software product line.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 2006.05a
• /
• pp.1329-1333
• /
• 2006

This paper proposes a framework for product development including hardware and software components. The framework provides separation of the hardware dependent software, an integrated product development process, and integration of software components with product configurations and product structures. In order to separates the hardware dependent software, the framework considers product configuration modules and engineering changes of associated hardware and software components. The proposed product development process integrates development of the hardware dependent software into the existing product development process. In order to integrates the hardware dependent software with product configurations and product structures, the framework represents software components by existing product data models in Product Data Management (PDM). The framework is applied to development of a robot system including hardware and software components in order to show its effectiveness.

• Korean Journal of Computational Design and Engineering
• /
• v.13 no.4
• /
• pp.314-322
• /
• 2008

This paper introduces an integration of Product Data Management (PDM) and Software Configuration Management (SCM). PDM and SCM have supported development of mechanical products and software products respectively. The importance of software components in the current products increases rapidly since the software enables the products to satisfy various customer requirements efficiently. Therefore the current product development needs enhanced product data management that can control both the hardware and software data seamlessly. This paper proposes an extended product data model for integrating SCM into PDM. The extension enables PDM document management to support the version control for software development. It also enables engineers to control both the software and hardware parts as integrated data objects during product configuration and engineering change management. The proposed model is implemented by using a commercial Product Lifecycle Management (PLM) system and a development of a network based robot system is tested by the implemented product development environment.

• Journal of Information Technology Services
• /
• v.11 no.4
• /
• pp.171-180
• /
• 2012

Since software and hardware integration has became a strategic tool for companies to innovate their products, an information system that can comprehensively manage software and hardware integrated product development is critical for the current product development. This paper proposed a product data model that can support modules of related software and hardware parts in Product Data Management(PDM) integrated with Software Configuration Management(SCM). The model allows engineers to define software and hardware product structure independently, and support the integration module that can summon related software and hardware parts to build a comprehensive module for collaboration. Through the integration module, engineers can identify and examine the effectiveness of their design alternatives to other related parts form different disciplines. The product data model was implemented as a prototype PDM system and tested with an example robotics product.

• Journal of the Korea Society of Computer and Information
• /
• v.23 no.12
• /
• pp.123-129
• /
• 2018

The purpose of this paper is to draw a conclusion on the impact of intermediate software on enterprise results. In this paper, product innovation and product reliability are especially used as analytical factors. An exploratory analytical study is conducted on the competitiveness of intermediate software, in the hope of gaining a new understanding of the competitiveness of intermediate software. Data are analyzed using such quantitative analytical tools as SPSS and AMOS. Using reliability analysis, validity analysis and structural equation model analysis, the final results are achieved. According to the analysis results, we can draw the following conclusions: the competitiveness of intermediate software has a positive impact on the innovation of software products. The competitiveness of intermediate software doesn't have a positive impact on the reliability of software products. Product innovation has a positive impact on enterprise results. Product reliability also has a positive impact on enterprise results. By analyzing the conclusions, we can make certain suggestions and draw implications on the competitiveness of China's software industry.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.31 no.4
• /
• pp.100-105
• /
• 2008

Cost reduction, time to market, and quality improvement of software product are critical issues to the software companies which try to survive in recent competitive market environments. Software Product Line Engineering (SPLE) is one of the approaches to address these issues. The goal of software product line is to maximize the software reuse and achieve the best productivity with the minimum cost. In software product line, software components are classified into the common and variable modules for composition work. In this paper, we proposed a dynamic composition process based on aspect-oriented programming methodology in which software requirements are classified into the core-concerns and cross-cutting concerns, and then assembled into the final software product. It enables developers to concentrate on the core logics of given problem, not the side-issues of software product such as transactions and logging. We also proposed useful composition patterns based on aspect oriented programming paradigm. Finally, we implemented a prototype of the proposed process using Java and Aspect to show the proposed approach's feasibility. The scenario of the prototype is based on the embedded analysis software of telecommunication devices.

• Journal of the Korea Society of Computer and Information
• /
• v.23 no.12
• /
• pp.65-72
• /
• 2018

In this paper, we have studied how to reuse common data link software by applying software product line engineering. Existing common data link software performed different stages of design, implementation, and testing without sharing the accumulated knowledge of different developers. In this situation, developers agreed that sharing the assets of each project and reusing the previously developed software would save human and time costs. Even with the initial difficulties, the common Data Link is a continually proposed project in the defense industry, so we decided to build a product line. The common data link software can be divided into two domains. Among them, the initial feature model for the GUI software was constructed, and the following procedure was studied. Through this, we propose a plan to build a product line for core assets and reuse them in newly developed projects.

• Proceedings of the Korean Society of Computer Information Conference
• /
• 2018.07a
• /
• pp.258-261
• /
• 2018

The purpose of this paper is to draw a conclusion on the impact of intermediate software on enterprise results. In this paper, product innovation and product reliability are especially used as analytical factors. An exploratory analytical study is conducted on the competitiveness of intermediate software, in the hope of gaining a new understanding of the competitiveness of intermediate software. Data are analyzed using such quantitative analytical tools as SPSS and AMOS. Using reliability analysis, validity analysis and structural equation model analysis, the final results are achieved. According to the analysis results, we can draw the following conclusions: the competitiveness of intermediate software has a positive impact on the innovation of software products. The competitiveness of intermediate software doesn't have a positive impact on the reliability of software products. Product innovation has a positive impact on enterprise results. Product reliability also has a positive impact on enterprise results. By analyzing the conclusions, we can make certain suggestions and draw implications on the competitiveness of China's software industry.

• The Journal of Society for e-Business Studies
• /
• v.22 no.2
• /
• pp.39-60
• /
• 2017

Software product line engineering is widely recognized as an effective way for systematic software reuse, and many studies have been conducted to convert existing software development practices and processes into software product line. In order to convert existing software development into product line, a lot of investments are required such as dedicated development units, appropriate process selection and adaptation, and tool support. In particular, small businesses need business cases and specific practices for applying software product line engineering before its full-scale adoption. In this paper, we present a practical case of applying software product line engineering to the development of web system families and a process of systematically building and reusing software assets. To do this, we analyzed a number of web development projects and presented the experiences and various considerations of small software companies adopting software product line.

• KIPS Transactions on Software and Data Engineering
• /
• v.3 no.1
• /
• pp.1-6
• /
• 2014

Many companies have tried to adopt Software Product Line Engineering for improving the quality and productivity of information systems and software product. There are several models defined in software product line methodology and each model has different abstraction level. Therefor it is important to maintain the traceability and consistency between models. In this paper, consistency checking rules are suggested by traceability matrix of work products.