Research On Method For Identification Of Crosscutting Concerns Based On Goal Model

To achieve the modularization of software design and development, separation of concerns has become one of the most important principles of software engineering.However, crosscutting concerns are scattered in multiple concerns, it is difficult to separate and module. Aspect-Oriented Programming provides a technique which encapsulates crosscutting concerns as aspects. It solves the problems of separation and modularization of crosscutting concerns in implementation phase. To realise the separation of crosscutting concerns in requirement phase, Aspect-Oriented Requirement Engineering was proposed. AORE aims at separation of crosscutting concerns and identification of aspects in the requirement phase. It can provide the support for the latter phases of software development. At present, reasearchers on the method for identification of crosscutting concerns in the requiremet phase have achieved some results, but have some drawbacks, such as imcomplete and lack of conflict dedection.This paper present a comparison of methods for identification of crosscutting concerns in requirement phase. First, the representation of aspect in requirement phase was analysed, and several common methods were introduced. Second, five criteria were provided, identification range, composability, composability, conflict resolution, tool support and input. Finally, a comparison of these mehod on criteria was given.This paper proposes a method for identification of crosscutting concerns based on goal model and two-state algorithm in requirements phase. It takes both function aspect and non-functional aspect into consideration, solve the prolem of imcomplete. It solves the conflict dedection by expending goal model, adding an execution priporty of decomposed goals. The method starts with extracting goals from requirements document,goals were decompose using AND/OR tree, hierarchical goal model was established based on the relation among goals. Second, goal model was stored into XML file. Finally,the identification of crosscutting concerns was realized according to identification rules.The method is illustrated through a case study(a ticket booking management system).The comparison with Theme/Doc shows the effectiveness of the method in identifying crosscutting concerns in the requirement phase.