Modularization of crosscutting concerns in requirements engineering

In spite of the generated benefits, Object-Oriented (OO) paradigm seems reaching its limits, regarding complexity reduction of current systems. In this context, the Aspect Oriented (AO) comes up as an alternative to reduce software development complexity while keeping OO advantages. Needs for investigating methodologies of AO Software Development have emerged a long with AO. As an example, Early Aspect (EA) aims to identify aspects on the early stages of software development, such as domain analysis requirements specification and architectural design. Being one of the newest software engineering paradigms, AO emphasizes that new studies and experiments should be carefully carried out, in order to establish improved methods, techniques and tools applicable to this new way of development. In this paper, we discuss a sequence of systematic activities toward an early consideration of specifying and separating crosscutting Functional Requirements (FRs) and Non-Functional Requirements (NFRs) by the adoption of use-cases to model systems. This approach would make it possible to identify and resolve conflicts between requirements earlier in the development cycle and can promote traceability of broadly scoped properties throughout system development, maintenance and evolution.