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

컴포넌트 기반 개발 방법론이 확산됨에 따라 성공적인 컴포넌트 기반 프로젝트의 핵심 요소인 효과적인 컴포넌트 식별 방법에 관한 연구가 활발히 진행되고 있다. 이에 본 논문에서는 시스템이 사용자에게 제공하는 기능을 독립적으로 분류한 유즈케이스를 기반으로 하여 인터페이스를 식별하고, 식별된 인터페이스의 상호작용을 분석하여 컴포넌트를 식별하는 방법에 대해 제안한다. 이를 위하여 유즈케이스를 기반으로 외부 인터페이스를 식별하고, 시나리오를 이용하여 식별된 인터페이스 단위로 객체를 추출한다. 추출된 객체에서 공통 객체를 분석하여 내부 인터페이스와 컴포넌트를 식별하고 최종적으로 이러한 인터페이스의 상호작용과 의존성을 분석하여 컴포넌트를 식별 하고자 한다.

• Journal of Korea Multimedia Society
• /
• v.7 no.7
• /
• pp.1009-1016
• /
• 2004

Component-based development is being generalized as the spread of software reuse technology for rapid development productivity and high quality software.In the CBD, the identification of independent and reusable component is the one of important tasks for component-based system development. Because existing methodologies providing component identification techniques provide techniques based on heuristic techniques of component developer, it is difficult for general developers to identify components using these methods. Therefore, this paper suggests new identification factors and a technique by considering dependency characteristics according to method call types and method call directions and dependency degree. Furthermore, proposed technique is verified through case study; business components based on system components are identified effectively.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2000.10a
• /
• pp.515-518
• /
• 2000

컴포넌트 소프트웨어 기술은 재사용성, 적시성, 유지 보수성 등이 업체의 경쟁력으로 대두되고 있는 정보 기술 업계에서 점차 각광을 받고 있다. 현재 다양한 컴포넌트 기반 개발 방법론 및 지원 도구들이 제공되고 있지만 각 방법론별 고유의 컴포넌트의 식별 방법을 기반으로 하고 있으며 포괄적인 컴포넌트 식별방법을 제공하는 방법론은 없다고 볼 수 있다. 이 논문에서는 현재 산업계에서 쓰이고 있는 여러 방법론과 한국전자통신연구원에서 개발하고 있는 컴포넌트 기반 개발방법론(FOCUS)에서 제안하고 있는 컴포넌트 식별 방법을 비교 분석하여, FOCUS에서는 보다 포괄적인 컴포넌트 식별 방법을 제공하고자 한다.

• Journal of KIISE:Computing Practices and Letters
• /
• v.11 no.1
• /
• pp.1-14
• /
• 2005

It is difficult to identify reusable and independent components in component-based development(CBD) process. Therefore existing methodologies have dealt the problem of component identification based on only developer's intuition and heuristics. As a result, it is difficult to identify the business components by common developers. Therefore, in this paper, we propose a new baseline and technique to identify the business components based on domain model such as use case diagrams, class diagrams, and sequence diagrams. proposed method identifies components through two phases; system component identification and business component identification. Especially, we consider structural characteristics as well as dependency characteristics according to methods call types and directions in identifying components. We also present a case study and comparative analysis and assessment to prove the practical use of our technique.

• The KIPS Transactions:PartD
• /
• v.9D no.1
• /
• pp.91-102
• /
• 2002

We need a component-based system to reflect software changes in user's requirements, to implement a system at a rapid speed as well as to efficiently manage the system in a maintenance phase and to easily change software. Moreover, the component-based system has a merit in development cost. However, existing component development methodology for implement of component-based system is inefficient in object identification for component identification. Moreover, the existing component development methodology also fails to provide any method to identify system component. It merely provides procedures and methods to identify business component focused on a whole system domain. In addition, it has another problem that it considerably relies on developer's experiences and intuitions for component identification. Therefore, according to this paper, RUP (Rational Unified Process) is applied from a requirement analysis phase to an object identification phase in order to improve the inefficiency of object identification. In addition, this paper procedures and methods for system component identification, and identifies business components based on the identified system component, rather than on the whole system domain. This paper also provides and applies cohesion metric and coupling metric so as to overcome the problem that component identification depends on developer's intuitions and experiences. Accordingly, the component identification method proposed in this paper, may identify components more effectively based on facility of object identification, functional reusability of components, traceability, and independence of components.

• Journal of KIISE:Software and Applications
• /
• v.28 no.8
• /
• pp.537-549
• /
• 2001

소프트웨어의 생산성과 유지보수 비용을 줄여줄 수 있는 기법으로 다양한 컴포넌트 기반의 개발 방법론이 제안되고 있다. 그러나 컴포넌트 기반의 시스템에서 재사용성과 독립성이 높은 컴포넌트의 식별은 가장 중요한 성공 요소 중의 하나임에도 불구하고, 대부분의 컴포넌트 기반 방법론들에서는 직관적이고 분석자의 경험에 의존적인 컴포넌트 식별 방법만을 제공하고 있을 따름이다. 본 논문에서는 분석 단계의 산출물인 시스템의 기능 모델 Use Case 모델과 자료 모델인 클래스 모델에 기반 하여 체계적인 컴포넌트 식별 기법과 지침들을 제안한다. 먼저 클래스에 대한 Use Case의 자료 접근값을 정의하고, 정의된 접근값을 기반으로 Use Case별로 접근되는 클래스의 가중치와 클래스별 동일 접근값을 가지는 Use Case들의 가중치를 계산하다. 두 가중치를 곱하여 최종적인 Use Case&클래스 가중치를 계산하여 후보 컴포넌트 식별의 기준으로 삼는다.

• The KIPS Transactions:PartD
• /
• v.11D no.3
• /
• pp.625-634
• /
• 2004

When constructing a component based system, It is understood that identifying reusable and independent business components is of utmost importance. However, according to conventional component based developing methodologies, most of developers depend on their experience and/or intuition for identification of business components. Furthermore, there are no criteria to evaluate whether the identified business components are more independently defined or not. Therefore, we propose a component identification metrics to apply to component properties In order to complement the difficulties of identifying business components through developers' experience and/or intuition. The metrics defined are the criteria for identifying the business Components and/or for evaluating the Identified components. We propose both a cohesion metric, and a coupling metric, to which component properties are applied, wherein those properties can be understood by high cohesion in, and low coupling between, components. Moreover, we propose an independence metric that can evaluate the degree of independence for a particular component by ratio of the cohesion and coupling of components. The metrics that we propose are applied to case study which demonstrates the identification of more independent business components and the validity of our metrics.

• Journal of the Korea Computer Industry Society
• /
• v.3 no.3
• /
• pp.383-390
• /
• 2002

System developments by components are accomplished by creating new software based on independent components having respective function. Generally, component-based software developments are expected to obtain profits caused by reuse of software, such as improvement of quality, rapid development, and efficiency of maintenance. In a component-based system, the most important goal and also key to success is to identify and construct high quality components that may increase reusability. Therefore, it is necessary for component developers to understand strong and weak points of existing component development methodologies in the aspect of identification of component, and to select the most appropriate methodology for the system to be constructed. It is also necessary for component developers to develop a new methodology enabling effective identification of independent components through modification and/or complementation of existing methodologies. The modification and complementation needs comparison and analysis of various existing methodologies. Accordingly, the this paper is to provide explanation for some widely used methodologies representing the existing component-based software development methodologies such as RUP(Rational Unified Process) of Rational company［1,9］, CBD96 of Computer Associates company［2,3］, UNIFACE of Compuware company［5］, and UML components methodology derived from extending of the component developing method of CBD96 by Cheesman and Daniels［4］. The this paper is also to point out respective problems of the representative existing methodologies. Furthermore, component identification methodologies are compared and analyzedon the whole through this paper.

• Journal of KIISE:Software and Applications
• /
• v.32 no.12
• /
• pp.1205-1216
• /
• 2005

Component-based Development (CBD) is gaining popularity as an effective reuse technology. Especially commercial-off-the-shelf (COTS) components are mainly for inter-organizational reuse, rather than intra-organizational reuse. One of the essential tasks in CBD is to reuse the right components that provide the functionality and interface required by component consumers. If candidate components provide a limited applicability and customizability, a component consumer cannot reuse the components in application development. To resolve this partial matching problem, we need smart connectors that fill the gap between candidate components and the specification of components required. Previous researches about smart connector describe only connector types to resolve mismatch problems. However, previous researches do not address the identification and design method to resolve the problems. In this paper, we suggest taxonomy of various mismatch problems to identify partial match problems between requirements of the application and components. We identify smart connector types and suggest a systematic process for designing smart connectors using the taxonomy. Therefore, components that have the problems can be used to develop applications.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2003.11c
• /
• pp.1551-1554
• /
• 2003

최근 SOA(Service Oriented Architecture)와 웹 서비스에 대한 관심이 높아져가고 있다. 웹 서비스는 재사용 측면에서 현재 사용되고 있는 컴포넌트와 많은 공통점이 있다. 웹 서비스의 개발과 수정 및 화장을 위해서 신뢰성 있는 컴포넌트를 이용한 경우 개발 시간의 단축 등의 많은 이점을 가질 수 있다. 이러한 컴포넌트를 이용하여 웹 서비스를 개발한 경우 웹 서비스 도메인에 대한 이해뿐만 아니라 요구사항의 추출 및 식별은 매우 중요한 부분이다. 본 논문에서는 사용자 요구사항으로부터 컴포넌트를 식별하고 이들 컴포넌트를 서비스 지원 컴포넌트인 Facade 컴포넌트와 Backside 컴포넌트로 식별할 수 있는 방법을 제시하고자 한다. 이를 위해 서비스를 오퍼레이션과 데이터 요소로 정의하고, 정의된 요소를 사용한 모델을 제시한다. 이러한 컴포넌트의 식별은 현재 활성화되어 있는 컴포넌트를 사용할 수 있도록 함으로써 웹 서비스 개발의 생산성을 보장하며, 웹 서비스를 컴포넌트로 구성함으로서 컴포넌트의 기본적인 특징인 재사용과 대체성을 통해 웹 서비스의 신뢰성과 수정의 용이성 등을 얻을 수 있다.