Current use case guidelines typically recommend a goal-driven process for use case creation and, in many cases, this approach indeed works sufficiently well. Yet, in our experience, this goal-driven approach does not seem to offer the best fit for every kind of function, e.g. for highly context-sensitive automotive driver assistance systems. For these functions we suggest selecting a context-driven process for use case creation. In this paper we first show the effectiveness of goaldriven use case creation for a usual car telephone function. Then we demonstrate the limits of this approach for an adaptive vehicle cruise control function (the Distronic system). Finally we present our basic ideas of a context-driven use case creation process and evidence its advantages as compared to the goal-driven approach using the example of the Distronic function.