Throughout software process, requirement evolution control is a relevant factor to achieve software reliable and correct. New paradigms such as Aspect-Oriented Software Development and Model-Driven Development provide mechanisms and strategies for separation of concerns and transformation in order to support the requirements evolution. In this paper, we present a framework that joins these paradigms by means of a transformation pattern. This standardizes the architectonic separation of concern in different abstraction levels, and provides a set of rules to support the requirements traceability. We make a case study to validate the framework.