• Proceedings of the Korean Information Science Society Conference
• /
• 2003.10b
• /
• pp.277-279
• /
• 2003

컴포넌트 기반 개발은 재사용 단위의 컴포넌트를 사용하여 소프트웨어의 중복개발을 지양하고 시스템을 효율적으로 개발한다. 또한 인터페이스를 통해 컴포넌트 배치시 내부의 수정없이 사용자의 요구에 맞게 컴포넌트를 특화하는 장치를 제공한다. 본 논문에서는 컴포넌트 가변성(Variability)을 위한 컴포넌트 Required 인터페이스를 제시한다. 분석단계에서 컴포넌트의 공통성 및 가변성 식별이 이루어졌음을 가정하고, 분석단계의 산출물인 '가변성 식별 테이블'을 수집하여 가변성을 위한 오퍼레이션 식별 및 인터페이스를 정의한다. 또한 컴포넌트 Requited 인터페이스 명세서를 제공한다. 따라서 제시된 기법은 Required 인터페이스를 구성하는 오퍼레이션의 식별부터 명세까지 체계적인 Required 인터페이스의 설계 프로세스를 제시하여 블랙박스 컴포넌트의 가변성 설정을 위한 실용적인 Required 인터페이스의 기반이 된다.

• Journal of KIISE:Software and Applications
• /
• v.34 no.4
• /
• pp.328-341
• /
• 2007

When the decision to initiate a software product line has been taken, the first step is the domain analysis describing the variability in the requirements, the second important step is the definition of a domain architecture that captures the overall structure of a series of closely related products. A domain architecture can be a core asset in product line by describing the commonalities and variabilities of the products contained in the software product line. The variabilities, which are identified at each phase of the core assets development, are diverse in the level of abstraction. Therefore, it is important to clearly define, systematically identify, and explicitly represent variability at the architectural level. However, it is difficult to identify and represent the variability which should be considered at the architecture level, because these may be appeared in architecture elements and in architecture configuration. In this paper, we suggest a method of developing domain architecture as a core asset in product line where commonality and variability are explicitly considered. First of all, we will describe a domain architecture metamodel that can explicitly define commonality and variability concepts by extending the Object Management Group's ($OMG^{TM}$ Reusable Asset Specification eRAS) model. Using the domain architecture metamodel, architecture elements are defined and the variations that can be identified at the architecture level are classified into two types in according th abstract level. Additionally, we describe a domain architecture where commonality and variability are explicitly considered on basis of this metamodel.

• Journal of KIISE:Software and Applications
• /
• v.33 no.6
• /
• pp.550-563
• /
• 2006

Software product line engineering is a method that prepares for the future reuse and supports to seamless reuse in application development process. Commonality and variability play central roles in all product line development processes. Reusable assets will become core assets by explicitly representing C&V. Indeed, the variabilities that art identified at each phase of core assets development have different levels of abstraction. In the past, these variabilities have been handled in an implicit manner and without distinguishing the characteristics of each core assets. In addition, previous approaches have depended on the experience and intuition of a domain expert to recognize commonality and variability. In this paper, we suggest a 2-dimensional analyzing method that analyzes the variabilities of core assets in software product line. In horizontal analysis process, the variation types are analyzed in requirements, architecture, and component that are produced at each phase of development process. In vertical analysis process, variations are analyzed in different abstract levels, in which the region of commonality is identified and the variation points are refined. By this method, the traceability of variations between core assets will be possible and core assets can be reused seamlessly.

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

• Proceedings of the Korean Information Science Society Conference
• /
• 2011.06a
• /
• pp.124-127
• /
• 2011

스마트 폰과 같은 모바일 디바이스의 연산 능력 향상으로 다양한 모바일 어플리케이션의 개발이 증가하고 있다. 특히, 모바일 디바이스에 장착된 다양한 센서를 통해 수집되는 컨텍스트 정보를 기반으로한 모바일 컨텍스트 애플리케이션에 대한 요구가 크게 증가하는 추세이다. 하지만 모바일 컨텍스트는 모바일 디바이스의 다양한 종류와 운영체제, 정보의 종류 등에 따라 다양한 형태가 존재한다. 모바일 컨텍스트의 다양성에 의해 모바일 컨텍스트 애플리케이션 개발에 추가적인 비용이 발생한다. 본 논문에서는 효과적인 모바일 컨텍스트 애플리케이션의 개발을 위한 모바일 컨텍스트의 가변성 모델을 제안한다. 가변성 분석을 통해 모바일 컨텍스트의 다섯 가변점과 각 가변점의 가변치를 정의한다. 또한 제안된 가변성 모델을 기반으로 활용 가능한 사례를 제시하고, 제안된 모델의 평가를 수행한다.

• Journal of Internet Computing and Services
• /
• v.9 no.1
• /
• pp.115-127
• /
• 2008

The component for satisfying several domain requirements must be developed to support variety. But, when the application is developed using the component, it happens other requirements. So, it is difficult to design component to satisfy severaldomain requirements. Also, it is impossible to support the special business logic. As this problem, the component must provide to the white-box component, it is not the black-box component. So, in this paper, we propose the variability design technique and the customization technique using the design technique that can support the various requirements. This technique is not focus on designing the component to analyze various domains. The variability of the component is designed to the initial variability in the component development phase and we use the customization technique for applying the variability to developing application. The variability can be re-designed during developing the application to use the component applying the variability. The variability of the component is evolved and the generation of the component is increased via the iteration Generally, the range of the component variability is classified the function modification within the component and the component internal structure modification as requirements in the component outside. As the range of the variability, we propose the variability design technique of the behavior and the message flow. This paper proposes a message flow design technique for modifying function call.

• KIPS Transactions on Software and Data Engineering
• /
• v.10 no.2
• /
• pp.45-56
• /
• 2021

In platoon driving, several autonomous vehicles communicate to exchange information with each other and drive in a single cluster. The platooning technology has various advantages such as increasing road traffic, reducing energy consumption and pollutant emission by driving in short distance between vehicles. However, the short distance makes it more difficult to cope with an emergency accident, and accordingly, it is difficult to ensure the safety of platoon driving, which must be secured. In particular, the unexpected situation, i.e., variability that may appear during driving can adversely affect the safety of platoon driving. Because such variability is difficult to predict and reproduce, preparing safety guards to prevent risks arising from variability is a challenging work. In this paper, we studied a simulation method to avoid the risk due to the variability that may occur while platoon driving. In order to simulate safe platoon driving, we develop diverse scenarios considering the variability, design and apply safety guards to handle the variability, and extends the detail functions of VENTOS, an open source platooning simulator. Based on the simulation results, we have confirmed that the risks caused form the variability can be removed, and safe platoon driving is possible. We believe that our simulation approach will contribute to research and development to ensure safety in platoon driving.

• Journal of KIISE:Software and Applications
• /
• v.29 no.10
• /
• pp.703-725
• /
• 2002

It is well recognized that component-based development (CBD) is an effective approach to manage the complexity of modem software development. To achieve the benefits of low-cost development and higher productivity, effective techniques to maximize component reusability should be developed. Component is a set of related concepts and objects, and provides a particular coarse-grained business service. Often, these components include various message flows among the objects in the component, called 'business workflow`. Blackbox components that include but hide business workflow provide higher reusability and productivity. A key difficulty of using blackbox components with business workflow is to let the workflow be customized by each enterprise. In this paper, we provide techniques to model the variability of family members and to customize the business workflow of components. Our approach is to provide formal specification on the component variability, and to define techniques to customize them by means of the formalism.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2011.11a
• /
• pp.1372-1375
• /
• 2011

프로덕트 라인 공학에서 프로덕트 라인 아키텍처는 가장 중요한 산출물 중에 하나이다. UML (Unified Modeling Language) 2.x 부터는 아키텍처를 모델링하기 위한 유용한 모델링 요소를 제공하고 있다. 이러한 UML을 이용하여 프로덕트 라인 아키텍처를 모델링하기 위해서는 가변성의 표현이 명시적으로 이루어져야 하지만, UML 자체에는 가변성을 표현하기 위한 방법 및 기법을 명시적으로 기술하고 있지 않다. 본 논문에서는 UML에서 제공하는 확장 메커니즘을 이용하여 가변성을 표현하는 방법을 제안한다. 즉, 모델링요소에 태그값(Tagged Value) 및 스테레오타입을 넣어주어 다양한 관점에서의 가변성을 표기하는 방법을 제안한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2013.11a
• /
• pp.915-917
• /
• 2013

제품 계열 소프트웨어 개발 방법에서 사용자 인터페이스 개발은 제품 계열의 기능 개발과 분리되어 단독으로 개발되고 있다. 기존 연구들에서는 유사한 사용자 인터페이스들이 갖는 가변성을 표기하고 표기된 사용자 인터페이스 가변을 기반으로 재사용 객체를 설계하는데 초점이 맞춰 있지 않다. 사용자 인터페이스 가변은 사용자 인터페이스 개발을 간결하게 하며 자동화 할 수 있는 기반을 제공할 수 있다. 본 논문에서는 사용자 인터페이스의 가변성을 모델링 하는 방법에 대해 살펴본다.