SAE R-361-2005 Automotive Software Engineering Principles Processes Methods and Tools (To Purchase Call 1-800-854-7179 USA Canada or 303-397-7956 Worldwide).pdf

《SAE R-361-2005 Automotive Software Engineering Principles Processes Methods and Tools (To Purchase Call 1-800-854-7179 USA Canada or 303-397-7956 Worldwide).pdf》由会员分享，可在线阅读，更多相关《SAE R-361-2005 Automotive Software Engineering Principles Processes Methods and Tools (To Purchase Call 1-800-854-7179 USA Canada or 303-397-7956 Worldwide).pdf（410页珍藏版）》请在麦多课文档分享上搜索。

1、Jrg Schuffele Thomas Zurawka Automotive Software Engineering Principles, Processes, Methods, and ToolsAUTOMOTIVE SOFTWARE ENGINEERING PRINCIPLES, PROCESSES, METHODS, AND TOOLSOther SAE titles of interest: Vehicle Multiplex Communication: Serial Data Networking Applied to Vehicular Engineering By Chr

2、istopher A. Lupini (Order No. R-340) Finite Element Analysis for Design Engineers By Paul M. Kurowski (Order No. R-349) Automobile Electrical and Electronic Systems, Third Edition By Thomas H. Denton (Order No. R-363) Electronic Control Systems By Ross Bannatyne (Order No. T-107) For more informatio

3、n or to order a book, contact SAE at 400 Commonwealth Drive, Warrendale, PA 15096-0001; phone (724) 776-4970; fax (724) 776-0790; e-mail CustomerServicesae.org; website http:/store.sae.org.AUTOMOTIVE SOFTWARE ENGINEERING PRINCIPLES, PROCESSES, METHODS, AND TOOLS Jrg Schuffele Thomas Zurawka Translat

4、ed by Roger Carey Warrendale, Pa. Copyright 2005 SAE International eISBN: 978-0-7680-5505-4All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmit- ted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, w

5、ithout the prior written permission of SAE. For permission and licensing requests, contact: SAE Permissions 400 Commonwealth Drive Warrendale, PA 15096-0001 USA E-mail: permissionssae.org Tel: 724-772-4028 Fax: 724-772-4891 Library of Congress Cataloging-in-Publication Data Schuffele, Jrg. Automotiv

6、e software engineering. English Automotive software engineering: principles, processes, methods, and tools / Jrg Schuffele, Thomas Zurawka ; translated by Roger Carey. p. cm. Translation from the German language ed. Includes bibliographical references and index. ISBN-10 0-7680-1490-5 ISBN-13 978-0-7

7、680-1490-5 1. Automotive computers. 2. Software engineering. I. Zurawka, Thomas. II. Title. TL272.53.S33 2005 Translated from the German language edition: Automotive Software Engineering: Grundlagen, Prozesse, Methoden und Werkzeuge by Jrg Schuffele and Thomas Zurawka Copyright Friedr. Vieweg on the

8、 other hand, entirely new opportunities are created by networking functions that formerly used to be independent of each other. Consistent application of systems engineering methods is a crucial factor for success in managing the vehicle as a complete system. This book addresses this extensive topic

9、 with special emphasis on the major vehicle subsystems of powertrain, chassis, and body. Hans-Georg Frischkorn, Senior Vice President System Architecture and Integration, BMW Group, Munich, Germany -v-AUTOMOTIVE SOFTWARE ENGINEERING From cost driver to competitive advantage. Only a pioneer in softwa

10、re technology will gain technological advantage in the automotive industry. Successful cooperation between engineers from various disciplines in systems engi- neering, however, will be possible only if everyone shares the same background knowledge, the same terminology, and an appropriate process mo

11、del. This book uses real-life examples in an impressive demonstration of software engineering essentials and applicable methods. Dr.-Ing. Wolfgang Runge, Member, Board of Management, ZF Lenksysteme GmbH, Schwbisch Gmnd, Germany Embedded systems are an automotive asset. Embedded computer systems prov

12、ide opportunities to distinguish transportation products and services in the increasingly competitive automotive business. To interpret Moores Law, elec- tronics continue to become more powerful while prices keep dropping. The resulting systems complexity can be managed only with an in-depth underst

13、anding of the principles, practices, methods, and tools discussed in this essential text. I applaud Dr. Zurawka and Mr. Schuffele of ETAS GmbH on their comprehensive work on very important topics. This material must be understood by any organization wishing to participate in the automotive business.

14、 As we continue to evolve our engineering processes, I look forward to more assistance from the leaders in this field. Craig A. Brown, GM Powertrain Engineering, General Motors Corp., Detroit, MI Advanced educationan opportunity and a challenge. In the greater Stuttgart area, vehicle manufacturing i

15、s the preeminent industry, with development centers of major vehicle manufacturers and suppliers offering a great many job opportunities. At the University of Stuttgart, courses in software technology are part and parcel of the engineer- ing program. This book offers students who are pursuing an aca

16、demic degree in engineering the opportunity to familiarize themselves with practical automotive industry applications. In fact, the methods introduced in this book may even serve as models for applications in other industries. Prof. Dr.-Ing. Dr. h.c. Peter Ghner, Institute for Automation and Softwar

17、e Technology, Univer- sity of Stuttgart, Germany Vehicle development needs perspective based on integrated model. As a natural consequence of ongoing advances in vehicle development, customer expectations must be satisfied while ensuring compliance with government regulations. Increasingly, these an

18、d related areas are the special domain of automotive electronic systems. -vi-THE ROLE OF SOFTWARE IN THE AUTOMOBILE In fact, most of the competitive advantage in vehicles today tends to lie in the electronic content of the vehicle, the software component being a major part of these systems. The safe

19、, reliable, cost effective, and rapid development of automotive software-based systems are major issues for vehicle and component manufacturers. Authors Schuffele and Zurawka address the complex issues of automotive electronic systems development from a perspective based on an integrated model, offe

20、ring students a paradigm for an integrated systems solution to vehicle embedded software engineering. The book will serve as a foundation for integrated vehicle software devel- opment practices as this technology continues to emerge and expand. Prof. Mark Thompson, Electrical and Computer Engineerin

21、g, Kettering University, Flint, MI A new system science is needed. As hardware development costs and manufacturing fixed costs have been increasing dramati- cally and as product requirements change faster and faster over a short period of time, embedded system, subsystem and even IC designers have t

22、urned to software as a way of coping with these problems. Yet this shift has caused an entire new set of challenges. Software programs have not been born equal. Software for transportation systems for example has to satisfy hard constraints that depend on the implementation platform thus making the

23、very base of the traditional software abstraction invalid. It is no wonder that more than 30% of severe malfunctions in automobiles are originated by faulty software. We need a new system science to deal with the digital abstrac- tion and the physical world in a unified way. This book is the documen

24、tation of pioneering work carried out by the authors in developing methodologies and tools for automotive software. The importance of methodologies cannot be overemphasized as tool power can only be unleashed by appropriate methodologies as I have learned over the years in my work in EDA. The unique

25、 value of this book is in documenting the effort of conjugating methodologies and tools, a very successful one indeed as the prosperity of ETAS witnesses. Prof. Alberto Sangiovanni Vincentelli, The Edgar L. and Harold H. Buttner Chair of EECS, University of California at Berkeley; Co-founder, Chief

26、Technology Advisor and Member of the Board of Directors, Cadence Design Systems, Berkeley, CA -vii-PREFACE After a history of more than 100 years, the automobile as a product continues to evolve at a very fast pace. Since the early 1970s, its evolution has strongly been influenced by a steady increa

27、se in onboard electronic systems and software in the vehiclea trend that continues unabated. As a consequence of this trend, vehicle development, production, and service are changing in fundamental ways. Using software to implement functions in the vehicle provides developers with new degrees of fre

28、edom and solutions to existing conflicts of objectives. The resulting complexity can be managed only by using processes, methods, and tools that are appropriate for vehicle-specific applications. In the last few years, various methods and standards have been devised for the development of software f

29、or in-vehicle electronic systems. These methods and standards are best described by the collective term automotive software engineering. Over time, a complex terminology has evolved in automotive software engineering. All of us working in this field are confronting these terms on a daily basis. Howe

30、ver, it is no overstate- ment to say that many of us are no longer sure of a clear or shared definition of many of these terms. In fact, some of the terms are used in very different contexts where they clearly do not mean one and the same thing. For example, the term “process“ occurs not only in the

31、 context of control engineering but is also used (to designate a very specific thing) in conjunction with real-time systemsto say nothing of its general meaning in development, where it describes development methods in a wider context. In this book, we define essential terms and then use them consis

32、tently as defined. The chapters of this book focus on the processes, methods, and tools for the development of software for electronic systems in the vehicle. The book also places emphasis on the interac- tion between software development (as a professional discipline limiting itself to certain vehi

33、cle components) and the all-embracing systems engineering (a field that considers all vehicle com- ponents). The development methods introducedthe so-called processestake the form of models, that is, they comprise an abstract and idealized reflection of daily practice. Although they may serve as gui

34、delines for a variety of development projects, they will need to be evaluated and adapted before they are applied to specific projects. We have taken great pains to provide clear and unambiguous descriptions of processes and supporting methods and tools. The wealth of information available on many a

35、spects of our topic forced us to forgo detailed discussion of some of them. Generally speaking, we have limited our discussion to aspects that are relevant and specific to the automotive industry. We certainly make no claim of having provided here the only proper or even a complete meth- odological

36、approach. As employees of ETAS, we are convinced, however, that tools and soft- ware components by ETAS are ideally suited to support the processes and methods introduced in this book. -ix-AUTOMOTIVE SOFTWARE ENGINEERING Practical Cases in Point To a development team, a process serves only as a supp

37、orting structure. The introduction of any given process will be successful only if every team member sees it as a benefit. When extensive practical tasks and their solutions can be made transparent to everyone in the team because every activity associated with any given task can be traced, this is a

38、 benefit. In this sense, this book is not a theoretical textbook, far removed from the practical world. On the contrary, all of its ideas, concepts, and suggestions are based on practical use cases that we present by means of appropriate examples. Of course, these aspects are derived from the experi

39、ence we gained over the years while working closely with vehicle manufacturers and suppliers. Examples come from production projects, including associated service considerations, as well as from research and advanced development projects. Readership of This Book We would like to offer this book to a

40、ll who work for manufacturers and suppliers in vehicle development, production, and service and who encounter software in the vehicle during their daily activities. We hope to be able to pass on some useful suggestions. In addition, we hope this book will serve as a basic tool for the instruction of

41、 engineering students and for the introduction of new employees to their respective workplaces. Basic familiarity with open-loop and closed-loop control engineering, system theory, and software engineering, although helpful, is not a prerequisite for being able to understand the topic of this book.

42、Readers may feel in some places that they could benefit from more detailed discussion of one topic or another. If you are one of these readers, please let us know. We welcome any and all feedback and especially any suggestions for improvement, which we will carefully consider for inclusion in subseq

43、uent reprintings. -x-ACKNOWLEDGMENTS We would like to take this opportunity to express to all of our customers our appreciation for the many years of successful and trusting cooperation. This book would not have been possible without this valuable exchange of experiences. We also wish to thank the B

44、MW Group for its kind permission to include experiences gathered while working on proprietary BMW projectsin the case of one author (Jrg Schuffele), also in his capacity as an employee at BMW. This includes the consideration of process definitions, as well as recommendations for production projects

45、at BMW. We are indebted to Hans-Georg Frischkorn for his foreword to this book, and special thanks go to Heinz Merkle, Dr. Helmut Hochschwarzer, Dr. Maximilian Fuchs, Prof. Dr. Dieter Nazareth, and all of their staff. Many of the processes and methods presented in this book evolved over many years o

46、f trusting cooperation with Robert Bosch GmbH. These processes and methods are now widely accepted, and they keep recurring here and there throughout this book. We gratefully acknowledge the valuable input from the capable staff in the Chassis Systems, Diesel Systems, and Gasoline Systems Divisions,

47、 and the Research and Advanced Development Department of Robert Bosch GmbH. Sincere thanks also go to Dr. Siegfried Dais, Dr. Wolfgang Runge, Craig A. Brown, Prof. Dr. Peter Ghner, Prof. Mark Thompson, and Prof. Alberto Sangiovanni Vincentelli for their words in the foreword section titled “The Role

48、 of Software in the Automobile.“ We also are indebted to our many colleagues who, over these past years, have contributed to this book in many different ways. For the careful and critical task of copy-editing the manuscript, we express our sincere apprecia- tion to Roland Jeutter, Dr. Michael Nicolaou, Dr. Oliver Schlter, Dr. Kai Werther, and Hans- Jrg Wolff. Finally, for the careful English translation of the manuscript, sincere thanks go to Roger Carey. Jrg Schuffele Thomas Zurawka Stuttgart, Germany June 2005 -xi-