Journal of Digital Contents Society (디지털콘텐츠학회 논문지)

Digital Contents Society (한국디지털콘텐츠학회)
권호 표지

A Method of the Widening Expression and Conversion of the Spring Framework AOP into UML/XML

Spring 프레임워크 AOP의 UML/XML 확장 표현 및 변환 기법

  • Received : 2009.12.16
  • Accepted : 2010.03.30
  • Published : 2010.03.31
Download PDF
⟨ Previous Next ⟩

Abstract

There is no guideline or standard for the specification of the open-source-framework-based Spring AOP, and it causes confusion in development and maintenance. Moreover, the inconsistency between the existing MVC model, the AOP model that is used for Struts framework and the UML diagram makes the aspect reuse more difficult. In this study, a widened existing method was proposed so that Aspect, Pointcut and Advice could be expressed by either UML or XML to ensure that the Spring AOP can accept the combined use of the existing MVC model and the AOP model, which is used for Struts framework. Relationship was defined so that the mutual conversion could be possible with the proposed expression method, and the realization of simple development and maintenance was verified via the examples of mutual conversion. In addition, a packaging method to efficiently reuse aspect was proposed, and the possibility of reuse was verified.

오픈 소스 프레임워크 기반의 Spring AOP에는 명세화를 위한 지침이나 표준이 없어 개발과 유지보수에 혼란을 야기 시키고 있으며, 특히 기존의 MVC 모델, Struts 프레임워크에서 사용하는 AOP모델 연구와 UML 다이어그램과의 불일치 문제는 Aspect의 재사용을 더욱 어렵게 하고 있다. 본 연구는 기존의 MVC 모델, Struts 프레임워크에서 사용하는 AOP 모델의 혼용을 Spring AOP에서 수용 처리하기 위하여, Aspect, Pointcut과 Advice를 UML과 XML로 어느 것으로 표현하여도 가능할 수 있도록 기존의 표현법을 확장하여 제시하고, 제시된 표현 기법이 상호변환 가능할 수 있도록 관계성을 정의한 후, 상호변환의 사례를 보여 개발과 유지보수를 용이하게 함을 입증 하였다. 또 Aspect의 재사용을 보다 효율적으로 활용하기 위한 패키지화 방법을 제안하고 그 재사용 가능성을 검증하였다.

Keywords

References

  1. CRAIG WALLS, 'Spring in Action Second Edition', Manning, 2008.
  2. 박옥자, 유철중, 장옥배, "프로그램 개발 및 유지보수를 지원하는 횡단관심사 명세 기법", 정보과학회논문지 : 소프트웨어 및 응용 제 34 권 제 9 호, 2007.
  3. Timo Aaltomen, Joni Helin, Mika Katara, Pertti Kello maki., "Coordinating Aspects and Objects", Electron ic Notes in Theoretical Computer Science 68, No.3, 2003.
  4. Georgia, S., Sergio, S., Paulo, B., and Jaelson, C., "Se paration of Crosscutting Concerns from Requiremen ts to Design: Adapting and Use Case Driven Approa ch", Aspect-Oriented Requirements Engineering and Architecture Design Workshop, pp. 93-102, 2004.
  5. Mik Kersten, Gail C. Murphy, "Atalas: A Case Study in Building a Web-Based Learning Environment usi ng Aspect-Oriented Programming", Technical Report Number TR-99-04, 1999.
  6. Jan Machacek, Jessica Ditt, Aleksa Vukotic, and Ani rvan Chakraborty, 'Pro Spring 2.5', Apress, 2008.
  7. Naoyasu Ubayash, Tetsuo Tamai, Shinji Sano, Yusa ku Maeno, Satoshi Murakami, "Model Evolution wit h Aspect-Oriented Mechanisms", Proceedings of the 2005 Eighth International Workshop on Principles of Software Evolution (IWPSE'05),IEEE, 2005.
  8. Spring AOP Schema, http://www.springframework.org/schema/aop/spring-aop-2.0.xsd.
  9. 김태웅, 김태공, "AOSD기반에서 Aspect의 동적결합을 위한 Connector", 한국정보처리학회, 2006.
  10. MDA Guide Version 1.0.1, http://www.omg.org/cgi-bin/doc?omg/03-06-01.pdf, June, 2003.
  11. Iris Groher, Thomas Baumgarth, "Aspect-Orientati on from Design to Code", in Proceedings of the Workshop on Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design; AOSD, March, 2004.
  12. IvarPan-Wei'Aspect-Oriented Software Development with Use Cases', Addison Wesley, 2004.
  13. Grady Booch, James Rumbaugh, and Ivar Jacobson, 'The Unified Modeling Language User Guide', Addi son-wesley, 1999.
  14. 박재성, 'Spring 프레임워크 워크북, 한빛미디어', 2006
  15. AspectJ Website, http://www.eclipse.org/aspectj/
  16. C. W. Krueger, "Software Reuse", ACM Computing Surveys, Vol.24, No.2, pp.131-184, Jun 1992. https://doi.org/10.1145/130844.130856
  17. Barry T. Peterson, Steven J. Clancy, Kay Champion and Jerry W. McLarty, "Improving Readability of Consent Forms: What the Computers May Not Tell You", IRB: Ethics and Human Research, Vol. 14, No. 6, pp. 6-8, 1992. https://doi.org/10.2307/3563853
  18. Ramnivas Laddad, 'AspectJ In Action: PRACTICAL ASPECT-ORIENTED PROGRAMMING', Manning, 2003.