One Aspect-Oriented Non-Functional Requirement Framework (AONFRF) Modeling Method

One of the most important principles in Software Engineering is separation of concerns. At first, the research towards applying that principle throughout the software development process has provided structured and object-oriented methods, and which promote great progress of software development technology. However, when using those methods it is difficult to achieve separation of concerns such as security, reliability, performance, persistence, logging, etc., the so-called crosscutting concerns. Hence, Aspect-Oriented Software Development has emerged to address those issues. This paradigm specifies the system in a higher abstract lever, where program units partition basically base on special behaviors of the system but not functions, and which paradigm achieves modularization of crosscutting concerns.Requirement Engineering (RE) is very important and basic in the whole Software Life Cycle. With the increase of software's scale and complexity, RE becomes more important because it directly conduce success or failure of the system. Traditional requirement analysis activity mainly driven by system's Functional Requirements (FR), and people gradually recognize that Non-Functional Requirements (NFR) is also important to the development of software system, such as safety, reliability and performance, et al. Therefore, we should not only deal with functional requirements well, but also non-functional requirements.In order to overcome the shortcomings in software engineering in dealing with crosscutting concerns, and modularizes NFRs effectively at the stage of requirementanalysis, such as safety, reliability and performance, et al. and which hence lays a solid foundation for later development stage of system analysis and design, I put forward Aspect-Oriented Non-Functional Requirements Framework (AONFRF) modeling method in the paper. At first, I analyses the NFRs' decomposition procedure in NFR framework and does some studies on Aspect-Oriented Requirement Engineering. Second, on the basis of analysis of traditional NFR Framework and analysis of existing Aspect-Oriented Requirement Engineering, I adapt the NFR framework to Aspect-Oriented Requirement Engineering. In the AONFRF method, we find out all NFRs in the system base on system's practical requirements condition at first, and second use the concept "softgoal" in NFR framework to decompose NFRs and refine it iteratively as far as get the final NFRs' "operationalizations", and then select the identified "operationalizations" and identify different priority to handle NFRs' conflicts. We utilize the particular mechanism of Aspect-Oriented Paradigm map the "operationalizations" to the later stage of software development as well as composing them with functional components at last, with three composition rule operators "overlap", "override", and "wrap".AONFRF method not only keeps the advantage of NFRs' good decomposition mechanism of NFR framework, but also combines the advantage of effective modularization of crosscutting non-functional requirements of Aspect-Oriented Software Development. To sum up, AONFRF method makes it possible to implement non-functional requirements in a loosely coupled fashion and combines these implementations to form the final system, which adapts to the development of larger scale and more complex software system, and improves the quality and accelerates the development of the software in some certain extent.