Frank Houdek1 and Thomas Zink2

1DaimlerChrysler, Ulm, Germany

2Nokia Mobile Phones, Ulm, Germany (formerlyat DaimlerChrysler)

THE SPECIFICATION volume needed to develop a premium car is amazing: The set of vehicle features and functions implemented in software now exceeds 104 pages. The countless requirements allocated to dozens of subsystems are described in intricate detail. They are influenced not only by market demands but also by technological opportunities and cost constraints.

Consequently, it is a non-trivial task to keep track of all the rationales behind individual requirements, or the interactions of all the functions. If new functions come into play or existing functions have to evolve because of changed constraints, it becomes hard not to get lost in detail.

In this context, we found scenarios to be beneficial in a range of activities supporting different stages of product definition and enhancement. They proved to be a good means of negotiating new product features, to provide meaningful rationales for requirements (without being too detailed), to provide a users' perspective on technological driven product features and to keep an overview in the chaos of detail.

To illustrate these benefits, the chapter gives first a brief overview of the characteristics of automotive software development. Then we sketch the benefits of scenarios for different activities in the specification area by typical examples. ...

Get Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.