Software requirements are divided into functional requirements and non-functional requirements. Non-functional errors affect the quality of the entire system more than functional errors do. Several issues such as analysis, specification and evaluation of non-functional requirements are not clear. This paper proposes a framework for definition and verification of non-functional requirements using AOP. By using UML extension and applying AOP we can solve the code mixing problem of the classified non-functional requirements which are interspersed with Aspects. The result of applying proposed scheme shows improvement of modularity, reduction of complexity, ease of traceability, clear validation of non-functional requirements.