• Journal of KIISE:Computing Practices and Letters
• /
• v.10 no.2
• /
• pp.125-133
• /
• 2004

In order to test reflecting the features of a development methodology and domain, it is required to tailor process standards and perform testing according to the tailored process. However, since commercial testing tools support only a part of the tailored process, it is essential to either acquire or develop testing tools appropriate for a development environment. This paper proposes a method to develop a test process execution tool which has common features of standards, and variousness in methodologies and domains. ‘Test Process Execution Tool: Test PET’ which is a test process execution tool developed adapting the concept of product line. Our Test PET generates the test process suitable for the development methodology and domain and then executes the produced test process.

• Proceedings of the Korea Inteligent Information System Society Conference
• /
• 2000.04a
• /
• pp.217-224
• /
• 2000

Configuration은 도메인 지식을 이용해서 주어진 모든 요구를 충족시키는 컴포넌트를 갖는 시스템을 구성하기 위한 기술이다. 최근 전자 상거래는 역경매, 공동구매, 사용자 프로파일에 의한 제품의 추천 등 다양한 방식으로 구매자 중심의 사거래 행위를 하고 있다. 하지만 아직도 전문 지식이 필요한 제품의 구입시에 구매자는 많은 어려움을 겪고 있다. 이러한 구매자의 행위를 보조하기 위한 수단으로써 전문가 시스템에서 수년간 연구되어 온 Configuration 기술을 확장 도입하였다. 본 논문에서는 도메인에 대한 규칙(Rules)에 기반해서 Classification Problem Solving 방법과 Constructive Problem Solving 방법을 적용하였다. 구매자와의 능동적인 질의 수행을 하여 제품에 대한 요구를 정확히 한 뒤, 얻어진 사실(Facts)을 Classification Problem solving에 이용이 되어 제품 모델이 결정된다. 이 제품 모델은 구매자를 위해 특성화 되어 있기 않기 때문에, Constructive Problem Solving을 이용한다. 이런 내용을 기반으로 컴퓨터 조립을 위한 Configurator를 디자인하고 구현했다.

• Proceedings of the Korean Information Science Society Conference
• /
• 1999.10a
• /
• pp.608-610
• /
• 1999

표준에 정의된 내용을 가지고, 각 프로젝트와 도메인에서 사용할 수 있는 수준의 프로세스를 구축하는 일은 쉽지 않다. 표준에 근거하여, 어떤 부분을 어떻게 tailoring하여야 하는지에 대한 지침이 없기 때문이다. 따라서 표준은 표준대로 존재할 뿐, 실제 프로세스 정의에는 제대로 사용되지 못하고 있다. 본 논문에서는 표준에 대한 tailoring이 갖는 문제를 해결하기 위해 컴포넌트가 갖는 메카니즘, 즉 customization과 composition을 이용한다. 표준에서 정의하는 프로세스를 추출하고, 그를 좀 더 다양한 모습으로 변형시키기 위해 콤포넌트들로 정의한다. 나아가 이들을 실제 특정 도메인에 맞게 tailoring하기 위한 customization과 composition 방안에 대해 제안한다. 본 논문에서 제안한 프로세스 콤퍼넌트를 이용하여 표준의 테스트 프로세스를 도메인의 특성에 적합한 테스트 프로세스로 tailoring 할 수 있다. 따라서 사용자는 프로세스 콤퍼넌트의 인터페이스를 제외한 나머지 부분에 대해서는 고려할 필요없이, 주어진 인터페이스와 플러그인들을 이용하여 customization과 composition만을 수행함으로써, 체계적으로 tailoring된 테스트 프로세스를 구축할 수 있다.

• Journal of KIISE:Software and Applications
• /
• v.31 no.6
• /
• pp.728-740
• /
• 2004

The increasing complexity and shorter life cycle of software have made it necessary to reuse software. Object-oriented development had not provided extensive reuse and computing infrastructures are evolving from mainframe to distributed environments. However, components provide more advanced means of structuring, describing and developing system, because they are more coarse-grained and have more domain-specific aspects than objects. And they are also suited for distributed environment due to their reusability and granularity. In this paper, we present a process including the static metrics and guidelines that can be applied to transform object-oriented systems into component-based systems. Our process consists of two parts: First, basic components are created based upon composition and inheritance relationships between classes. Second, intermediate system is refined into component-based system with the static metrics and guidelines we propose.

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

Component-Based Software Engineering (CBSE) is widely accepted as new paradigms for building applications with reusable assets. Mismatch problems occur while integrating the assets and make a burden in CBSE. Therefore, a larger-grained reuse unit than a component such as a framework is required, and it consists of relevant components, connectors and domain-specific architecture. The benefits of frameworks over components are commonly known, however, the key elements and internal structure of framework has not been clearly defined. We believe most of the framework models proposed in recent works remain at conceptual level. In this paper, we propose a practical-level framework reference model, and define key elements of frameworks. The research goal is to precisely identify concrete elements of a framework, inter-connection of components within a framework, extended notion of connectors, and tailored meaning of architecture In a framework. Hence, the proposed framework can be practically implemented in common object-oriented languages and with middleware such as lava, J2EE, CORBA Component Model (CCM) and NET.

• Journal of the Korea Society for Simulation
• /
• v.19 no.4
• /
• pp.179-188
• /
• 2010

The concern of Software Product Line(SPL) engineering is spreading widely because the program or product developers are able to satisfy the customer's demands quickly and give a way to handle maintenance efficiently. SPL is a reuse paradigm that reuse common parts and adopts variable parts optionally to form a differentiated product by analyzing domains. Purposes of this paper are to design an architecture which has a dynamic reconfiguration function and to develop basic components which are the basic unit of reconfiguration to raise the reuse level of the guided weapon system using the SPL. Initially we design an architecture and define basic components for developing a dynamic reconfigurable components based on SPL. Then we develop the composer for physical components and behavior components referenced by behavior models of OneSAF.

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

프로덕트 라인은 다양하고 빠르게 변화하는 시장의 요구사항과 특정 도메인 영역에 속하는 애플리케이션 간의 재사용 가능한 아키텍처 및 컴포넌트의 구성으로부터 연관된 시스템 구축시 생사성과 품질의 향상을 제공함으로써 현재 많은 관심의 초점이 되고 있다. 또한, 이들 프로덕트 라인에서는 프로덕트들 사이의 공통성과 변화성에 초점을 두고 이들 분류 방법으로 휘처 모델링이라는 개념을 주로 사용하여 분석하고 있다. 또한 재사용 가능한 아키텍처는 많은 변화 계획들과 메카니즘을 포함하고 있다. 하지만, 아키텍처를 설계하기 위한 아키텍처에서의 변화성 관리에 대한 명확한 방법이 미흡하다. 따라서 본 논문에서는 재사용 가능한 아키텍처를 설계하기 위해 변화성의 명확한 표현과 아키덱처에서의 적절한 위치를 식별하기 위해, 다양한 변화성 타입을 정의하고, 휘처 모델을 기반으로한 아키텍처의 변화성과 아키덱처의 컴포넌트 관련성에서의 변화성 표현 방법을 기술하고 사례 연구로 웹기반교육 시스템 개발에 적용하고자 한다.

• 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:Computing Practices and Letters
• /
• v.12 no.2
• /
• pp.129-140
• /
• 2006

The existing CBD development methods deal with the analysis phase in a superficial manner. Applying such a superficial analysis to business applications with a number of subsystems makes analysis models be inconsistent with levels and styles, only depending on experiences of the analysts. This inconsistent analysis might cause more serious problems during the subsequent development phases, resulting in the failure of the projects. In this paper, we propose a rule-based analysis pattern that provides an analysis template for business applications. This pattern analyzes the concepts of business applications by using external events and internal rules that process the events. Employing this pattern, a huge business application can be developed by a couple of co-analysts who work together in a consistent and systematic manner. This paper also describes an efficient way to develop business components with the suggested analysis pattern using banking deposit case study through UML Components development process.

• Journal of KIISE:Computing Practices and Letters
• /
• v.7 no.4
• /
• pp.288-298
• /
• 2001

Utilizing standards for software process to a specific project requires a tailoring process to meet the development domain. However, the existing tailoring schemes are not systematical and possible to use without analyzing the methodology and development domain. Also, it is not quite easy to apply them to similar projects. This paper includes: 1) systematical tailoring steps and 2) an automatic algOlithm for generating test process based on "a scheme of tailoring process using the component-based development paradigm"; 3) "an automation tool for tailoring, AutoTP" which is derived from XML techniques. Users can generate a tailored test process through our AutoTP automatically without analyzing standards. methodology and domain.