Role engineering for role-based access control (RBAC) is a process to define roles, permissions, constraints, and role hierarchies. The scenario-driven role engineering process provides a systematic way to elicit the RBAC components. However, the traceability between those components has not been well analyzed. As a result, it is both time-consuming and error-prone to modify the RBAC components. Therefore, a guideline to propagate changes is essential to the scenario-driven role engineering process. The importance of traceability in role engineering has been recognized but very little work has been done to date. In this paper, we propose a way to address the traceability issue based on aspect-oriented requirements engineering.