A comparison of methods for identification of early aspects

Aspects are tangled and scattered behaviours across a system. The identification of early aspects helps to separate these behaviours from the requirements and improve modularity in the design and implementation stages. In recent years, many methods for identification of crosscutting concerns have been proposed at the requirements level. This paper analyzes how these well-known Aspect-Oriented Requirements Engineering approaches address crosscutting concern and makes a comparison between these techniques.