• Proceedings of the Korean Information Science Society Conference
• /
• 2000.10c
• /
• pp.298-300
• /
• 2000

복잡한 시스템을 구현하는데 컴포넌트의 사용이 유용하다는 것은 이미 누구나 인지하고 있는 사실이다. 엔터프라이즈 자바 빈즈(Enterprise JavaBeans, EJB)는 컴포넌트 트랜잭션 모니터를 위한 표준 서버측 컴포넌트 모델이다. 엔터프라이즈 자바 빈즈 아키텍쳐를 이용해 만들어진 어플리케이션은 확장성이 있고, 트랜잭션을 보장할 수 있으며, 다수 사용자 환경에서도 안전하다. 기존의 객체지향 방법론으로 어플리케이션을 개발하더라도 진정한 소프트웨어 재 사용성을 보장할 수 없었다. 그러나 EJB 아키텍쳐를 사용하면 소프트웨어 재 사용성을 보장하고 보다 용이하게 새로운 어플리케이션을 개발할 수 있다. 본 논문은 정확한 분석과 설계를 위하여, Rational rose의 UML을 이용하여 시스템을 모델링하고, 템플릿 제너레이트인 인라인(inline)과 비주얼 카페를 연동하여 온라인 주문 시스템을 구현하였다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.10a
• /
• pp.511-513
• /
• 2001

레거시 시스템은 수년간 각 기업의 비즈니스 완성에 따라 최적화되어 있다. 국부적인 영역에만 적용되어진 레거시 시스템은 웹과 같은 분산환경에서 더 이상 사용하기 어려워졌다. 따라서 레거시 시스템으로부터 중요한 비즈니스 로직을 식별하여 재사용할 수 있는 메커니즘이 필요하다. 본 논문에서는 레거시 시스템을 컴포넌트 래핑 기술을 이용하여 엔터프라이즈 자바 빈즈(EJB)로 생성하는 지원도구를 설계 및 구현하였다. 본 논문은 비즈니스 로직을 이벤트와 데이터 분석과 관계를 이용여여 레거시 컴포넌트를 식별하는 방법을 제시하고 이러한 방법으로 추출된 컴포넌트를 EJB환경에서 재사용 가능만 프레임웍 기반의 래퍼 구조를 제시하고자 한다.

• Journal of KIISE:Software and Applications
• /
• v.28 no.3
• /
• pp.239-248
• /
• 2001

‘컴포넌트 기반 소프트웨어 개발’에서 컴포넌트 사용자는 컴포넌트 맞춤, 즉 컴포넌트를 특정 도메인 요구사항에 맞추는 작업을 반복적으로 수행함으로써, 소프트웨어를 개발한다. 따라서 컴포넌트 기반 소프트웨어 테스트의 주요 대상은 맞춤으로 변형된 컴포넌트에서 발생하는 오류이다. 본 논문에서는 엔터프라이즈 자바빈즈(Enterprise JavaBeans : EJB)를 기반으로 구체화된 EJB 컴포넌트 맞춤 테스트 기법을 개발한다. 본 기법은 EJB 컴포넌트의 인터페이스 가운데 맞춤 오류가 일어나는 곳에만 오류를 삽입하여, 맞추어진 컴포넌트와 오류가 삽입된 컴포넌트를 차별하는 테스트 케이스를 선정한다. 따라서 본 논문에서는 EJB 컴포넌트 맞춤 테스트 기법을 EJB 컴포넌트 맞춤에 적용한 사례를 보이고 이를 분석하여, 본 기법이 EJB 컴포넌트에 적용 가능한 것임을 보인다.

• Journal of Digital Convergence
• /
• v.12 no.11
• /
• pp.257-264
• /
• 2014

This paper is to construction of the data mining preprocessing tool for efficient database marketing. We compare and evaluate the often used data mining tools based on the access method to local and remote databases, and on the exchange of information resources between different computers. The evaluated preprocessing of data mining tools are Answer Tree, Climentine, Enterprise Miner, Kensington, and Weka. We propose a design principle for an efficient system for data preprocessing for data mining on the distributed networks. This system is based on Java technology including EJB(Enterprise Java Beans) and XML(eXtensible Markup Language).

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

An application in Component-Based Software Development (CBSD) is built by 'composing'two kinds of components; One is a component that is made by current developer himself, and the other is a component that is from other developments. We define the former as a 'White-box component' and the latter as a 'Black-box component.' The error from the composition can be said to be caused by interactions of Black-box components and White-box components. This paper proposes a new testing technique for composition errors, and applies the technique to Enterprise Java Beans component architecture. Our technique selects test cases by injecting a fault only into the specific parts of a White-box component. This specific parts for injecting a fault are selected by analyzing composition patterns, and lead to make our test cases have a good effectiveness. We show the effectiveness of our test cases through an experiment. Moreover, we also mention an automation tool for our technique.

• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.705-714
• /
• 2001

The computing systems of today expanded business trade and distributed business process Internet. More and more systems are developed from components with exactly reusability, independency, and portability. Component based development is focused on advanced concepts rater than passive manipulation or source code in class library. The primary component construction in CBD. However, lead to an additional cost for reconstructing the new component with CBD model. It also difficult to serve component information with rapidly and exactly, which normalization model are not established, frequency user logging in Web caused overload. A lot of difficult issues and aspects of Component Based Development have to be investigated to develop good component-based products. There is no established normalization model which will guarantee a proper treatment of components. This paper elaborates on some of those aspects of web application to adapt user requirement with exactly and rapidly. Distributed components in this paper are used in the most tiny size on network and suggest the network-addressable interface based on business domain. We also discuss the internal and external specifications for grasping component internal and external relations of user requirements to be analyzed. The specifications are stored on Servlets after dividing the information between session and entity as an EJB (Enterprise JavaBeans) that are reusable unit size in business domain. The reusable units are used in business component through query to get business component. As a major contribution, we propose a systems model for registration, auto-arrange, search, test, and download component, which covers component reusability and component customization.

• Journal of KIISE:Software and Applications
• /
• v.32 no.7
• /
• pp.601-611
• /
• 2005

Due to not only proven stability and reliability but a significant investment and years of accumulated -experience and knowledge, legacy systems have supported the core business applications of a number of organizations over many years. While the emergence of Web-based e-business environments requires externalizing core business processes to the Web. This is a competitive advantage in the new economy. Consequently, organizations now need to mine the business value buried in the legacy systems for reuse in new e-business applications. In this paper we suggest a systematic approach to mining components that perform specific business services and that consist of the legacy system's assets to be leveraged on the modem platform. The proposed activities are divided into several tasks. First, use cases that realize the business processes are captured. Secondly, a design model is constructed for each identified use case in order to integrate the use cases with the similar functionalities. Thirdly, we identify component candidates from the design model and then adjust the component candidates by considering common elements among the candidate components. And also business components are divided into three more fine-grained components to deploy them onto J2EE/EJB environments. finally, we define the interfaces of components which provide functionalities of the components as operations.