• Journal of the Korean Society for Industrial and Applied Mathematics
• /
• v.10 no.2
• /
• pp.11-25
• /
• 2006

The current RFID middleware standard is ALE (Application Level Event) of EPCglobal that takes the lead in RFID standardization. ALE suggests the minimal interface and extension points so that it can be operated independently from system infrastructure, and actual implementation is left to vendors. But there is no specific mention with regard to functional extension through extension points, and It is very hard to extend or modify the function on running system. To solve this problem, we suggest AOP (Aspect Oriented Programming)-based ALE middleware framework for developing RFID middleware. In addition, we designed aspect for RFID middleware for implementing and extending functions according to ALE rules and for the convenience of maintenance.

• Journal of the Korea Society of Computer and Information
• /
• v.21 no.3
• /
• pp.39-45
• /
• 2016

In this paper, we propose a log management service model for efficient developments of android applications. The proposed model consists of two major parts which are the log collector and the log manager service. The log collector can capture the log information of a target application without modifications, because the collector is composed by aspect-oriented programming. The collected logs are transformed to chunk of data, and the chunk of data is sent to the log management service. The log management service is an android service component and an independent application in another process. So, the log management service can reduce the workload of logging in the target application. Through a case study, we show that the proposed log management service model can reduce the log processing time compared to other models without modifications of a target application.

• Annual Conference of KIPS
• /
• 2010.11a
• /
• pp.318-321
• /
• 2010

임베디드 소프트웨어를 테스트하고 디버깅하려면 기능 분석, 프로세스 추적, 메모리 디버깅 등 다양한 기술들이 존재한다. 하지만 테스터가 임베디드 시스템 내부의 컴포넌트들의 사이에 결함을 발견하고 그 위치를 찾아야 하는 경우, 디버깅 기술과 도구만으로는 한계가 있다. 만약 테스터가 테스트 도구를 이용할 경우 이런 단점을 보완할 수 있지만 다양한 임베디드 시스템 환경에서는 테스트 환경만을 구축하는 데도 많은 노력과 시간이 소요된다. 따라서 이러한 문제 해결하기 위하여 본 논문에서는 관점 지향 프로그래밍(Aspect-Oriented Programming)을 사용한 후크(Hook) 개념을 적용하여 새로운 테스팅 아키텍처를 제안한다.

• Annual Conference of KIPS
• /
• 2011.04a
• /
• pp.207-210
• /
• 2011

표준 워크플로우 언어로 가장 인지도가 높은 BPEL은 분기를 통한 플로우선택에 있어 상황정보를 기술하기 어려워 유비쿼터스 컴퓨팅 환경에 적용하기 어렵다. 이를 위해 본 논문에서는 모듈간 낮은 결합도를 보장하는 관점지향 프로그래밍 (AOP: Aspect-Oriented Programming) 기법을 사용하여 기존 BPEL 워크플로우 시스템에 상황인지 기능을 추가한 시스템을 제안한다. 제안하는 상황인지 워크플로우 시스템은 AOP 기법을 사용하여 BPEL 워크플로우에 상황에 따른 서비스를 제공하기 위한 Context 정보를 삽입하는 방식으로 개발함으로써, 기존 BPEL 문서를 수정할 필요 없이 상황인지 기능을 적용한 워크플로우의 생성이 가능하다. 본 논문에서는 시나리오 기반의 실험을 통하여 제안한 시스템을 입증한다.

• Annual Conference of KIPS
• /
• 2007.11a
• /
• pp.627-629
• /
• 2007

최근 상황 중심 프로그래밍(Aspect-Oriented Programming)에 관한 연구가 활발해져서 분산 및 병렬 시스템의 설계를 더 효과적으로 할 수 있게 되었다. 이 논문에서는 상황 중심 프로그래밍을 활용하여 분산 시스템의 전통적인 이슈 중의 하나인 결함 내성 시스템을 구축해보고자 한다.

• Journal of KIISE:Computer Systems and Theory
• /
• v.37 no.4
• /
• pp.205-214
• /
• 2010

BPEL is a standard workflow language, which interacts with Web Services and is used in various applications. But it is difficult to use BPEL for specific applications which require additional functions. In this paper, we present a system which can add new functions to BPEL based on an aspect-oriented programming (AOP) technique. In order to add new functions to BPEL, we define a JWX document format that can describe new functions to apply to BPEL. JWX is XML-oriented document that can code the corresponding Java program in order to dynamically add new functions to BPEL documents. It is possible for BPEL workflow to add new functions without modifying the existing programs using the AOP technique, which guarantees low degree of coupling between key and additional requirements. Additionally this systems weaves based on new functions of Java program and JWX document by expanding BPEL engine called B2J based on AOP and execute them. Therefore it is possible to develop a new BPEL engine with additional functions easily and with low cost. The new system can execute additional conditions that the current BPEL engine doesn’t provide. The new system using functions of BPEL supplied by B2J. The new system can be used to add a new rule engine, which isn't currently provided.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.11 no.3
• /
• pp.943-950
• /
• 2010

A secure entrance system is complicated because it should have various functions like monitoring, logging, tracing, authentication, authorization, staff locating, managing staff enter-and-leave, and gate control. In this paper, we built and applied a secure entrance system for a domestic nuclear plant using Aspect Oriented Programming(AOP) and design pattern. Using AOP has an advantage of clearly distinguishing the role for each functional module because building a system separated independently from the system's business logic and security logic is possible. It can manage system alternation flexibility by frequent change of external environment, building a more flexible system based on increased code reuse, efficient functioning is possible which is an original advantage of AOP. Using design pattern enables to design by structuring the complicated problems that arise in general software development. Therefore, the safety of the system can also be guaranteed.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.07b
• /
• pp.400-402
• /
• 2005

동적 Aspect 프로그래밍(Aspect-Oriented Programming : AOP)은 로깅과 같은 비 기능적인 부분을 모듈화할 수 있도록 해주는 새로운 프로그래밍 기법이다. AOP는 절러 클래스에 영향을 미치는 행위들을 재사용 가능하도록 Aspect로 캡슐화 시켜준다. 기존의 Aspect 위버(weaver)에서는 Aspect를 위빙 할 경우, 새로운 서비스나 메소드를 추가하고자 한다면 서브클래스를 별도로 상속을 해주어야하며, 이로 인해 코드의 라인수가 증가되며, 수행 시간도 느려지게 된다. 이러한 문제점을 해결하기 위하여 동적 Aspect 위버 상에 Decorator 패턴을 적용하여 별도의 서브클래스를 상속하지 않고, 필요한 메소드만을 추가하여 위빙시키고, Aspect의 join point에 훅(hook)을 첨가하여 불필요한 메소드의 실행을 제거해준다. 이로 인해 수행속도와 재사용성을 증가시킬 수 있게 된다.

• Journal of Information Technology Services
• /
• v.10 no.2
• /
• pp.223-234
• /
• 2011

Loosely coupled properties of SOA(Service Oriented Architecture) services do not guarantee that service applications always work properly. Service errors may also influence other services of SOA. These characteristics adversely affect software reliability. Therefore, it is a challenge to effectively manage system change and errors for operating services normally. In this study, we propose a SOA based framework using AOP(Aspect Oriented Programming) for reliable service applications. AOP provides a way to manipulate cross-cutting concerns such as logging, security and reliability and these concerns can be added to applications through weaving process. We define a service specification and an aspect specification for this framework. This framework also includes service provider, requester, repository, platform, manager, and aspect weaver to handle changes and exceptions of applications. Independent Exception Handler is stored to exhibited external Aspect Service Repository. When exception happened, Exception Handler is linked dynamically according to aspect rule that is defined in aspect specification and offer function that handle exception alternate suitable service in systematic error situation. By separating cross-cutting concerns independently, we expect that developer can concentrate on core service implementation and reusability, understanding, maintainability increase. Finally, we have implemented a prototype system to demonstrate the feasibility of our framework in case study.

• The KIPS Transactions:PartD
• /
• v.16D no.1
• /
• pp.93-104
• /
• 2009

Modular implementation of a feature is a first step toward feature-oriented product line engineering, which develops and then utilizes core assets to configure products in terms of features. Aspect-oriented programming provides effective mechanisms for improving the modularity of feature implementations. However, as features in general are not independent of each other, changes in the implementation of one feature may cause changes to or side effects in the implementation of other features. Moreover, since the time at which a feature is incorporated into products, called feature binding time, may be various from compile time through load time to run time, a feature may have to be implemented differently depending on when the feature is bound into a product. To make each feature implementation module as independent as possible, this paper proposes aspectual implementation patterns that can effectively separate feature dependencies as well as feature binding time from feature implementation modules. These patterns enable flexible composition of feature implementation modules without affecting other modules according to feature selection. The approaches are demonstrated and evaluated based on a product line of scientific calculator applications.