Ideally, a feature interaction (FI) approach for scenario models should require minimal additional specification effort and allow for incremental definition of new scenarios. Furthermore, the scenario specification model and the validation model should be clearly separated. The specification model comprises the intrinsic behavioral and structural properties of the application under consideration, while the validation model consists of any additional information required for ensuring compliance with the feature specifications. The usage of pre- and postconditions in scenario models is one lightweight approach for detecting, modeling, and resolving FIs. It requires low effort, allows for incremental development, and if properly structured, allows for separation of the scenario and validation models. Aspect-oriented modeling techniques, however, add further requirements, as aspectual scenarios should remain independent from each other even if FIs are present. We present a specification and validation framework that satisfies the above-mentioned goals and assess its aspect-oriented scenario notation, Aspect-oriented Use Case Maps, against these goals based on a radio software case study.