Complete and precise software requirements description is critical in successful development of software systems. This description specifies both functional requirements that define the different functionalities the system should perform, and non-functional requirements that define how the system should perform these functional requirements. Valuable software should meet both its functional (FRs) and non-functional requirements (NFRs). In this paper, we show the possibility of associating NFRs to behavioral models. We propose a framework where NFRs are defined as a set of non functional attribute goals which derive the composition of behavioral models towards the construction of a behavioral model of the overall system.