• Journal of KIISE:Software and Applications
• /
• v.35 no.7
• /
• pp.424-430
• /
• 2008

Identifying crosscutting concerns during requirements engineering phase is one of the most essential parts in Aspect-Oriented Software Development. Considering crosscutting concerns in the earlier phase of the development improves consistency among requirements so that it can help maintain software systems efficiently and effectively. It also provides a systematic way to manage requirements changes by supporting traceability throughout the software lifecycle. Thus, identifying tangled and scattered concerns, and encapsulating them into separate entities must be addressed from the early phase of the development. To do so, first, functional and non-functional concerns must be clearly separated. Second, a pointcut where a main concern meets crosscutting concerns should be defined and specified precisely. Third, it is required to detect conflicts being occurred during composition of crosscutting concerns from the earlier phase. Therefore, this paper proposes a systematic approach to identifying and specifying crosscutting concerns using goal-scenario based requirements analysis. And we demonstrate the applicability of the approach by applying it into the intelligent service robot system.

• Journal of KIISE:Software and Applications
• /
• v.34 no.9
• /
• pp.773-784
• /
• 2007

Aspect-Oriented Programming (AOP) has focused on improving the modularity of the crosscutting concerns. The existing AOP methodology has been mainly focused on the implementation method of programs and thus developer-oriented concern extraction and development were performed. Recently, many studies for applying AOP to the entire software development processes ranging from requirement analysis to design and implementation are being conducted. But specification methods having consistency from the initial phase of concern extraction to implementation phase are not sufficient. In this paper, we have presented the specification of crosscutting concerns so as to solve these problems. The specification of crosscutting concerns provides guidelines and specification from the requirement analysis phase to the process of converting extracted crosscutting concerns to codes. This method reduces the gap to the process of mapping extracted crosscutting concerns into a single class and thus enhances program development and understandability. In addition, it raises program reusability, maintenance and extensibility by enhancing traceability.

• Journal of KIISE:Software and Applications
• /
• v.35 no.12
• /
• pp.741-752
• /
• 2008

Aspect-Oriented Software Development(AOSD) is the software development methodology that classifies concerns of the system and identifies crosscutting concerns and organizes aspect class, and AOSD has emerged as an important user-oriented software development methodology with high maintainability. However, most of related studies worked on identification and specification and coding of crosscutting concerns. And there have been few studies on slicing technique for tracing method of specified crosscutting concerns. Therefore, this paper proposes slicing technique based on AOSD that identifies and specifies crosscutting concerns through interactive analysis between use cases; also, suggests slicing technique which improves traceability centering on identified crosscutting concerns; applies the aspect-oriented slicing technique to Learning Management System(LMS) for case-study. LMS is a cyber educational system that demands a lot of functional changes and expansion, so it is effective to apply AOSD with high maintainability in developing LMS; and shows the results that compared with related studies by comparing six elements.

• Proceedings of the Korean Information Science Society Conference
• /
• 2006.06c
• /
• pp.226-228
• /
• 2006

관심사 분리는 소프트웨어 공학에서 핵심 문제로 다루어왔다. 기존의 OOD나 CBD등은 관심사를 분리하여 모듈화함으로써 프로그램 개발 및 유지보수를 용이하도록 발전해왔다. 하지만, 에러 처리나 로깅과 같이 여러 모듈에 산재되어 실행되는 횡단 관심사는 기존의 방법으로 해결하기 어려웠다. AOP는 이와 같은 횡단 관심사를 처리하려는 데 목적을 두고 제안된 방법으로 기존의 OOD나 CBD의 단점을 보완하면서 병행적으로 발전해왔다[1]. AOP가 나타난 가장 큰 특징은 기존의 개발 방법론을 기반으로 핵심 관심사를 개발하고 해결하기 어려운 횡단 관심사는 AOP로 개발하려는데 초기 목적을 두고 있다. 하지만, 대부분의 연구가 초기 요구사항 분석 단계에서 관심사를 명시하는데 초점을 두고 있을 뿐 구현 단계에서 효율적인 접근 방법은 아직 부족한 편이다. 본 논문에서는 Java와 AspectJ를 이용하여 구현한 간단한 사례 연구를 적용한 AOP 개발 프레임워크를 제안한다. AOP 개발 프레임워크에서는 관심사 분리, 구현, 평가의 세 단계를 기술한다. 이 중 구현단계에서는 핵심 관심사와 횡단 관심사 구현에 초점을 두고 AOP 기법에 쉽게 접근할 수 있는 방법을 기술하고 있다. 프레임워크는 프로그램 개발을 보다 용이하게 하고 확장 및 유지보수시 많은 시간을 단축시키려는데 있다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2006.10c
• /
• pp.453-457
• /
• 2006

프로그램 구현 방법에 편중되어온 기존의 AOSD 방법론이 최근에는 전체 개발 라이프사이클에서 초기 요구사항의 중요성이 강조되면서 요구사항 모델링, 분석, 설계분야에서 많은 연구가 진행되고 있다. 하지만, 요구사항 분석에서 추출된 관심사를 설계하여 구현 단계로 변환하는 과정에서 아직까지 상세화된 프로세스가 부족하다. 본 논문에서는 횡단 관심사 구현 명세 기법을 제시한다. 이 기법은 추출된 관심사를 구현 코드로 변환하기 위한 4단계의 프로세스로 구성되어 있다. 상세화된 명세 기법과 가이드라인은 AOSD에서 해결하기 어려운 설계에서 구현간의 갭을 줄여줌으로써 이해 및 유지보수성을 높여준다.

• The KIPS Transactions:PartD
• /
• v.15D no.5
• /
• pp.669-680
• /
• 2008

There are various studies about AOP(Aspect-Oriented Programming) which modularizes cross-cutting concerns like logging and security effectively. But, we need to utilize techniques which specify the information of aspects modularizing cross-cutting concerns and detailed join information between aspects and targets. We propose a specification technique for aspects which focuses on clarifying the join information between aspects and targets. The technique includes the activities of specifying aspects, defining priority, specifying join information, and specifying pointcuts. We describe the join matrix which represents relationships of aspects and targets and the pointcut specification which is made by analyzing the commonality of join points. The proposed specification technique supports detailed information of the aspects and the join information between aspects and targets so that we can use detailed information to implement aspects.

• Journal of IKEEE
• /
• v.17 no.4
• /
• pp.525-530
• /
• 2013

The BPEL is standard of workflow. A domain experts not familiar with programming languages and he can write workflow. But he need new function without BPEL. We must develop or modify a BPEL engine for new functions. This method is expensive. In this paper, We propose the XAS4B documents that extend the XML schema. And We describe method that can process new function in BPEL using Aspect-Oriented Programming. AOP can cross-cut concern adding to core concern using weaving without modification. We use an existing B2J (BPEL to JAVA) engine that is transfer a BPEL's document to a JAVA program and B2J execute a JAVA program. This system adding new functions to BPEL's flow using AOP. In this system, A JAVA program is core concern and a program of new function is cross-cut concern. And this system weave a JAVA program made in B2J and a program of new function. This method provide abstract grammar for new functions. And domain experts can easily write new function is a BPEL Document and reuse new function using abstract grammar.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2014.04a
• /
• pp.704-707
• /
• 2014

데이터베이스 복제(Replication)는 데이터의 저장과 백업하는 방법과 관련이 있는 데이터를 호스트 컴퓨터에서 다른 컴퓨터로 복사하는 것이다. 데이터베이스 복제의 종류로는 마스터/슬레이브(Master/Slave), 멀티마스터(Multi-Master)형태가 존재한다. 멀티마스터 데이터베이스는 상당한 비용증가와 복잡도 때문에 어떤 상황에서는 실용적이지 않다. 그러한 이유로 마스터/슬레이브 데이터베이스를 많이 사용한다. 마스터/슬레이브 데이터베이스에서 마스터 데이터베이스는 데이터베이스의 변경을 담당하고 그 결과는 슬레이브로 복제된다. 슬레이브 데이터베이스에서는 읽기 전용 질의만 처리하는 것을 목적으로 한다. 데이터베이스 트랜잭션 처리는 대표적인 횡단 관심사이다. 연구는 마스터/슬레이브 데이터베이스의 트랜잭션을 AOP 를 사용하여 횡단 관심사로 분리하고, 마스터/슬레이브 데이터베이스를 라우팅하는 알고리즘을 제안한다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2007.06a
• /
• pp.49-50
• /
• 2007

• Journal of Software Engineering Society
• /
• v.24 no.1
• /
• pp.27-33
• /
• 2011

The importance of the low-power management has increased due to the recent advances of the embedded systems. However, it is noted that low-power concerns are detrimental to the readability and the maintainability of the codes for the core concerns. In this study, in order to reduce occurring leakage power during run-time, we present a power management while considering the run-time leakage power of devices. the power management codes is separated from the core concern codes by applying aspect-oriented programming. Finally, we analyze the theoretical model of our proposed scheme and present experimental results.