The role of the requirements engineer is to establish a complete consistent and unambiguous requirements specification which defines the requirements at a conceptual level. Many traditional modelling approaches from Structured Analysis ,  to UML-based methods  supporting him in this task neglect the use of concrete examples about current or future system usage. In this paper, we present so called Abstraction Guides which assist the requirements engineer in establishing and applying an interrelating structure between conceptual models and persistent recorded usages of existing systems called Real World Scenes (RWS). This structure is used to improve traceability, understandability and negotiation of conceptual models. We show how Abstraction Guides define support for eliciting requirements from RWS and validating re-quirements against RWS, explanation of conceptual models, and comparing scenes and models.