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

가변성은 컴포넌트의 재사용성을 향상시킬 수 있는 요소이다. 어떤 도메인의 여러 패밀리에서 사용될 수 있는 컴포넌트를 개발하기 위해 컴포넌트 가변성이 강조되고 있다. 개발된 컴포넌트가 다양한 유형의 가변성을 지원할수록 도메인 내에서 재사용성이 높아진다. 하지만, 컴포넌트가 너무 많은 가변성을 지원하도록 개발되면, 컴포넌트의 크기가 거대해지며, 개발 기간과 개발 비용이 증가하게 된다. 따라서 해당 도메인에 맞는 적절한 가변성을 지원하는 컴포넌트를 개발해야 한다. .NET의 C＃ 언어는 컴포넌트 개발 언어로 산업계에서 각광 받고 있다. 본 논문에서는 C＃에서 제공하는 기본적인 장치를 활용해 속성 가변성을 지원하는 컴포넌트를 구현 기법을 제시한다. 클래스를 동적으로 생성할 수 있는 빌더(Builder) 클래스를 통해 속성 가변성을 지원한다. 그래서 여러 패밀리 멤버에서 재사용 할 수 있는 고품질의 컴포넌트 개발 방법을 제시한다.

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.414-429
• /
• 2003

Component-based development(CBD) has been generalized in industry to master the complexity and reduce the development cost and time. However, current CBD practice is developing the component which is dependent on single application[l][2]. Therefore component variability is emphasized to reuse the component in many family members in a domain[8]. However, components are developed for the reason of replaceability rather than the reusability which is the main purpose of the component due to the insufficiency of the study of component variability definition and type[3]. In this paper, we formally specify the component variability reflecting the characteristics of the component to increase the component reusability. We define the logic variability which was recognized as the existing component variability and we propose all types of variability existing in the component by suggesting three more variability types. And we propose the component variability scope which makes us estimate and verify the number of cases of the variability when we customize the component. We propose these component variability types and scope through formal specification. By applying these techniques in developing components, we can develop high quality components reusable in many family members.

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

• Journal of Korea Multimedia Society
• /
• v.9 no.8
• /
• pp.1076-1085
• /
• 2006

It is difficult to design a component to satisfy several domain requirements and almost impossible to support a specific business logic completely. To satisfy this requirement, there need white box components rather than black box components. So, in this paper, we propose the variability design technique and the customization technique that can support the various requirements of domains. The initial variability of the component is designed at the CD (component development) phase and the customization technique is used for further application of the variability. In the paper, the behavior variability design and customization techniques are used for altering component behavior. As the components that have been developed using the variability technique can easily be re designed during the development of the applications, the variability of the components can be generalized further.

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

• The KIPS Transactions:PartD
• /
• v.9D no.5
• /
• pp.837-846
• /
• 2002

When you develop component, you can offer reusability and extension by analyzing commonality and variability about attribute and behavior. Therefore Component that analyzing commonality and variability are use for the purpose of reducing discord of function and adaptedness. I wish to research reusability and extension of component by analysis commonality and variability of component that exist by domain in this paper, extractfunctionofcomponentbybehavioranalysis.

• Journal of KIISE:Software and Applications
• /
• v.27 no.9
• /
• pp.920-930
• /
• 2000

컴포넌트 기반의 소프트웨어 개발이 소프트웨어 복잡성, 비용, 그리고 품질을 해결하기 위한 새로운 대안으로 소개되고 있다. COM, Enterprise JavaBeans, CORBA 컴포넌트 모델등과 같은 다양한 컴포넌트 아키텍쳐들이 소개되고 있으며 컴포넌트 기반의 소프트웨어 개발 방법론과 여러 CASE 도구들이 이를 지원하고 있다.[1,2,3,4]. 그러나 현재 컴포넌트를 구현할 수 있는 기술은 제시되어 있지만 컴포넌트를 모델링하는 기법들에 대한 연구는 미약한 상태이다. 본 논문에서는 도메인 분석에서 공통성과 가변성 추출 및 클러스터링 기법을 이용한 컴포넌트를 분석하는 기법을 제시한다. 즉 컴포넌트 추출 기법, 컴포넌트의 핫스팟(또는 가변성)표현 기법, 컴포넌트 요구사항 정의 기법 등을 제시한다. 컴포넌트 개발에 있어서 이러한 모델링 기법을 적용함으로써 컴포넌트를 효율적으로 개발할 수 있을 뿐만 아니라 재사용성이 높은 고품질의 컴포넌트 개발을 지원할 수 있다.

• Journal of KIISE:Software and Applications
• /
• v.30 no.3_4
• /
• pp.185-201
• /
• 2003

The business component for satisfying a variety of domain requirements should be developed to provide a variety. But, although components are developed by analyzing the variety of requirements when they are developed, developing components that satisfy all requirements is not easy since unexpected requirements occur as it is used components. For this reason, components are not provided as black boxes but as white boxes, and there by components are not modified in the interface only but the source codes are directly modified. Accordingly, a Time-To-Market by the use of components is not easy and a reusability of the components also decreases. This study proposes a customization technique that can be satisfied requirements of many different kinds of domains by analyzing variable spots of components. The initial variability of components is designed in the component development phase. and a customization technique is used to apply the variability. The variability can be redesigned during the development of application by using the components to which the variability is applied. Through this process, a variability of components evolves and a generality of the components can be improved. The proposing customization technique in this study can change the component to extend without changing the existing component when it is redesigned.

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.10a
• /
• pp.501-503
• /
• 2000

컴포넌트가 보편화되고 있는 현 시점에서 컴포넌트의 사용은 증가하고 있다. 이러한 컴포넌트들을 효과적으로 재사용하기 위해서는 컴포넌트 설계와 재사용의 올바른 분석과 설계가 요구된다. 재사용의 요구사랑을 만족하기 위해서 컴포넌트의 설계시에 발생할 수 있는 기능과 적합성의 불일치를 줄이고자하는 연구가 활발히 진행되고 있다. 본 논문에서는 공통성과 가변성 분석을 하기 위하여 도메인의 특성이 서비스 중심적인 관점인 경우에 대하여 접근을 했다. 이를 위하여 인터페이스의 추출이 선행되어야 하고, 추출된 인터페이스를 중심으로 두 도메인에 존재하는 공통성과 가변성을 추출하였다.