The Goal-Oriented requirement engineering approach offers important advantages for a deeper study of software requirements. Some of them are supported for reasoning about design alternatives and traceability between requirements and software architecture. However, in complex systems, requirements specifications suffer from crosscutting, which affects elaboration, readability and maintainability of the specification, even when using a Goal-Oriented approach. Separation of concerns, included in Aspect-Oriented Requirement Engineering provides an elegant and effective solution to cope with this problem. In this work we present a model for requirement specification which integrates Goal-Oriented and Aspect-Oriented approaches. This model is included in ATRIUM, a methodology for concurrent definition of requirements and software architecture. Using a UML profile we give graphical notation to our model allowing its support in most CASE tools based on UML.