DOI QR코드

DOI QR Code

효율적인 서비스 시스템 개발을 위한 룰 기반의 관점 지향 기법

Rule-based Aspect Oriented Approach for Efficient Service System Development

  • 이우진 (세종대학교 정보통신공학과) ;
  • 최일우 (강남대학교 교양학부)
  • Lee, Woo-Jin (Dept. of Information and Communication Engineering, Sejong University) ;
  • Choi, Il-Woo (Division of General Studies, Kangnam University)
  • 투고 : 2014.07.24
  • 심사 : 2015.01.08
  • 발행 : 2015.01.31

초록

서비스 지향 아키텍처(Service Oriented Architecture)는 엔터프라이즈 애플리케이션 개발 시 유연성을 보장하여, 비즈니스 변화에 최대한 민첩하게 대응하도록 지원한다. 그럼에도 불구하고 비즈니스와 제약조건을 하나의 서비스로 코딩하는 일반적 접근법은 비즈니스 룰의 변경을 위하여 전체 결합로직을 변경하는 등 많은 자원을 소모하게 된다. 본 논문에서는 이러한 문제점을 개선하기 위하여 서비스 시스템 개발에 관점 지향 기법(Aspect Oriented Approach)을 확장하여 적용한다. 관점 지향 기법의 기존 핵심관심(Core Concern), 횡단관심(Cross Cutting Concern)이외에 비즈니스 프로세스와 서비스에 포함된 비즈니스 룰을 룰관심(Rule Concern)이라는 새로운 관심사로 분리한다. 룰관심은 수준에 따라 프로세스 룰관심(PRA: Process Rule Aspect)과 서비스 룰관심(SRA: Service Rule Aspect)으로 구분된다. 시스템은 이러한 관심사의 분리를 통하여 핵심관심, 횡단관심 및 룰관심으로 각각 모듈화 되고 독립적으로 유지보수 되어 서비스 시스템의 적용성, 재사용성 및 유지보수성을 높일 수 있다.

The service oriented architecture assures flexibility of enterprise application development, so it supports agile reaction to business change. On the other hand, considerable effort is needed to develop a service by combining business and constraint consumes because the entire combination logic should be changed according to the change in business rule. To improve the current method, this paper applied an aspect oriented approach to service system development. In this paper, the rule concern is proposed in addition to the core concern and cross cutting concern of aspect oriented approach. The rule concern is extracted from business rules included in the business processes and services. The rule concern is classified into the process rule aspect and service rule aspect according to the level of the rule. In the proposed approach, system is modularized into the core concern, cross cutting concern and rule concern through separation of concern, and they are maintained independently. Therefore, the adaptability, reusability, and maintainability of a service system will be enhanced.

키워드

참고문헌

  1. Roy W. Schulte Yefim V. Natis, "Service Oriented Architecture," Gartner Group. SSA Research Note SPA-401-068. 1996.
  2. F. Curbera et. al. Business Process Execution Language for Web Services, version 1.1, May 2003
  3. W3C Web Services WG, "Web Services Architecture," http://www.w3.org/TR/2004/NOTE -ws-arch-20040211/.W3C, Working Group Note 11, Feb 2004.
  4. A Charfi and M. Mezini. "Hybrid Web Service Composition: Business Processes Meet Business Rules," In proceedings of the 2nd International Conference on Service Oriented Computing, November 2004
  5. M.A. Cibran and B. Verheecke, "Dynamic Business Rules for Web Service Composition," Proc. of the 2nd Dynamic Aspects Workshop DAW05, March 2005.
  6. M.A. Cibran, M. D'Hondt, and V. Jonckers, "Aspect-Oriented Programming for Connecting Business Rules," Proceedings BIS, 2003.
  7. Chankyu Park et al. "Knowledge-Based AOP Framework for Business Rule Aspects in Business Process," ETRI Journal, Volume 29, Number 4, August 2007 DOI: http://dx.doi.org/10.4218/etrij.07.0106.0145
  8. A. Charfi and M. Mezini, "Aspect Oriented Web Service Composition with AO4BPEL," Proc. of the European Conference on Web Services ECOWS 2004, LNCS 3250.
  9. Jacobson, Ivar, Aspect-oriented software development with use cases, Addison-Wesley, 2005.
  10. Gregor Kiczales, John Lamping, Anurag Mendhekar, Chris Maeda, Cristina Videira Lopes, Jean-Marc Loingtier, and John Irwin, "Aspect-Oriented Programming," ECOOP, pp220-242, 1997.
  11. Adam Przybylek, "Where the truth lies: AOP and its impact on software modularity," FASE'11/ETAPS'11, March 2011.
  12. Shaukat Ali, Tao Yue, Lionel C. Briand, "Does aspect-oriented modeling help improve the readability of UML state machines", Software and Systems Modeling (SoSyM) , Volume 13 Issue 3, July 2014.
  13. G. H. Alferez, V. Pelechano, R. Mazo, C. Salinesi, D. Diaz, "Dynamic adaptation of service compositions with variability models", Journal of Systems and Software , Volume 91, May 2014. DOI: http://dx.doi.org/10.1016/j.jss.2013.06.034
  14. Eric Bodden, Eric Tanter, Milton Inostroza, "Join point interfaces for safe and flexible decoupling of aspects", Transactions on Software Engineering and Methodology (TOSEM), Volume 23 Issue 1, February 2014
  15. B2J,"http://www.eclipse.org/stp/b2j"