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

• Journal of Information Technology Services
• /
• v.4 no.2
• /
• pp.47-59
• /
• 2005

S/W product line is a S/W product or a set of S/W system, which has common functions. We can develop a specific S/W product, which satisfiesrequirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed S/W architecture through the S/W product line. S/W development methodology based on the S/W product line can develop a S/W more easily and fast by reusing the developed S/W core asset. An advanced country of S/W technology selects S/W product line as a core field of S/W 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 Ministry of National Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. In this paper, we aim to construct reference architecture of S/W product line for production of the S/W product line.

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

• Proceedings of the Korean Nuclear Society Conference
• /
• 1996.05b
• /
• pp.637-642
• /
• 1996

This paper presents the analysis results for the core degradation processes and the fission product release of the PHEBUS FPT0 experiment using MELCOR1.8.3. The objective of this study is to assess models associated with the core damage and fission product behavior in MELCOR. The calculation results were much improved through sensitivity studies. Thermal/hydraulic behavior in the core and the circuit was well predicted under the intact core geometry. In non-eutectic model case. the UO$_2$ dissolution model in the MELCOR always showed such a tendency that the resulting dissolved UO$_2$ mass was small at the highly oxidized condition due to the model logic. Total H$_2$ generation mass was underpredicted because the stiffner was not modeled and the liner in the shroud was not allowed to be oxidized in MELCOR. Some difficulties were found in modeling the activation product were solved by manipulating the RN input associated with the initial fission product inventory. These problem were occurred because there are no control rod model in MELCOR. Generally the fission product release ratio showed a similar trend compared with the measured data except the activation product. which have no model to simulate in MELCOR.

• Journal of applied mathematics & informatics
• /
• v.25 no.1_2
• /
• pp.169-181
• /
• 2007

Applying the properties of Hadamard core for totally nonnegative matrices, we give new lower bounds of the determinant for Hadamard product about matrices in Hadamard core and totally nonnegative matrices, the results improve Oppenheim inequality for tridiagonal oscillating matrices obtained by T. L. Markham.

• Nuclear Engineering and Technology
• /
• v.36 no.1
• /
• pp.36-46
• /
• 2004

The ISAAC fission product release calculation is based on detailed FPRAT models developed by Jaycor. For volatile fission product release calculations, either the Cubicciotti steam oxidation correlation or the NUREG-0772 correlation is used. In this study, evaluation is carried out for these volatile fission product release models. As a result, in the case of early release, the IDCOR model with an in-vessel Te release option shows the most conservative results and for the late release case, the NUREG-0772 model shows the most conservative results. Considering both early and late release, the IDCOR model with an in-vessel Te bound option is evaluated to show mitigated conservative results. In addition, a sensitivity study on detailed core nodalization is performed. In the study, 380 horizontal fuel channels in the Wolsong plant are nodalized into 12 (6 channels per loop, $3{\times}3$ Core Pass) representative channels and detailed by 16/20/24 channels. For reference accidents, LOAH and large LOCA are selected as representing high and low pressure sequences, respectively. According to the results, the original 12 channel approach with $3{\times}3$ core passes is evaluated to be sufficient as an optimal scheme.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.04a
• /
• pp.673-675
• /
• 2001

본 논문에서는 Product line 개념을 활용하여 체계적으로 각 어플리케이션에 적합한 소프트웨어 테스트 프로세스를 생성할 수 있도록 하는 1)“소프트웨어 테스트 프로세스의 재사용 방안”을 제안하고, 2) 이를 자동화한 “소프트웨어 테스트 프로세스 생성 도구”프로토타입을 제시한다. “소프트웨어 테스트 프로세스의 재사용 방안”은 product line 개념에 따라 표준, 방법론과 도메인을 위한 개발 프로세스들의 공통점과 차이점을 분석하여 core asset들을 CBD개념의 컴포넌트들로 개발하고, 이 core asset들을 가지고 컴포넌트의 맞춤 패턴을 이용하여 손쉽게 각 어플리케이션에 적합한 테스트 프로세스를 생성할 수 있도록 한다. “소프트웨어 테스트 프로세스 생성도구”는 “소프트웨어 테스트 프로세스 재사용 방안”의 core asset 개발 단계에서 개발된 core asset들을 저장소에 재사용을 목적으로 저장하며, 프로덕트 개발 단계를 자동화하여 각 어플리케이션에 적합한 테스트 프로세스를 생성한다.

• Journal of KIISE:Software and Applications
• /
• v.33 no.10
• /
• pp.896-914
• /
• 2006

Product line engineering (PLE) is one of the most recent and emerging reuse approaches in software engineering. Core asset, which is a reusable unit of PLE, is shared by several members in a product line (PL). So, developing a well-defined core asset is a prerequisite to increase productivity and time-to-market. Existing PLE methodologies emphasize the importance of core asset but mainly focus on analyzing core asset. And, several processes for designing core asset do not fully cover all elements of core asset which is from product line architecture (PLA) to decision model and need to augment systematic process, detailed instructions, and templates of artifacts. These problems result in difficulty with designing core asset and applying PLE. In this paper, we present an overall process and templates of artifacts to design core assets. And, we apply proposed process to a case study in order to show its applicability. With the proposed process, detailed instructions, and templates of artifacts, we believe that we can more systematically and more easily design high-quality core assets and we fully cover product line architecture, component, and decision model when designing a core asset.

• Journal of KIISE:Software and Applications
• /
• v.31 no.8
• /
• pp.1010-1026
• /
• 2004

The goal of product line engineering is to support the systematic development of a set of similar software systems by understanding and controlling their common and distinguishing characteristics. The product line engineering is a process that develops reusable core assets and develops a set of software-intensive systems from a common set of core assets in a prescribed way. Currently, many software development technologies are accomplished in context of product line. However, much of the product line engineering research have focused on the reuse of work products relating to the software's architecture, detail design, and code. The product lines fulfill the promise of tailor-made systems built specifically for the needs of particular customers or customer groups. In particular, commonality and variability play central roles in the all product line development processes. These must be treated already during the requirement analysis phase. Requirements in product line engineering are basis of software development just like as traditional system development engineering, and basis of deciding other core assets' property - commonalities and variabilities. However, it is difficult to elicit, analyze and manage correct requirements. Therefore, it is necessary to develop systematic methods which can develop and manage requirement as core asset, which can be stable in anticipative change and can be well adapted to unpredictable change. In this paper, we suggest a method of managing requirements as core asset in product line. Through this method, the reuse of domain requirements can be enhanced. As a result, the cost and time of software development can be reduced and the productivity can be increased.

• Design & Manufacturing
• /
• v.10 no.3
• /
• pp.46-50
• /
• 2016

Laminate products for motor core are developed with a structure in which the importance of quality level and clamping force is influenced by the recent performance and safety of the product. It has been confirmed that the accuracy of the mold is emphasized, and that the accuracy of the tightening force produced by the stacked product for the motor core is greatly influenced by the change in the bottom dead center displacement of the aged high speed press. The reason why setting the mold, and test the effect of bottom dead center of high speed press is to improve product pull force in embossing process at mold. We have applied the system to minimize the effect on the damping displacement under the dynamical degree of the equipment by applying the emboss complement device which can test the influence and complement in the process.