• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.7
• /
• pp.337-352
• /
• 2017

Clone-and-own reuse is an approach to creating new software variants by copying and modifying existing software products. A family of legacy software products developed by clone-and-own reuse often requires high maintenance cost and tends to be error-prone due to patch-ups without refactoring and structural degradation. To overcome these problems, many organizations that have used clone-and-own reuse now want to migrate their legacy products to software product line (SPL) for more systematic reuse and management of software asset. However, with most of existing methods, variation points are embedded directly into design and code rather than modeled and managed separately; variation points are not created ("engineered") systematically based on a variability model. This approach causes the following problems: it is difficult to understand the relationships between variation points, thus it is hard to maintain such code and the asset tends to become error-prone as it evolves. Also, when SPL evolves, design/code assets tend to be modified directly in an ad-hoc manner rather than engineered systematically with appropriate refactoring. To address these problems, we propose a feature-oriented method for extracting a SPL asset from a family of legacy applications. With the approach, we identify and model variation points and their relationships in a feature model separate from implementation, and then extract and manage a SPL asset from legacy applications based on the feature model. We have applied the method to a family of legacy Notepad++ products and demonstrated the feasibility of the method.

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

• Journal of Digital Convergence
• /
• v.11 no.12
• /
• pp.439-445
• /
• 2013

There has been a growing amount of research on combining Agile methods and software reuse. Most of it introduces Agile into software product line rather than software reuse into Scrum method. Meanwhile, some assets such as backlogs and incremental artifacts in Scrum development are reusable. In this paper, we identify a backlog binder that aggregates reusable Scrum assets and proposes a backlog binder reuse technique. In addition, we can apply the proposed technique and show prototyping of backlog binder reuse in job matching applications.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2008.11a
• /
• pp.550-553
• /
• 2008

최근 많은 기업들이 조직 내의 소프트웨어 프로세스 개선을 위한 CMMI 레벨 획득을 위해 노력을 기울이고 있다. 하지만 기존의 CMMI 지원 솔루션들은 특정 프로세스 영역별로 분리되어 제한적으로 활용됨으로써 원활한 평가 지원에 한계가 있다. 따라서 소프트웨어 단계별 프로세스 전반에 걸쳐 툴, 자산 그리고 산출물들의 연계적 적용, 관리를 지원하는 통합 저장소 활용이 절대적으로 요구된다. 본 논문에서는 이질적인 CMMI 관련 툴, 방법론 그리고 다양한 문서 등을 효과적으로 관리 지원을 위한 통합 저장소인 PARMS(Process Assets Repository Management System) 개발 기술에 대해 서술한다. 즉, 통합 저장소 아키텍처와 메타데이터를 설계하고, 통합 모델을 제시한다. 이들 모델을 기반으로 하여 기 개발된 각 도구간의 효과적 네트워킹을 위한 미들웨어 아키텍처 구현은 CBD 개발 기법을 적용한다. 그리고 구현된 프로토타이핑 시스템 실행 예를 제시하고 저장소 평가 모델을 적용하여 평가한다. 이를 통해 소프트웨어 프로세스 개선을 위한 기존의 지원 도구로부터 산출되는 이질적인 산출물들을 통합하여 보다 쉽고 간편한 제어 및 관리를 가능케 하며, 통합된 소프트웨어 프로세스 개선 자산을 통해 CMMI의 인증 지원에 유용한 도구로 활용가능하다.

• Journal of Convergence for Information Technology
• /
• v.7 no.5
• /
• pp.111-116
• /
• 2017

In this paper, we propose a method to measure the complexity of assets when a software component is constructed as a basic asset, a standardized design model is acquired, and a reusable extended asset is designed based on the standardized design model. However, each asset of our proposed asset management system consists of composite assets that combine assets of two domains. So this method can not make accurate measurements. Therefore, the complexity of the overall asset can be measured by reflecting the property value of the basic asset stored under the architecture. In conclusion, it is possible to measure the composite-complexity of a composed asset that is inversely proportional to cohesion and proportional to the cumulative sum of the associated values of each asset in the asset-related design.

• 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 Information Science Society Conference
• /
• 2005.11b
• /
• pp.427-429
• /
• 2005

최근 컴포넌트 기반의 소프트웨어 프로덕트 라인에 대한 연구와 소프트웨어 프로덕트 라인에 자동 생성 프로그래밍 기법을 적용하기 위한 연구가 활발히 진행 중이다. 본 논문에서는 재사용 가능한 컴포넌트 자산을 구축하고, 재구성 자동화를 통해 컴포넌트 코드를 생성하는 시스템을 제안한다. 본 도구는 컴포넌트 기반 프로덕트 라인 개발 방법론과 자동 생성 프로그래밍 기법, XML/XSLT 기술을 이용하여 구축되었다. Component Asset 개발자 레벨에서 사용하는 컴포넌트 자산 구축기와 재사용자 레벨에서 사용하는 컴포넌트 코드 생성기로 구성되어 있으며, 컴포넌트 기반의 소프트웨어 프로덕트 라인 개발에 효과적으로 활용될 수 있다.

• 정보화사회
• /
• s.173
• /
• pp.48-50
• /
• 2005

• 소프트웨어세계
• /
• s.4
• /
• pp.132-135
• /
• 1999

• 정보화사회
• /
• s.172
• /
• pp.34-36
• /
• 2005