AUTOSAR – An open standardized software architecture for the automotive industry Simon Fürst, BMW 1st AUTOSAR Open Conference & 8th AUTOSAR Premium Member Conference October 23rd, 2008, Cobo Center, Detroit, MI, USADocument Inf o rmati on and Change History Document Ow ner He iko Dör r Document Responsibility SC Document Version 1.5 Document filename AUTOSAR_Tutorial Document S t atus t | R eady for A pproval |
Final > Document Change History Date Ve rsion Changed by Change Des c r iption 30.05.2007 0.1 He iko Dör r Initial creation and proposal for content 10.08.2007 0.2 He iko Dör r Ready for approval 16.08.2007 0.3 He iko Dör r Comments by Mr. B unzel entered 17.08.2007 0.4 He iko Dör r Section on Methodology updated af ter discussion with member of W P I I - 1.2; Sec t ion on Exploitation removed; Ready for approval by SC 23.08.07 1.0 He iko Dör r Tutorial approved by SC 31.08.07 1.1 He iko Dör r PM memberships updated accordin g to slide provided by admin 07.04.08 1.2 He iko Dör r CP updated, readability improved 07.05.08 1.3 He iko Dör r Bus s t ate managers added to BSW modules slide 03.07.2008 1.4 He iko Dör r Selected slides from A T I added (Animated use case for dist ributed scenario, Validator 2), Schedule updated 01.10.2008 1.5 He iko Dör r Selection of slides f o r present ation at 8t h PM conf erence 2 O c t . 2 3 r d 20 08 AUTOS A R Tut o rialDocument Inf o rmati on and Change History Document Change ...
Document Change History Change Description Initial creation and proposal for content Ready for approval Comments by Mr. Bunzel entered Section on Methodology updated after discussion with member of WPII-1.2; Section on Exploitation removed; Ready for approval by SC Tutorial approved by SC PM memberships updated according to slide provided by admin CP updated, readability improved Bus state managers added to BSW modules slide Selected slides from ATI added (Animated use case for distributed scenario, Validator 2), Schedule updated Selection of slides for presentation at 8th PM conference
AUTOSAR Tutorial
Document Information and Change History
3
Date
22.10.2008
Version
1.51
Oct. 23rd 2008
Changed by
Simon Fürst
Document Change History
Change Description
Review
AUTOSAR Tutorial
4
Automotive Systems and SW Engineering
Oct. 23rd 2008
AUTOSAR Tutorial
Automotive Open System Architecture Cooperate on standards compete on implementation
5
Non functional legal requirements
Vehicle family management
Resource efficiency
Driver assistance
Driving dynamics
Safety functions (active/passive)
Comfort functions
Oct. 23rd 2008
AUTOSAR Tutorial
AUTOSAR Managing Complexity by Exchangeability and Reuse of Software Components OEM b
6
OEM a
Platform a.1 Platform a.2 Platform a.n Exchangeability between‘ manufacturer s applications OEM f
O
Platform f.1 Platform f.2 Platform f.n
ct.23rd2008
Platform b.1 Platform b.2 Platform b.n
Exchangeability between‘supplier s solutionsOEM c
Supplier B Supplier A ¾Chassis¾Chassis ¾Safety¾Safety ¾Bo/Cdyfoomrt¾Telematics Supplier C ¾Body/Comfort ¾Powertrain ¾Telematics ¾Multimedia OEM e
Platform e.1 Platform e.2 Platform e.n
AUTOSARTutorial
Platform c.1 Platform c.2 Platform c.n OEM d
Platform d.1 Platform d.2 Platform d.n
Exchangeability between vehicle platforms
AUTOSARProject Objectives and Main Working Topics
¾Implementation and standardization of basic system functionsas an OEM wide “Standard Core“ solution Architecture ¾Scalabilityto different vehicle and platform variants
¾
Maintainabilitythroughout the whole “Product Life Cycle“
¾Increased use ofreicla“mmCo off the shelf hardware“
¾Architecture: ArchitectureSoftware architecture including a complete basic or AInptpelirfcaatioMethodologyASRUAOTcoSaBisreftwaninasaoitargetoftalpnorfrmeldclaeosshtECUfortackresawtfoslatnemnorvien ce hardware independent software applications.
¾Methodology: ArchitectureExchange formats or description templates to enable a seamless configuration process of the basic software stack AInptplifcaactieoMethodology erand the integration of application software in ECUs and it includes even the methodology how to use this framework.
¾Application Interfaces: ArchitectureSpecification of interfaces of typical automotive applications Applicatiofrom all domains in terms of syntax and semantics, which Interface Methodologyshould serve as a standard for application software.
8 Oct. 23rd 2008
AUTOSAR Tutorial
Technical scope of AUTOSAR
9
New concepts
Industry-wide consolidation of existing basic ‘ software designs
cOt.23rd2008
Methodology
Exchange Meta Model Formats Configuration Concept Virtual Function InputBus(VFB)Error TemplatesRunTimeHandling Environment
Diagnostics Gateway OS Kernel ECU Bus systems µControllerAbstractionComplex AbstractionDrivers Drivers
AUTOSARTutorial
Benefits from AUTOSAR
10
OEM
Oct.23rd200
OEM overlapping reuse of software modules Maintaining ability to compete on innovative functions, enlarged design flexibility Simplification of the integration task Reduction of total SW development costs
Supplier
8
Reduction of version proliferation Development partitioning among suppliers Increase of efficiency in functional development New business models possible
Common interfaces with development Tool provideressesSeamless,amanegbael,atksptoizimedcorp (time dependent) tool landscape
New market entrant
AUTOSRATutorial
Transparent and defined interfaces enable new business models