• The KIPS Transactions:PartD
• /
• v.16D no.5
• /
• pp.747-754
• /
• 2009

Software product line engineering is an approach to creating core assets by systematically exploits common that can be highly reusableand different characteristics in related system families that is domain. By adapting this approachin object and component paradigm, software productivity is extended. Recently, Software development paradigm is changed to service oriented paradigm which is using services that are core assets. Therefore, to develop service oriented software more flexible, systematic and to enhance business agility about business changes, we need adaptation of product line to creation of services that are core assets. In this paper, we propose an approach to create and specify domain service through combine of product line and service oriented paradigm. Domain service explicitly specifies commonality and variability by domain service common/optional property variability, operation type variability, message type variability. By using this approach, it can support efficient and flexible service oriented development by producing various services through customization of domain service for the purpose.

• The KIPS Transactions:PartD
• /
• v.13D no.7 s.110
• /
• pp.909-922
• /
• 2006

The core assets include all properties which consist of an application in Product Line Engineering. The requirement, one of the core assets, is a basis of other core assets and commonality and variability of other core assets are classified by the requirement. accordingly, commonality and variability of the domain requirement should be managed objectively and it is necessary to make a process to reuse the domain requirements. However the requirement is analyzed by domain experts or developers without proper process. In this paper, we proposed the 4 activities: (1)the domain scoping, (2)the extraction and generalization of the domain requirement, (3)the domain requirement analyzing and modeling, (4)the change management, and sub activities. For all reasons given previously, it is possible to reduce the development time and cost by reusing the architectures and components related to the domain requirement. In addition, it is possible to increase the quality of the artifacts produced based on the requirements by managing them systematically.

• Journal of KIISE:Software and Applications
• /
• v.33 no.7
• /
• pp.589-604
• /
• 2006

Software product lines (SPL) are recently an emerging software reuse paradigm, which helps organizations develop their products from reusable core assets rather than from scratch. For developing these assets, understanding commonality and variability (C&V) is essential. A feature-oriented approach has been used extensively for C&V analysis in the SPL. However, this contains no proposal to systematically identify features and provide the rationale for the features. Further, the approach does not directly show how the results of C&V analysis will satisfy an organization's high-level business goals and provide the rationale for the C&V. Therefore, this paper presents a domain analysis method for the SPL based on goals, scenarios, and features in order to overcome some of the deficiencies and limitations of the feature-oriented approach. In particular, the paper proposes a domain requirements model (DRM) and a domain requirements modeling method based on the DRM. This method has been applied to the home integration system (HIS) domain to demonstrate its feasibility with a supporting tool, namely IDEAS. Our approach makes it possible to systematically identify the features and provide the rationale for both the features and the C&V.

• Journal of KIISE:Computing Practices and Letters
• /
• v.14 no.7
• /
• pp.733-737
• /
• 2008

Business process modeling is to represent the business activities in a graphical notation that enterprises use to achieve their customer's requirements. Nowadays, lots of requirements are changed quickly and variously. Therefore, business process models should provide the means which can prepare for changes by analyzing (pointing) elements of business process that are likely to alter. In this paper, we propose a business process family model (BPFM) which represents the commonalities and the variabilities of a set of business processes. In addition, we propose the process which develops the tools for BPFM based on Eclipse Plug-In Graphical Modeling Framework (GMF). The variabilities of Business Process are modeled by using expanded model elements of UML2.0 activity diagram.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2004.11a
• /
• pp.263-266
• /
• 2004

유사한 제품 패밀리들에 대한 생산성 향상과 재사용성을 향상시키기 위해 Product Line Engineering에 대한 관심이 높아지고 있다. PLE를 이용한 소프트웨어 개발이 기존 방법들보다 생산성과 재사용성을 향상시키기 위해서는 제품 패밀리에 대한 도메인 분석을 통한 핵심 자산을 효율적으로 구축해 놓아야 한다. 현재 SI업체에서 많이 이용하고 있는 프레임웍처럼 PLE의 핵심 자산들을 만들기 위해서는 제품 패밀리 내의 제품들의 특징을 공통성과 가변성으로 분리하고 이들 특성들 간의 관계성을 추출하는 작업이 선행되어야 한다. 본 논문에서는 도메인 전문가 또는 제품 패밀리 분석가들이 제품 패밀리 특징들을 추출하고 모델링하기 위한 방법을 제안하고자 한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2004.11a
• /
• pp.421-424
• /
• 2004

Product-Line 기반의 소프트웨어 개발은 특정 도메인의 소프트웨어 제품군 내의 공통성과 가변성 분석을 통한 공통 아키텍처의 추출과 재사용으로 개발의 생산성과 효율성을 향상시킨다. 일반적인 Product-Line 기반 방법론에 따르면, 재사용되는 핵심자산은 아키텍처, 컴포넌트, 등의 소프트웨어 내부 비즈니스 로직에 한정되어 있으며, 실제로 소프트웨어 개발에 있어 많은 비용이 지출되는 UI(User Interface), 데이터베이스 등의 설계 및 개발에 대한 내용은 언급되어 있지 않은 실정이다. 본 논문에서는 소프트웨어 개발에 필요한 UI 모듈을 핵심자산의 형태로 Product-Line 에서 사용할 수 있도록 하는 방법을 제안한다. UI 모듈을 설계하여 명세하는 방법과 설계된 UI를 디자인 템플릿과 연결하여 내부 로직과 연계하는 방법에 대해 설명한다. 이 방법을 이용하면 Product-Line을 위한 핵심자산 구성시 UI 모듈을 포함할 수 있어 생산성과 효율성을 향상시킬 수 있을 것으로 생각된다.

• The KIPS Transactions:PartD
• /
• v.15D no.3
• /
• pp.361-374
• /
• 2008

In the latest intelligent computing environments, the self-adaptive software, as new software paradigm, which modifies its own behavior in response to changes in its operating environment is needed. To develop the self-adaptive software, it is necessary to analyze and design the context of software as well as the structure and the behavior of software. We need more efforts for self-adaptive software development than for traditional software development because we need more activities and technologies like context modeling and adaptation to develop the self-adaptive software. In this paper, we present the product line architecture for self-adaptive software and templates of artifacts to improve the efficiency of development through a reuse methodology. The artifacts of the architecture support the systematic reuse activities of core assets by expressing the commonality and variability of product line.

• Proceedings of the Korean Information Science Society Conference
• /
• 2004.10b
• /
• pp.319-321
• /
• 2004

제품 계열 공학(Product Line Engineering, PLE)는 패밀리 멤버들의 공통성과 가변성을 분석하여 만든 핵심 자산을 특화시켜 어플리케이션을 개발함으로써 재사용성과 이용가능성을 증대시키는 접근 방법이다. 핵심 자산은 제품 계열에 속하는 패밀리 멤버들이 어플리케이션을 만드는데 기초가 되는 모든 자산을 포함하며, 아키텍처, 컴포넌트 둥이 포함될 수 있다. 범용 아키텍처는 패밀리 멤버들이 공통적으로 사용할 수 있는 아키텍처로, 제품 계열에 속하는 제품들의 구조를 정의하고 컴포넌트의 인터페이스 명세를 제공하여 컴포넌트만큼 중요한 재사용 단위이다. 본 논문에서는 대표적인 PLE 방법론에서 정의한 제품 계열 아키텍처와 일반 소프트웨어 아키텍처를 비교하여 범용 아키텍처에 포함되는 요소들을 선정하고, 메타 모델을 이용하여 범용 아키텍처 구성요소와 구성요소간 관계를 명확히 정의함으로써, 개념적인 아키텍처를 보다 실용적으로 설계하는데 도움이 되게 하고자 한다.

• Journal of Korea Game Society
• /
• v.9 no.2
• /
• pp.95-104
• /
• 2009

The windows games and the console games that use DirectX occupied 20% or more of world game market and that are developed by C++ Language occupied 75% or more of the market. This study proposed that commonality and variability for code of the 20 projects based on DirectX and C++ is analysed and patternized, that common modules are created, and that modules are modeled. As a result of applying a case study, it is verified that the proposed model reduces effort in game development.

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