Towards a model for cost-benefit-analysis of quality assurance in the automotive E/E development
Proceedings of the 1st international workshop on Business impact of process improvements
Applying restricted english grammar on automotive requirements: does it work? a case study
REFSQ'11 Proceedings of the 17th international working conference on Requirements engineering: foundation for software quality
Improved control of automotive software suppliers
PROFES'05 Proceedings of the 6th international conference on Product Focused Software Process Improvement
Empirical validation of a requirements engineering process guide
EASE'09 Proceedings of the 13th international conference on Evaluation and Assessment in Software Engineering
Hardware-in-the-loop-based evaluation platform for automotive instrument cluster development (EPIC)
Proceedings of the 5th ACM SIGCHI symposium on Engineering interactive computing systems
| Hi-index | 0.00 |
The specification volume for all software-based systems that are built in a modern car has passed the 20,000 pages mark.Even for a single component, we find specification documents comprising several hundred pages.Clearly, such specification documents cannot be created and changed simply and quickly.We hence need a systematic process to elicit and maintain, negotiate and validate all requirements, i.e. a proper requirements engineering process. In this paper, we present an example for such an automotive requirements engineering process and the instruments we employed to manage this process.The experiences are drawn from projects at DaimlerChrysler Passenger Car Development. The paper sketches the requirements engineering process used, the core management instruments deployed, e.g. a feature list, and observations gained in utilizing this process.