• The KIPS Transactions:PartD
• /
• v.13D no.4 s.107
• /
• pp.593-602
• /
• 2006

Software development methodology has been developed for satisfying goals of improvement in productivity and reduction in time-to-market through the reuse of software assets. The current methods that implement software product-line, one of software development methodologies, interfere massively with the core assets, which require high cost in assembly level reducing the effectiveness. In this paper, we introduce Aspect-Oriented Programming (AOP) as a method for improving assembly process in software product-line. The method that assembles core assets and variabilities is described by grammar elements such as Join point, pointcut and advice without code-change. We analyze requirements of a mini-system as an example adapting AOP and design using UML. Our study implements the variabilities, which are from design stage, using an Aspect-Oriented Programming Language, AspectJ and prove usability and practicality by implementing the proposed idea using an Aspect-Oriented Programming Language, AspectJ.

• The KIPS Transactions:PartD
• /
• v.15D no.4
• /
• pp.495-504
• /
• 2008

Aspect Oriented Programming(AOP) is a relatively new programming paradigm and has properties that other programming paradigms don't have. This new programming paradigm provides new modularization of software systems by cross-cutting concerns. In this paper, we propose a regression test method for program evolution by AOP. By using JoinPoint, we can catch a pointcut-name which makes it possible to test the incorrect pointcut strength fault and the incorrect aspect precedence fault. Through extending proof rules to aspect, we can recognize failures to establish expected postconditions faults. We can also trace variables using set() and get() pointcut and test failures to preserve state invariant fault. Using control flow graph, we can test incorrect changes in control dependencies faults. In order to show the correctness of our proposed method, channel management system is implemented and tested by using proposed methods.

• The KIPS Transactions:PartD
• /
• v.13D no.2 s.105
• /
• pp.251-258
• /
• 2006

Aspect-Oriented Software Development is new software development method. It has many advantages related to software performance, maintenance and repair. Also it offers modularization method to a existing programming language for secondary function such as security and fault tolerance. But the present problem is that we have to use new aspect-oriented programming language. Further more when we apply Aspect to legacy system, we have to recompile the source code in order to build software system based on AOSD. In this paper, we propose and design Connector that can be composed with Aspect in legacy system dynamically. To elaborate this work, we use the information of operations about Core and Aspect, and the information of pointcut described with XML. We validate that the proposed Connector has features such as no need of new compiler, no recompilation and no modification of legacy system through case study.

• Journal of Digital Contents Society
• /
• v.11 no.1
• /
• pp.25-38
• /
• 2010

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.

• 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.

• 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.