Clear definitions for complex requirement profiles
Stuttgart, Nov 30, 2006
Vehicle electrical and electronic systems are not only becoming more comprehensive; they’re also growing increasingly complex, especially in terms of their functions. This development is being driven by automakers’ ability to precisely define which requirements a certain component must meet in order to ensure that it can subsequently be integrated as desired into the overall system. For a component or system to even be suitable for cross-platform applications, a very sophisticated approach is needed — a new culture of vehicle development that demands more than simply specifying technical processes.

Anyone who thinks a blinker is only a simple light, or says that a tachometer can hardly be considered a complex instrument, can expect a vociferous rebuttal from Frank Houdek. The DaimlerChrysler researcher needs only a few minutes to convince even the most uninformed lay person that such notions are all wrong. “I myself am time and again amazed by how complex the definitions of requirements have to be, even for components I had thought were very simple,” he reassures his novice visitor.
Houdek works in the Software Process Design department led by Bärbel Hörger in Ulm. The sign on his office door says “Requirement Engineering Processes,” because there’s no succinct German translation for this area of research. The focuses of the work performed by Hörger’s department include a process central to the overall task of vehicle development — specification. To the experts, the term means precisely describing all the requirements that must be fulfilled by simple components like LEDs, by more complex systems such as the vehicle dynamics system ESP, or even by the entire vehicle with all of its various functions.
And in this field, “precise” means “unambiguous.” In practice, “unambiguous” in turn means that “Anton,” a development engineer responsible for a control unit, is able to understand a requirement definition in exactly the same way as does his colleague “Boris,” whose tire pressure sensor sends a signal to Anton’s component. And the two of them must understand the specification document in exactly the same way as “Claude,” an engineer working for a supplier who is responsible for developing the tire pressure display for the instrument cluster of the planned model.
Clarity also means that development engineers “Osamu” at Fuso in Tokyo, “Beth” at Freightliner in Portland and “Kurt” at Mercedes-Benz in Stuttgart all have exactly the same understanding of a jointly formulated requirement definition — for a new multifunctional display that is to be installed in the respective instrument clusters of the heavy-duty trucks from these three brands, for example.
Read the rest of this entry »



