• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.43 no.4
• /
• pp.23-32
• /
• 2020

Many small and medium-sized manufacturing companies process various product types to respond different customer orders in a single production line. To improve their productivity, they often apply batch processing while considering various product types, constraints on batch sizes and setups, and due date of each order. This study introduces a batch scheduling heuristic for a production line with multiple product types and different due dates of each order. As the process times vary due to the different batch sizes and product types, a recursive equation is developed based on a flow line model to obtain the upper bound on the completion times with less computational complexity than full computation. The batch scheduling algorithm combines and schedules the orders with same product types into a batch to improve productivity, but within the constraints to match the due dates of the orders. The algorithm incorporates simple and intuitive principles for the purpose of being applied to small and medium companies. To test the algorithm, two case studies are introduced; a high pressure coolant (HPC) manufacturing line and a press process at a plate-type heat exchanger manufacturer. From the case studies, the developed algorithm provides significant improvements in setup frequency and thus convenience of workers and productivity, without violating due dates of each order.

• Proceedings of the Korean Society of Precision Engineering Conference
• /
• 1995.10a
• /
• pp.707-710
• /
• 1995

Structure of product, which is not considered by easy of assembly, has many hidden costs. For reduction of hidden costs, concepts of line balancing and assembly-oriented design are used. We find that part of structure can be improved by concept of line balancing. To reduce assembly time and enhance easy of assembly, design principles are developed by concept of assembly-oriented design. And design principles for improvement are applied according to condition of the grasped parts of product structure. Thersfore, we could design assembly-oriented design for better structure and low cost.

• KIPS Transactions on Software and Data Engineering
• /
• v.11 no.7
• /
• pp.273-282
• /
• 2022

Testing approaches for configurable software product lines differs significantly from a single software testing, as it requires consideration of common parts used by all member products of a product line and variable parts shared by some or a single product. Test coverage is a measure of the adequacy of testing performed. Test coverage measurements are important to evaluate the adequacy of testing at the software product line level, as there can be hundreds of member products produced from configurable software product lines. This paper proposes a method for measuring code coverage at the product line level in configurable software product lines. The proposed method tests the member products of a product line after hierarchizing member products based on the inclusion relationship of the selected features, and quantifies SPL(Software Product Line) test coverage by synthesizing the test coverage of each product. As a result of applying the proposed method to 11 configurable software product line cases, we confirmed that the proposed method could quantitatively visualize how thoroughly the SPL testing was performed to help verify the adequacy of the SPL testing. In addition, we could check whether the newly performed testing for a member product covers the newly added code parts of a feature.

• Journal of KIISE:Software and Applications
• /
• v.41 no.7
• /
• pp.469-480
• /
• 2014

Software Product Line (SPL) is a software development paradigm that guarantees high productivity, reduced cost, and shorter time-to-market by systematically planning and reusing commonality and variability. In order to maximize the benefits of SPL engineering, testing should be integrated into the SPL engineering lifecycle processes that consist of domain engineering and application engineering and should be performed with as little test efforts as possible. This paper proposes a systematic software product line test cases derivation method using combinatorial test design. By applying combinatorial test design to product line test cases derivation and exploiting commonality between products at the same time, the number of generated test cases is dramatically reduced with the result that they can be effectively reused by the products of the given product line. Case studies conducted in this paper show the efficacy of our method compared with other methods that use only commonality or combinatorial design or neither of them in terms of the number of derived test cases.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.15 no.7
• /
• pp.2455-2475
• /
• 2021

Patient Navigation Program (PNP) is considered as an important implementation of health care systems that can assist in patient's treatment. Due to the feasibility of PNP implementation, a systematic reuse is needed for a wide adoption of PNP computerized system. SPL is one of the promising systematic reuse approaches for creating a reusable architecture to enabled reuse in several similar applications of PNP systems which has its own variations with other applications. However, stakeholder decision making which result from the imprecise, uncertain, and subjective nature of architecture selection based on quality attributes (QA) further hinders the development of the product line architecture. Therefore, this study aims to propose a quality-driven approach using Multi-Criteria Decision Analysis (MCDA) techniques for Software Product Line Architecture (SPLA) to have an objective selection based on the QA of stakeholders in the domain of PNP. There are two steps proposed to this approach. First, a clear representation of quality is proposed by extending feature model (FM) with QA feature to determine the QA in the early phase of architecture selection. Second, MCDA techniques were applied for architecture selection based on objective preference for certain QA in the domain of PNP. The result of the proposed approach is the implementation of the PNP system with SPLA that had been selected using MCDA techniques. Evaluation for the approach is done by checking the approach's applicability in a case study and stakeholder validation. Evaluation on ease of use and usefulness of the approach with selected stakeholders have shown positive responses. The evaluation results proved that the proposed approach assisted in the implementation of PNP systems.

• Proceedings of the KIPE Conference
• /
• 1998.10a
• /
• pp.865-870
• /
• 1998

We propose a multifunctional power line compensator (PLC) which can individually compensate multiple impediments at the same time. The PLC has the flexibility to share power to each compensation according to commands, this improving the working rate. We constructed a 100kVA PLC model including a controller with digital signal processor (DSP) to realize a multifunctional compensation were obtained.

• Journal of KIISE:Software and Applications
• /
• v.32 no.9
• /
• pp.835-846
• /
• 2005

A Product Line (PL) is a set of products (applications) that share common assets in a domain. Product Line Engineering (PLE) is a set of principles, techniques, mechanisms, and processes that enables the instantiation of produce lines. Core assets, the common assets, are created and instantiated to make products in PLE. Model Driven Architecture (MDA) is a new software development paradigm that emphasizes its feasibility with automatically developing product. Therefore, we can get advantages of both of the two paradigms, PLE and MDA, if core assets are represented as PIM in MDA with predefined automatic mechanism. PLE framework in the PIM level has to be interpreted by MDA tools. However, we do not have a standard UML profile for representing core assets. The research about representing PLE framework is not enough to make automatically core assets and products. We represent core asset in PIM level in terms of structural view and semantic view. We also suggest a method for representing architecture, component, workflow, algorithm, and decision model. The method of representing framework with PLE and MDA is used to improve productivity, applicability, maintainability and qualify of product.

• Journal of Korean Institute of Industrial Engineers
• /
• v.39 no.1
• /
• pp.1-9
• /
• 2013

The current manufacturers have generated tremendous amount of digitized product data to efficiently share and exchange it with other stakeholders or various software systems for product development. The digitized product data is a valuable asset for manufacturers, and has a potential to support high level strategic decision makings needed at many stages in product development. However, the lack of studies on extraction of key performance indicators(KPIs) from product data management(PDM) databases has prohibited manufacturers to use the product data to support the decision makings. Therefore this paper examines a possibility of an architecture that supports KPIs for evaluation of product development performances, by applying multidimensional product data model and on-line analytic processing(OLAP) to operational databases of product data management. To validate the architecture, the paper provides a prototype product data management system and OLAP applications that implement the multidimensional product data model and analytic processing.

• KIPS Transactions on Software and Data Engineering
• /
• v.12 no.1
• /
• pp.1-18
• /
• 2023

Similar software is often developed with the Clone-And-Own (CAO) approach that copies and modifies existing artifacts. The CAO approach is considered as a bad practice because it makes maintenance difficult as the number of cloned products increases. Software product line engineering is a methodology that can solve the issue of the CAO approach by developing a product family through systematic reuse. Migrating product families that have been developed with the CAO approach to the product line engineering begins with finding, integrating, and building them as reusable assets. However, cloning occurs at various levels from directories to code lines, and their structures can be changed. This makes it difficult to build product line code base simply by finding clones. Successful migration thus requires unifying the source code's file path, class name, and method signature. This paper proposes a clustering method that identifies a set of similar codes scattered across product variants and some of their method full paths are different, so path unification is necessary. In order to show the effectiveness of the proposed method, we conducted an experiment using the Apo Games product line, which has evolved with the CAO approach. As a result, the average precision of clustering performed without preprocessing was 0.91 and the number of identified common clusters was 0, whereas our method showed 0.98 and 15 respectively.

• KIPS Transactions on Software and Data Engineering
• /
• v.2 no.11
• /
• pp.739-746
• /
• 2013

Variability of the software product line that differentiates member products within a product line must be described with precise meaning and visualized so as easy to select. Moreover, it should be easy to manage. Variability description approaches can largely be divided into two approaches, integrated variability description approach and orthogonal variability description approach. Orthogonal Variability Description Language (OVDL) was developed for clear and precise description of variability without ambiguity. This paper validates the variability description capability of OVDL by translating the variability models of Inter-Working Function (IWF) product line described by using Orthogonal Variability Model (OVM) notations into variability descriptions in OVDL.