Researxch On Aspect-oriented Requirements Modeling Based On Separation

Separation of functional requirements and non-functional requirements in requirements engineering is the key principle during software development. In traditional software development methodology, they are twisted together because they can not be separated effectively during the process of requirements. The software developers only pay attention to functional requirements to be implemented, and non-functional requirements are often neglected as it can not be expressed clearly. So the result is that the software can not be able to meet the needs of the users and has to be reworked. AOP (Aspect-Oriented Paradigm) has the ability to resolve the separation of concerns between functional requirements and non-functional requirements effectively. And the method can avoid the spread of non-functional requirements to functional requirements and be able to express clearly through modularizing non-functional requirements. In the thesis, the non-functional requirements modeling framework for the NFR (non-functional requirements) and method of Use Case driven modeling are analyzed and studied. The method of non-functional requirements modeling based on UML Profile is proposed in the thesis. And the method of requirements modeling separately based on Aspect-Oriented is proposed, too. Functional requirements and non-functional requirements can be modeled separately through the methods above. And it implements the different concerns through multi-view. Then they can be interwoven automatically. Finally, an online bank case is given to illustrate the feasibility of the methodology.