Software traceability is a recognized problem in software development that can be alleviated with requirements management tools.  Traceability information can be used in a number of different software engineering activities such as software change impact analysis and testing.  One main challenge to automation of software testing is mapping modeling to code concepts.  The level of granularity and the semantics supported by available requirements management tools does not, however, fully support such mapping, nor more sophisticated requirement change impact analysis.  Scenarios have been used as an alternative (and sometimes complementary) way to express requirements and system behavior throughout the software phases.  Their use has different representation and semantics across software phases, which can be related.  This paper argues for exploring scenarios as one means for tracing requirements to code, and using this information to leverage automation of activities that benefit from traceability such as change impact analysis and software testing.