• Title/Summary/Keyword: 애스펙트 명세

Search Result 2, Processing Time 0.016 seconds

A Specification Technique for Aspects Focusing on Join Information Between Aspects and Targets (애스펙트와 목표의 결합정보 중심 애스펙트 명세 기법)

  • Choi, Yun-Seok;Chong, Ki-Won
    • 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.

Specification of Crosscutting Concerns to Support Program Development and Maintenance (프로그램 개발 및 유지보수를 지원하는 횡단관심사 명세 기법)

  • Park, Oak-Cha;Yoo, Cheol-Jung;Jang, Ok-Bae
    • 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.