The Early Identification of Functional and Non-Functional Crosscutting Concerns

Over the last few years, several research efforts have been devoted for handling crosscutting concerns at the early phases of software development especially at requirements level. These efforts are meaningless unless all the crosscutting concerns are properly identified. Many approaches only consider nonfunctional concerns as crosscutting concerns. However, crosscutting concerns may also be functional. In this paper, we are proposing an integrated approach that supports complete separation of concerns i.e. handles both functional and nonfunctional concerns as crosscutting. Our work will surely contribute some positive in this direction.